> Documentation > CommCell Disaster Recovery > CommServe Recovery > CommServe LiveSync For High Availability Disaster Recovery > Managing CommServe LiveSync Setup > Verifying Disaster Readiness

Performing Test Failovers to an Isolated or Bubble Networks

You can perform a test failover to a standby CommServe host located in an isolated network from where there is no connectivity to the production environment.

Before You Begin

  • Setup the standby CommServe host in such a way that the network can be isolated, during the test failover. The network must be setup in such a way that connections to production environment, which includes the CommServe host, production MediaAgents and the production clients, can be disconnected during a test failover, and reconnected once the test failover is complete.

  • If you would like to test restores, setup a read-only MediaAgent in the isolated environment.

    To test the environment, you may also have to clone some clients or install new clients as test clients in the isolated environment.

  • To disable all other activities in the standby CommServe host. create the keepActivityDisabledPostFailover additional setting. For more information, see Disabling Activities and Schedules After a Planned Failover.

Performing Test Failovers

  1. From the production CommServe hosts, shut down the services associated with the SQL client (or Instance002).

  2. Disconnect and confirm that the standby CommServe host used for testing, has no connectivity to production environment.

  3. If using a floating CommServe name, update DNS server in the standby site to resolve Commserve DNS name to standby CommServe host. For more information, see Setting Up Failovers Using a Floating CommServe Name.

  4. From the standby CommServe host, perform unplanned failover using the Process Manager associated with the SQL client (or Instance002). For more information, see Unplanned Failovers.

  5. If necessary, perform restore operations.

Resetting Test Failovers

  1. From the standby Commserve host, shut down the services associated with the both the CommServe and SQL instance.

  2. Delete the following file in the standby CommServe host:

    ContentStore2\iDataAgent\JobResults\CommServeFailover.xml

  3. If using a floating CommServe name, remove the DNS record in the standby site that was updated to resolve the Commserve DNS name to standby CommServe host.

  4. Reconnect the standby Commserve network to the production CommServe host.

  5. From the production CommServe host, start the services associated with the SQL client (or Instance002).

  6. From the standby CommServe, verify and ensure that the services associated with the SQL client (or Instance002) is started.

Loading...