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
About Enterprise Vault single instance storage
Enterprise Vault's optimized single instance storage can provide a significant reduction in the storage space that is required for archived items. Enterprise Vault identifies the shareable parts (SIS parts) of an item, such as a message attachment or the contents of a document. It stores each SIS part separately, and only once within a sharing boundary. A sharing boundary can include one or more vault stores within a vault store group. When Enterprise Vault identifies a SIS part that it has already stored in the target vault store's sharing boundary, it references the stored SIS part file instead of archiving the SIS part again.
Enterprise Vault applies a minimum size threshold for SIS parts. The size threshold enables Enterprise Vault to balance the likely storage savings against the resources that are required to create, archive, and retrieve the SIS parts.
Enterprise Vault single instance storage can save storage space in a number of ways:
Enterprise Vault shares the SIS parts between all the vault stores within a sharing boundary. For example, if you use separate vault stores for journaling and mailbox archiving, Enterprise Vault can share the SIS parts between the vault stores.
If a number of separate messages with the same attachment are sent to multiple recipients, Enterprise Vault stores the attachment only once within a sharing boundary.
Enterprise Vault identifies a SIS part from the content, not the file name. If two messages both have the same file attachment, Enterprise Vault can share the attachments, even if they have different file names.
Enterprise Vault can share the identical SIS parts that result from different types of archiving, such as an Exchange message attachment that is also stored as a file on a file server.
A new vault store uses single instance storage by default, and shares only the SIS parts of items that are archived within itself. You can run the Configure Sharing wizard on a vault store group to extend sharing between vault stores, or to turn off Enterprise Vault single instance storage if you want.
Note the following:
. Enterprise Vault single instance storage is not performed when items are stored to partitions that are hosted on Dell EMC Centera devices. Enterprise Vault provides a separate device-level sharing option to take advantage of the sharing capabilities of Centera devices.
. Enterprise Vault shares the SIS parts between items in the same smart partition, but it does not share the SIS parts between a smart partition and other partitions.
For example, suppose that two employees receive the same email, which has an attachment. For compliance reasons, Enterprise Vault archives one employee's emails to a smart partition; it archives the other employee's emails to the standard vault store partition. If Enterprise Vault first archives the email and its attachment to the standard partition then, when it subsequently archives the email to the smart partition, it should not normally archive the attachment again. This would mean that the data on the smart partition is not fully compliant, however, so in this case Enterprise Vault archives both the email and the attachment again.