Veritas Enterprise Vault™ Installing and Configuring
- About this guide
- Section I. Enterprise Vault requirements
- Enterprise Vault hardware requirements
- Hardware requirements for Enterprise Vault server
- Hardware requirements for SQL Server
- Network requirements for Enterprise Vault
- About the storage requirements for Enterprise Vault
- Storage for vault stores
- Storage for Enterprise Vault indexes
- Storage requirements for SQL databases
- Storage requirements for the Enterprise Vault cache folder
- Local storage requirements for temporary files
- TEMP folder security requirements
- Granting additional users and groups access to the TEMP folder
- Enterprise Vault required software and settings
- About the Enterprise Vault required software and settings
- About valid computer names for Enterprise Vault servers
- About the Enterprise Vault Deployment Scanner
- Basic software requirements for Enterprise Vault
- Best practice settings for Enterprise Vault servers
- Message queue cleanup interval: MessageCleanupInterval
- Message queue message storage limit: MachineQuota
- Disable opportunistic locking: OplocksDisabled
- Disable loopback check: DisableLoopbackCheck
- Disable strict name checking: DisableStrictNameChecking
- Maximum Outlook attachments and recipients: AttachmentMax and RecipientMax
- TCP/IP maximum ports and TCP timed wait delay
- Preinstallation tasks for Enterprise Vault server
- Creating the Vault Service account
- Creating a SQL login account
- About assigning permissions and roles in SQL databases
- Locking down Enterprise Vault SQL databases
- Creating Enterprise Vault DNS aliases
- Turning off or reconfiguring Windows Firewall
- Securing data locations
- About User Account Control (UAC)
- Additional requirements for Operations Manager
- Additional requirements for classification
- Additional requirements for Enterprise Vault Reporting
- Additional requirements for Exchange Server archiving
- About Exchange Server archiving
- Preinstallation tasks for Exchange server archiving
- Installing Outlook on the Enterprise Vault server
- Creating the Enterprise Vault system mailbox
- Removing the restriction on NSPI connections to a Windows Server domain controller
- Creating a user profile on the Enterprise Vault server
- Creating a mailbox for the Vault Service account
- Configuring the Exchange throttling policy on the Vault Service account
- Granting the Vault Service account Send As permission on the system mailboxes
- 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
- Domino Server archiving requirements for all Enterprise Vault servers
- Requirements for Domino mailbox archiving
- Required software for Enterprise Vault Domino Gateway
- Required software for target Domino mail servers
- Requirements for Enterprise Vault extensions for Notes clients
- Preinstallation tasks for Domino mailbox archiving
- Register the Enterprise Vault Domino Gateway
- Configuring the Internet port for HTTP on the Enterprise Vault Domino Gateway
- Configuring server security for the Enterprise Vault Domino Gateway
- Configuring Single Sign-On on the Enterprise Vault Domino Gateway
- Clustering Enterprise Vault Domino Gateway servers
- Configuring an alias URL for web connections to the Enterprise Vault Domino Gateway server
- About the user ID for Domino mailbox archiving
- Configuring the server document for each target Domino mail server
- Install and configure Enterprise Vault Domino Gateway
- Requirements for Domino journaling archiving
- Additional requirements for File System Archiving (FSA)
- Additional requirements for SharePoint Server archiving
- Additional requirements for SMTP Archiving
- Additional requirements for Enterprise Vault Search
- Additional requirements for a standalone Enterprise Vault Administration Console
- Enterprise Vault hardware requirements
- Section II. Installing Enterprise Vault
- Licenses and license keys
- Installing Enterprise Vault
- Postinstallation tasks
- Repairing, modifying, or uninstalling Enterprise Vault
- Section III. Configuring Enterprise Vault
- About configuring Enterprise Vault
- Running the Enterprise Vault configuration wizard
- Running the Enterprise Vault Getting Started wizard
- What the Enterprise Vault Getting Started wizard does
- Preparing to run the Enterprise Vault Getting Started wizard
- 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
- About policy definition with the Enterprise Vault Getting Started wizard
- About Exchange target configuration with the Enterprise Vault Getting Started wizard
- About Domino target configuration with the Enterprise Vault Getting Started wizard
- About file target configuration with the Enterprise Vault Getting Started wizard
- Planning for the Enterprise Vault Getting Started wizard
- Configuring Enterprise Vault Operations Manager
- Section IV. Initial Enterprise Vault setup
- Initial Enterprise Vault setup
- Setting up storage
- About setting up storage for Enterprise Vault archives
- About Enterprise Vault single instance storage
- About sharing levels and sharing boundaries
- How Enterprise Vault single instance storage works
- About the fingerprint database
- Deletion of SIS parts
- Requirements for Enterprise Vault single instance storage
- About EMC Centera device-level sharing
- About sharing partitions on storage devices that support the Enterprise Vault storage streamer API
- Developing a suitable sharing regime for Enterprise Vault single instance storage
- Creating vault store groups
- About creating vault stores
- About Enterprise Vault safety copies
- Choosing when to remove Enterprise Vault safety copies
- Checking that the partition has been backed up before Enterprise Vault removes safety copies
- Using the archive attribute to determine whether a partition has been backed up
- Using the trigger file mechanism to determine whether a partition has been backed up
- Creating a vault store
- About Enterprise Vault safety copies
- Creating vault store partitions
- Configuring sharing for a vault store group
- Adding index locations
- Setting up Index Server groups
- About Index Server groups
- Do I need to create Index Server groups?
- Do you have more than one Enterprise Vault server?
- Do you use or plan to use journal archiving or File System Archiving?
- Do you use or plan to use Compliance Accelerator or Discovery Accelerator?
- Is the server loading evenly distributed across existing Enterprise Vault servers?
- Are there more than approximately 5,000 mailbox archives per Enterprise Vault server?
- Creating an Index Server group
- Adding an Index Server to an Index Server group
- Removing an Index Server from an Index Server group
- Assigning a vault store to an Index Server group
- Unassigning a vault store from an Index Server group
- Assigning a vault store to a different indexer
- Reviewing the default settings for the site
- Setting up Enterprise Vault Search
- About Enterprise Vault Search
- Defining search policies for Enterprise Vault Search
- Setting up provisioning groups for Enterprise Vault Search
- Creating and configuring Client Access Provisioning tasks for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Configuring Enterprise Vault Search for use in Forefront TMG and similar environments
- 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
- Before you run 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
- About installing and configuring SFW HA-VVR with Enterprise Vault
- Overview of the steps for installing and configuring SFW HA-VVR
- Setting up the VCS cluster on the primary site
- Setting up the VCS cluster on the secondary site
- Adding the VVR components for replication
- Adding the GCO components for wide-area recovery
- Troubleshooting clustering with VCS
- Section VI. Clustering Enterprise Vault with Windows Server Failover Clustering
- Introducing clustering with Windows Server Failover Clustering
- About clustering Enterprise Vault with Windows Server Failover Clustering
- Supported Windows Server Failover Clustering configurations
- Required software and restrictions on clustering Enterprise Vault with Windows Server Failover Clustering
- Typical Enterprise Vault configuration in a Windows Server failover cluster
- 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
- About configuring Enterprise Vault in a Windows Server failover cluster
- Setting up a new Enterprise Vault installation with Windows Server Failover Clustering support
- Configuring a new Enterprise Vault server with Windows Server Failover Clustering support
- Configuring a failover node in a Windows Server failover cluster
- Troubleshooting configuration of the Enterprise Vault Monitoring database
- 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
- About this chapter
- Enterprise Vault event messages and the failover cluster log
- Resource ownership and dependencies when configuring Enterprise Vault in a failover clustered environment
- Registry replication on failover clustered nodes
- Viewing the clustered message queues for an Enterprise Vault cluster server
- Starting and stopping Enterprise Vault services in a Windows Server Failover Clustering environment
- Potential failover issue in a Windows 2012 or later cluster
- Introducing clustering with Windows Server Failover Clustering
- Appendix A. Automatically preparing an Enterprise Vault server
Configuring a new Enterprise Vault server with Windows Server Failover Clustering support
Perform one of the following procedures on a newly installed Enterprise Vault server to configure it as an Enterprise Vault server with cluster support. Choose the appropriate procedure depending on which of the following you want to do:
Create an Enterprise Vault Directory on the Enterprise Vault server. This is mandatory for the first Enterprise Vault server you configure. The Directory is a container for Enterprise Vault Sites, which define common settings for Enterprise Vault servers. Every Enterprise Vault server must belong to just one Site. The configuration process creates a new Site in the new Directory and adds the Enterprise Vault server to that Site. It also creates a Directory database on the SQL server you specify.
Join an Enterprise Vault Directory on another Enterprise Vault server. You can add the Enterprise Vault server to an existing Enterprise Vault Site in the Directory, or create a new Site in the Directory and add the Enterprise Vault server to that.
Follow this procedure if you want to create a new Enterprise Vault Directory. You must use this procedure if there is no existing Directory.
To configure a server with a new Directory
- Use Failover Cluster Manager to ensure that a suitable cluster service that you prepared earlier is online on the Enterprise Vault server node.
- Start the Enterprise Vault Configuration wizard on the server node.
- Click Create a new Enterprise Vault server with Cluster support, and then click Next.
- The wizard lists the cluster services that are currently online on this node. Select the prepared cluster service, and then click Next.
- On the next Wizard page you can choose whether to create a new Vault Directory or to use an existing Vault Directory. Select Yes to create a new Vault Directory on this computer. This creates a new Enterprise Vault site. Click Next.
- Select the language you want Enterprise Vault to use when populating the default settings in the Administration Console. Then click Next.
- The wizard asks for details of the Vault Service account. This is the account you created earlier as part of the preinstallation tasks for Enterprise Vault. Use the format domain_name\username. Alternatively, click the ... button and browse for the account.
Enter the password details and then click Next.
The wizard then displays a couple of messages relating to the Vault Service account having been granted user rights on the computer, and the creation of the Directory Service.
- When prompted, enter the location of the SQL Server to use for the Enterprise Vault Directory database and click Next.
- The wizard prompts you to enter the locations for the Enterprise Vault Directory database and transaction log. For performance reasons it is good practice to place these on separate disks. If default locations are shown, change them if they are incorrect. If you specified a SQL server on a remote computer, the paths must be valid paths on that computer, such as
\\DC\C$\Program Files\Microsoft SQL Server\MSSQL\Data.Then click Next.
- When prompted, enter the location of the SQL Server to use for the Enterprise Vault Monitoring database. Leave Start Monitoring immediately selected to begin monitoring as soon as the configuration is complete on this Enterprise Vault server. Then click Next.
- The wizard prompts you to enter the locations for the Enterprise Vault Monitoring database and transaction log. For performance reasons it is good practice to place these on separate disks. If default locations are shown, change them if they are incorrect. If you specified a SQL server on a remote computer, the paths must be valid paths on that computer.
Then click Next.
- The wizard then prompts you for a name and description for the new Vault Site.
A Vault Site alias is created automatically. This is the client access point for the cluster service that you selected in step 4.
- Click Next to continue.
- The wizard confirms the Enterprise Vault Site and Enterprise Vault Directory computer you have selected. It prompts you to specify the Computer Alias for the computer you are currently configuring.
Enter the client access point for the Enterprise Vault cluster service that you selected in step 4, and click Next to update the Enterprise Vault Directory.
- There is a prompt that asks whether you are sure that you do not want to use a DNS alias. Click Yes and then click Next again on the wizard page.
- The wizard lists the Enterprise Vault services that are to be added to this computer. Click Next to add the services.
- The wizard lists the Enterprise Vault services that it has now added. Note that in a cluster configuration you are not allowed to add or remove services. Click Next to continue.
- The wizard shows a summary of the services it has added. Click Next to continue.
- The Configuration wizard indicates that it needs to create cluster resources for each of the Enterprise Vault services.
- The final wizard page displays a list of the actions the wizard has performed, and the results. Select Run the Enterprise Vault Administration Console and then click Finish to exit the wizard.
Note:
Do not select the option to run the Getting Started wizard.
Follow the steps below to set the path to the index metadata folder, which must be on a shared drive in the cluster. The index metadata folder is the folder in which Enterprise Vault stores indexing configuration data and reporting data.
Bring the Enterprise Vault Directory service and Admin service online.
In the left pane of the Enterprise Vault Administration Console, browse to Enterprise Vault Servers > EVServer.domain.local > Services.
In the right pane, right-click Enterprise Vault Indexing Service, and then click Properties.
On the General tab of the Service Properties dialog box, set the Index metadata location path to that of the shared drive in the cluster.
Click OK to save the change that you have made, and then restart the Indexing service.
Follow this procedure if you want to join an existing Directory. The existing Directory does not need to be in the cluster.
To configure a server and join an existing Directory
- Use Failover Cluster Manager to ensure that a suitable cluster service that you prepared earlier is online on the Enterprise Vault server node.
- Start the Enterprise Vault Configuration wizard on the Enterprise Vault server node.
- Click Create a new Enterprise Vault server with Cluster support, and then click Next.
- The wizard lists the cluster services that are currently online on this node. Select the prepared cluster service, and then click Next.
- On the next wizard page, select No to join an Enterprise Vault Directory on another Enterprise Vault server, and specify the DNS alias for the remote Enterprise Vault server.
Click Next and continue.
On the next wizard page, do one of the following:
Select the option to create a new Vault Site in the remote Enterprise Vault Directory.
Click Next and continue from step 7.
Or select the option to join an existing Vault Site in the remote Enterprise Vault Directory, and select a Vault Site from the list displayed.
Then click Next and continue from step 10.
- The wizard prompts you for a name and description for the new Vault Site.
- The vault site alias, which is created automatically when the first Enterprise Vault server is added to the site, will be the DNS alias for the remote Enterprise Vault server you specified in step 6.
- Click Next to continue.
- The wizard confirms the Enterprise Vault Site and Enterprise Vault Directory computer you have selected. It prompts you to specify the DNS Alias for the computer you are currently configuring.
- Enter the client access point of the Enterprise Vault cluster service.
- Click Next to update the Enterprise Vault Directory.
- The wizard lists the Enterprise Vault services that are to be added to this computer. Click Next to add the services.
- The wizard lists the Enterprise Vault services that it has now added, giving you the option to check their properties. Note that in a cluster configuration you are not allowed to add or remove services. Click Next to continue.
- The wizard displays the storage locations for the Indexing and Shopping services. These locations default to the first disk resource in the selected cluster service. If the locations are suitable, click Next. If you want to specify different storage locations, click Back and edit the properties of the service. The wizard displays a warning if you try to modify these to a local location such as
E:\Shopping. - The Configuration wizard indicates that it needs to create cluster resources for each of the Enterprise Vault services.
- The final wizard page displays a list of the actions the wizard has performed, and the results. Click Finish to exit the wizard.
Follow the steps below to set the path to the index metadata folder, which must be on a shared drive in the cluster. The index metadata folder is the folder in which Enterprise Vault stores indexing configuration data and reporting data.
Bring the Enterprise Vault Directory service and Admin service online.
In the left pane of the Enterprise Vault Administration Console, browse to Enterprise Vault Servers > EVServer.domain.local > Services.
In the right pane, right-click Enterprise Vault Indexing Service, and then click Properties.
On the General tab of the Service Properties dialog box, set the Index metadata location path to that of the shared drive in the cluster.
Click OK to save the change that you have made, and then restart the Indexing service.