Enterprise Vault™ Installing and Configuring
- About this guide
- Section I. Enterprise Vault requirements
- Enterprise Vault hardware requirements
- Hardware requirements for Enterprise Vault server
- About the storage requirements for Enterprise Vault
- Storage for vault stores
- Storage requirements for SQL databases
- Enterprise Vault required software and settings
- Basic software requirements for Enterprise Vault
- Best practice settings for Enterprise Vault servers
- Preinstallation tasks for Enterprise Vault server
- About assigning permissions and roles in SQL databases
- Additional requirements for Operations Manager
- Additional requirements for classification
- Additional requirements for Enterprise Vault Reporting
- Additional requirements for Exchange Server archiving
- Preinstallation tasks for Exchange server archiving
- Assigning Exchange Server permissions to the Vault Service account
- Enterprise Vault client access with Exchange Server archiving
- Requirements for RPC over HTTP
- Additional requirements for Domino Server archiving
- Requirements for Domino mailbox archiving
- Register the Enterprise Vault Domino Gateway
- About the user ID for Domino mailbox archiving
- Requirements for Domino journaling archiving
- Additional requirements for File System Archiving (FSA)
- Additional requirements for SharePoint Server archiving
- Additional requirements for Skype for Business Archiving
- Additional requirements for SMTP Archiving
- Additional requirements for Enterprise Vault Search
- Additional requirements for a standalone Enterprise Vault Administration Console
- Additional requirements for the Archive Discovery Search Service
- Enterprise Vault hardware requirements
- Section II. Installing Enterprise Vault
- Section III. Configuring Enterprise Vault
- About configuring Enterprise Vault
- Running the Enterprise Vault configuration wizard
- Securing Enterprise Vault Web Access components
- Running the Enterprise Vault Getting Started wizard
- About the express and custom modes of the Enterprise Vault Getting Started wizard
- About indexing configuration with the Enterprise Vault Getting Started wizard
- About storage configuration with the Enterprise Vault Getting Started wizard
- Configuring Enterprise Vault Operations Manager
- Configuring the Archive Discovery Search Service
- Section IV. Initial Enterprise Vault setup
- Initial Enterprise Vault setup
- Setting up storage
- About Enterprise Vault single instance storage
- About creating vault stores
- About Enterprise Vault safety copies
- About Enterprise Vault safety copies
- Creating vault store partitions
- Adding index locations
- Setting up Index Server groups
- Do I need to create Index Server groups?
- Reviewing the default settings for the site
- Setting up Enterprise Vault Search
- Setting up provisioning groups for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Setting up Enterprise Vault Search Mobile edition
- Managing metadata stores
- Section V. Clustering Enterprise Vault with VCS
- Introducing clustering with VCS
- Installing and configuring Storage Foundation HA for Windows
- Configuring the VCS service group for Enterprise Vault
- Running the Enterprise Vault Configuration wizard
- Setting up Enterprise Vault in an active/passive VCS configuration
- About setting up Enterprise Vault in a VCS N+1 configuration
- Implementing an SFW HA-VVR disaster recovery solution with Enterprise Vault
- Troubleshooting clustering with VCS
- Section VI. Clustering Enterprise Vault with Windows Server Failover Clustering
- Introducing clustering with Windows Server Failover Clustering
- Control of Enterprise Vault services in a Windows Server failover cluster
- Preparing to cluster with Windows Server Failover Clustering
- Configuring Enterprise Vault in a Windows Server failover cluster
- Setting up a new Enterprise Vault installation with Windows Server Failover Clustering support
- Examples of Enterprise Vault installations in various Windows Server Failover Clustering modes
- Converting an existing Enterprise Vault installation to a Windows Server failover cluster
- Modifying an existing Enterprise Vault cluster
- Troubleshooting clustering with Windows Server Failover Clustering
- Introducing clustering with Windows Server Failover Clustering
- Appendix A. Automatically preparing an Enterprise Vault server
Setting up the shared disks and volumes for a Windows Server failover cluster
You must set up shared storage and volumes for the cluster, ready to accept the shared data. Each Enterprise Vault cluster server requires one or more volumes in which to store the following:
MSMQ data
Enterprise Vault Storage queue
Indexing service data
Storage service data (vault store partitions)
Shopping service data
PST holding folders
SMTP holding folder
Centera staging areas
It is good practice for MSMQ data, the Enterprise Vault Storage queue, Indexing service data, Storage service data, and the SMTP holding folder to each have a separate storage device resource. Placing them on the same drives may result in degraded performance. You can however place MSMQ data and the Enterprise Vault Storage queue on the same storage device resource because MSMQ and the Storage queue have similar performance.
For performance reasons we recommend that you take care to place the shared data in suitable locations. Some data requires separate disks.
See the Enterprise Vault Performance Guide at https://www.veritas.com/docs/100000918 for details.
For example, if you are setting up two Enterprise Vault cluster servers, EVSERVER1 and EVSERVER2, you might allocate the shared storage for the cluster as follows:
Cluster |
|
EVServer1 |
|
EVServer2 |
|
Note the following when setting up the shared disks and volumes:
You must configure the storage for different cluster services on different storage devices, as only one server can connect to a storage device at a time.
Configure shared disks and volumes such that the required nodes will be able to access the clustered disk resources on failover. For example, in a 2+1 configuration, the failover node must have access to the quorum data volume, plus all the volumes that the cluster servers use.