Updating service locations after failover

Article:HOWTO56905  |  Created: 2011-08-01  |  Updated: 2013-07-12  |  Article URL http://www.symantec.com/docs/HOWTO56905
Article Type
How To


Subject


Updating service locations after failover

This section describes the procedure to follow when an Enterprise Vault server that is part of a building blocks solution has failed or been replaced.

Before you use this procedure it is essential that you have configured a working building blocks solution. The failover will not work unless you have already run Update Service Locations on the correctly-configured Enterprise Vault site.

To update service locations after failover

  1. Change the DNS alias of the failed Enterprise Vault server 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 in 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 in the site.

  6. If the Update Service Locations has created any services, start them.

See Monitoring the system status


Legacy ID



v11746261_v41328148


Article URL http://www.symantec.com/docs/HOWTO56905


Terms of use for this information are found in Legal Notices