Enterprise Vault™ Introduction and Planning
- About this guide
- Overview of Enterprise Vault
- How Enterprise Vault works
- About Enterprise Vault indexing
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Archive Discovery Search Service
- About the Enterprise Vault Outlook Add-In
- About Enterprise Vault Search
- Enterprise Vault administration
- About reporting and monitoring in Enterprise Vault
- Exchange Server archiving
- About Exchange Server archiving and user mailboxes
- Exchange Server and journal mailbox archiving
- Exchange Public Folder archiving
- File System Archiving
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Skype for Business Archiving
- Enterprise Vault Accelerators
- About Compliance Accelerator
- The Compliance Accelerator client application
- About Discovery Accelerator
- Discovery Accelerator client application
- Building in resilience
- About Enterprise Vault and VCS
- About Enterprise Vault and Windows Server Failover Clustering
- About Enterprise Vault building blocks
- Planning component installation
- Where to set up the Enterprise Vault Services and Tasks
- Installation planning for client components
- Planning your archiving strategy
- How to define your archiving policy for user mailboxes
- How to plan the archiving strategy for Exchange public folders
- How to plan settings for retention categories
- How to plan vault stores and partitions
- About Enterprise Vault reports
Supported Windows Server Failover Clustering configurations
An Enterprise Vault cluster consists of:
One or more primary nodes, each normally hosting an Enterprise Vault cluster server.
One or more failover nodes: standbys that can take over the job of hosting an Enterprise Vault cluster server if a primary node fails.
Enterprise Vault does not permit "active/active" cluster configurations. That is, only one Enterprise Vault cluster server can run on a clustered node at any one time. You can configure Enterprise Vault in any operation mode that adheres to this restriction, such as:
An active/passive failover pair: a primary node with a dedicated failover node.
N+1 (hot standby server): two or more primary nodes share a single failover node. Only one node failure can be accommodated at any one time.
N+M: an extension of the hot standby concept with N primary nodes and M failover nodes. Only M node failures can be accommodated at one time.
N+M any-to-any: identical to N+M, except that there is no need to fail back to the original node after a failover. When the original node becomes available again, it can operate as a failover node.