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
File System Archiving in a clustered environment
If your Windows file servers are grouped in a cluster, you can make the FSA services that run on them highly available. You must add an FSA resource to the cluster resource group or service group, and configure the FSA resource for high availability. The FSA resource monitors the state of the FSA services on the online node. If a problem occurs with the FSA services on the online node, then the cluster resource group or service group that contains the FSA resource fails over to the next available node.
Figure: Example FSA cluster configuration shows an environment in which three file servers are clustered together.
Note that you can make the FSA Agent services highly available only when there is a shared disk resource.
The FSA clustering feature works with the following cluster software:
Windows Server Failover Clustering (formerly known as Microsoft Cluster Server, or MSCS)
Veritas Cluster Server (VCS)
See the Enterprise Vault Compatibility Charts for details of the supported versions of this software, and the supported versions of Windows.
The following cluster types are supported:
Active/passive cluster. To support high availability, the shared cluster resources are made available on one node of the cluster at a time. If a failure on the active cluster node occurs, the shared resources fail over to the passive node and users may continue to connect to the cluster without interruption.
Active/active cluster. To support load balancing and high availability, the cluster resources are split among two or more nodes. Each node in the cluster is the preferred owner of different resources. In the event of a failure of either cluster node, the shared resources on that node fail over to the remaining cluster nodes.
Enterprise Vault supports multiple nodes in any combination of active/passive and active/active. We have validated configurations with up to four nodes.
For guidelines on how to make the FSA Agent services highly available in a clustered environment, see the Setting up File System Archiving guide.