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
Developing a suitable sharing regime for Enterprise Vault single instance storage
If you use Enterprise Vault single instance storage, you need to create a sharing regime that meets your organization's data sharing requirements and which is appropriate for your network connection speeds.
Consider what sort of sharing regime you require before you start archiving. There are limits to what you can change:
You can change a vault store's sharing level, but the change does not act retrospectively. For example, if you change a vault store's sharing level from 'share within group' to 'share within vault store', any items already shared within the vault store group remain so.
You cannot move a vault store to another vault store group unless all of the following circumstances apply:
You previously upgraded to Enterprise Vault 8.0.
The vault store is one that Enterprise Vault upgraded to Enterprise Vault 8.0, or one that you created in the Default Upgrade Group.
The vault store's sharing level is "No sharing" and has never been changed.
When deciding how to set up single instance storage, consider the following:
You may need to keep parts of your organization separated with information barriers, also known as "Chinese walls". For example, a datacenter may be required by law or by company policy to keep information separate between its investment, retail, and mergers and acquisitions groups, to avoid conflicts of interest.
You may want to create a separate vault store group for each organizational group in which information must be isolated.
Network connectivity between the appropriate computers must be sufficient to provide acceptable storage and retrieval times. As a minimum we recommend that you limit single instance storage to an environment in which the connections support the expected response time of a 100 Mbps switched Ethernet LAN.
The Enterprise Vault server whose Storage service manages a vault store must have adequate connectivity with the following:
The computers that host the vault store partitions for the vault stores that are within the vault store's sharing boundary.
The computer that hosts the vault store group's fingerprint database.
The slower the connection speeds between these computers, the longer it takes Enterprise Vault to archive and retrieve the shared items.
If your organization spans several widely-dispersed geographical locations it may be appropriate to create separate vault store groups for each location. Remember to locate the fingerprint databases locally.
Enterprise Vault provides a connectivity test to estimate connection speeds across sample network connections. The relevant wizards prompt you to run the connectivity test when you create a new vault store group or partition, or when you configure sharing. The connectivity test can help you create a sharing regime with an acceptable level of performance. To assess performance, the connectivity test measures the average round-trip time for a number of ping requests. If you have disabled ping in your environment, use your own tools to decide if the performance is acceptable. We recommend a round-trip time of one millisecond or less.
If the test results indicate poor connectivity, consider modifying the sharing boundaries or changing the location of your computers to improve connection speeds. If you are willing to accept poorer performance, you can choose to accept poor connectivity test results.
When you create a vault store group, configure its fingerprint database appropriately for the projected sharing requirements.
More Information