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
Requirements for SharePoint Servers
The required software and settings for the SharePoint Servers are as follows:
You must use a version of Microsoft SharePoint that Enterprise Vault supports.
For more information see the Enterprise Vault Compatibility Charts.
Ensure that the Vault Service account has local administrator permissions on the SharePoint Server computer.
The account under which the Enterprise Vault SharePoint task runs (typically the Vault Service account) must have full access to target site collections and their content.
SharePoint Servers must be running Windows Server 2008 with Service Pack 1 or later. If Windows Server 2008 with Service Pack 1 is installed, you must also install the following mandatory hotfix for IIS:
http://support.microsoft.com/kb/949516
Note the following:
The hotfix that Microsoft provides for Windows Vista is the hotfix to use for Windows Server 2008.
By default, the Microsoft web page presents a hotfix download that matches the operating system of the computer that you are using. On the download page, choose the option to show hotfixes for all platforms and languages so that you can select the correct version of the hotfix.
If you install in a server farm, you must install the Enterprise Vault components on all the front-end web servers.
The Enterprise Vault SharePoint components require the Enterprise Vault SharePoint HttpModule. The Enterprise Vault Setup program automatically installs the Enterprise Vault HttpModule when you choose to install the Enterprise Vault SharePoint component.
The DCOM port (135) must be open on the target SharePoint system.
If Enterprise Vault and SharePoint run on separate computers, we recommend that you do not install Backup Exec on the same computer as the Enterprise Vault Microsoft SharePoint Components.
You must use host names in the URL when adding SharePoint targets.
To add a web application in SharePoint 2013 or later as an archiving target, you must ensure that the web application has the following authentication settings:
Integrated Windows authentication is enabled.
Trusted identity providers and forms-based authentication for all zones in the target web application are disabled.
To add a web application in SharePoint 2010 as an archiving target, you must ensure that the web application has the classic mode authentication enabled.
Note:
Authentication settings are required not only for adding the web application as a target but also for archiving its content. Archiving stops if these settings are changed after adding the target.
When a site in SharePoint 2013 or later uses claims authentication, the Claims to Windows Token Service (C2WTS) must be configured and running.
For more information on how to configure C2WTS, see the following article:
For full details of all the supported versions of required products, see the Enterprise Vault Compatibility Charts.