How to configure Enterprise Vault building blocks (Update Service Locations) to implement a disaster recovery solution using Microsoft Cluster

Problem

The Update Service Locations (USL) process hangs until the Enterprise Vault services are manually stopped

Cause

Enterprise Vault Update Service Locations (building blocks) do not recognize the clustered Enterprise Vault Resource

Solution

Use Enterprise Vault building blocks (USL) with Microsoft Cluster for DR.

Before initiating USL after a failover on a DR site, ensure that:

• Only the Enterprise Vault Admin and Enterprise Vault Directory services are running on the cluster nodes.
  The Admin service needs to be running so that USL can determine the machine name and hence detect if the alias has changed. It also needs this service to check whether a single machine is represented by multiple computer aliases.
• Stop all other services (i.e. Storage, Index, Task Controller, and Shopping Services) on all cluster nodes.
• Enterprise Vault databases must be replicated or copied to the DR site.
• Ensure that you have a DNS alias pointing to the DR site Enterprise Vault server, Enterprise Vault SQL database Server, and SAN storage (used for Vault Store, Indexes).
• All services that will be failed over must already be installed on the DR Cluster and must be configured, (Index service with an empty Index location for the DR Alias that is different from the intended failover Index locations- I:\Index\DRAlias\IndexLoc1 and I:\Index\ProdAlias\IndexLoc1)
• Vault Store must be replicated or manually synced to the DR site.

To update service locations after failover, follow these steps:

1. Change the DNS alias of the failed Enterprise Vault server, Enterprise Vault SQL database Server, and SAN storage (used for Vault Store, Indexes) so that it maps to a working server. You must make this change on all the remaining servers in the Enterprise Vault site.
   The method you use to do this depends on the procedures within your organization, as follows:
   ♦ Using a host file. Update the host files on all the remaining server computers in the Enterprise Vault site.
   ♦ Using DNS zones. Update the DNS zones to reflect the new alias, and clear the DNS cache using the command line ipconfig /flushdns.
2. Start the Administration Console on any of the servers on the Enterprise Vault site.
3. In the left pane, expand the tree until the Enterprise Vault Servers container is visible.
4. Right-click the Enterprise Vault Servers container and, on the shortcut menu, click Update Service Locations.
   You are prompted for the password for the Vault Service account.
5. Enter the password for the Vault Service account and click OK.
   Enterprise Vault updates the service locations and creates new services as necessary.
   At the end of the update, a summary screen appears, listing the services on each computer on the site.
6. If the Update Service Locations has created any services, start them.
    

Scenario - Building Blocks with MSCS

Note:

Enterprise Vault Server and Enterprise Vault SQL database Server is configured using DNS alias. (For the pre-requisites for building blocks - refer to the following article: -  https://www.veritas.com/docs/000029301 )
Ensure that DNS aliases are configured for each Enterprise Vault Server, Enterprise Vault SQL database Server, and SAN storage used for Vault Store and Indexes.
Enterprise Vault is installed on Microsoft Windows clustered nodes.
The Disaster Recovery (DR) site has an additional Enterprise Vault Server in the same Enterprise Vault site installed on Microsoft Cluster.
Enterprise Vault Databases are replicated or manually synced/copied between sites.
The Vault Store & Indexes are created on a network Share (the network share must use a DNS alias) and replicated or manually synced/copied between sites.
The Enterprise Vault Storage queue location must be on a file system that is a common shared location between the associated building block servers. For important information about other requirements, see the section "Extra requirements for building blocks" in the Enterprise Vault Administrator's Guide.

Related Knowledge Base Articles

• How to set up building blocks and configure Enterprise Vault for a failover scenario in Enterprise Vault 14.2 or later
• How to setup building blocks and configure Enterprise Vault for a failover scenario in Enterprise Vault 14.1 or earlier
• Enterprise Vault™ 14.2 Administrator's Guide - Failover in a building blocks configuration