How to setup building blocks and configure Enterprise Vault for a fail-over scenario

  • Modified Date:
  • Article ID:000029301


The following procedure should be performed on a new Enterprise Vault (EV) installation:

Before running Update Service Locations (USL)

Setting up Alias records

1. Ensure you have DNS aliases for each Enterprise Vault Server that point to the physical servers DNS A record

Berlinalias.lucern.local CNAME   BERLIN.lucern.local
Praguealias.lucern.local CNAME PRAGUE.lucern.local
Warsawalias.lucern.local CNAME WARSAW.lucern.local

BERLIN.lucern.local       A HOST
PRAGUE.lucern.local    A HOST
WARSAW.lucern.local  A HOST

2. Ensure you have a DNS alias pointing to a designated primary Enterprise Vault server

vaultsite.lucern.local CNAME Berlinalias.lucern.local

3. Check that the these records resolve correctly on each Enterprise Vault Servers, flush the dns cache if required (ipconfig /flushdns).

4. Perform the Pre installation Tasks and install Enterprise Vault version 8.0.x/9.0.x/10.0.x/11.0.x as per the EV documentation. Remember to use the alias name and not machine name when configuring EV.

5. Once all EV servers have successfully installed, complete the Post installation Tasks as per EV documentation.

6. Run Update Service Locations (USL):·
  • This function is run from a menu option on the 'Enterprise Vault Servers container in the EV Administration Console
  • Check that the Admin service is running on all EV servers in the site.  ***NOTE*** If the Admin service is not running on the server you are trying to fail over to it will not work and it will not show a message as to why it is not working.  It will trigger Event ID 10016 COM error in the Windows System event logs.  If a server fails making these services not reachable, then the DNS alias for the failed server needs to point to another server where the services are running so that USL will work after refreshing DNS on the server being pointed to.
  • (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.)
  • If a server doesn't have a Directory service, USL will create one, but not start it.

Notice that the VAC shows both computer alias and machine name for each computer. (Figure 1)

Figure 1

7. Log on using the Vault Service Account (Figure 1).

Figure 2

Once USL has completed, a summary page will be displayed. Notice that both Prague and Warsaw had Directory services already installed, but Berlin didn't.

Figure 3

8. Refresh 'Computers' node after each USL run so that it updates the changed information in the EV Administration Console.

Figure 4

The following steps need to be taken when an EV server has failed or is replaced and the services need to be moved:

1. Change DNS alias name of failed server to point to an up and running EV server.

Berlinalias.lucern.local CNAME BERLIN.lucern.local
Berlinalias.lucern.local CNAME   PRAGUE.lucern.local

2. Flush the DNS cache on server replacing the failed server
ipconfig / flushdns

3. Present the volume from the failed server to the running server and run USL and check USL summary page that the correct services have been created or moved to the desired machine.


Figure 5

4. Refresh 'Computers' node. You should now notice that the failed machine's alias is pointing to the new EV server's computer name. If this didn't work, check that the aliases can all be resolved and then re-run USL.

Figure 6

5. Check that you have DSN connections to the Directory database and all the Vault Stores. The Event log will throw errors if it has any problem connecting to these databases.


Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)