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
Moving Enterprise Vault data to highly available locations
In outline, the procedure for moving the Enterprise Vault data to highly available locations is as follows:
Stop the Indexing, Shopping, Storage, and Task Controller services.
Make a backup copy of the Enterprise Vault Directory database and data files.
Use the Enterprise Vault Administration Console or run a SQL query against the Enterprise Vault Directory to move the data, as described below.
IndexRootPathEntry [IndexRootPath]
Move the contents of this location to a highly available location.
Update the database using SQL to point at the new location.
The SQL to view the current location is as follows:
SELECT * FROM IndexRootPathEntry WHERE (IndexRootPathEntryId = '<ID FROM LOG FILE>')
The SQL to update the location is as follows:
UPDATE IndexRootPathEntry SET IndexRootPath = '<THE NEW LOCATION>' WHERE (IndexRootPathEntryId = '<ID FROM LOG FILE>')
PartitionEntry [AccountName]
Move the pool entry authorization (
.pea
) file to a highly available location.Use the Enterprise Vault Administration Console to view the properties of the Centera partition and then, on the
tab, edit the box to point at the new location.
PartitionEntry [PartitionRootPath]
Move the contents of this location to a highly available location.
Update the database using SQL to point at the new location.
The SQL to view the current location is as follows:
SELECT * FROM PartitionEntry WHERE (PartitionEntryId = '<ID FROM LOG FILE>')
The SQL to update the location is as follows:
UPDATE PartitionEntry SET PartitionRootPath = '<THE NEW LOCATION>' WHERE (PartitionEntryId = '<ID FROM LOG FILE>')
PartitionEntry/Locations [SecondaryLocation]
Move the secondary storage files to a highly available location.
Update the database using SQL to point at the new location.
The SQL to view the current location is as follows:
SELECT * FROM PartitionEntry INNER JOIN Locations ON PartitionEntry.SecondaryLocation = Locations.LocationIdentity WHERE (PartitionEntry.PartitionEntryId = '<ID FROM LOG FILE>')
The SQL to update the location is as follows:
UPDATE Locations SET Location = '<NEW LOCATION>' WHERE LocationIdentity = (SELECT SecondaryLocation FROM PartitionEntry WHERE PartitionEntryId = '<ID FROM LOG FILE>')
PartitionEntry [StagingRootPath]
Move the contents of this location to a highly available location.
Update the database using SQL to point at the new location.
The SQL to view the current location is as follows:
SELECT * FROM PartitionEntry WHERE (PartitionEntryId = '<ID FROM LOG FILE>')
The SQL to update the location is as follows:
UPDATE PartitionEntry SET StagingRootPath = '<THE NEW LOCATION>' WHERE (PartitionEntryId = '<ID FROM LOG FILE>')
PSTMigratorTask [MigrationDirectory]
Move the contents of this location to a highly available location.
Use the Enterprise Vault Administration Console to view the properties of the PST Migrator Task and update the Temporary files folder.
ShoppingServiceEntry [ShoppingRootPath]
Move the contents of this location to a highly available location.
Use the Enterprise Vault Administration Console to edit the Shopping service location to the new highly available location.
SiteEntry [PSTHoldingDirectory]
Move the contents of this location to a highly available location.
Use the Enterprise Vault Administration Console to view the site properties and update the PST Holding Folder property to point at the new location.
SmtpArchivingTask [HoldingFolder]
Move the contents of this location to a highly available location.
Use the Vault Administration Console to view the properties of the SMTP Archiving task, and update the SMTP Holding Folder property to point at the new location.