Failing over to an alternate primary server cluster
You must failover to the alternate primary server cluster under the following circumstances:
All the nodes of the main primary server cluster fail.
Access to the main site is denied.
The exact failover procedure can vary for different replication technologies. Refer the following procedure listing the high-level steps to failover to the alternate primary server cluster.
To fail over to an alternate primary server cluster
- Stop NetBackup on the main primary server cluster.
- Stop or reverse the replication of the catalog volume.
- If necessary, update the DNS with the new virtual IP address for the primary server.
- Start NetBackup on the alternate primary server cluster.
Note:
Steps 1 and 2 occur automatically if the main site fails.
In globally clustered environment the process of failing over to alternate primary server can be automated. To automate the process, multiple heartbeat connections must exist between the clusters. Failure of the heartbeat network can cause the alternate primary server cluster to come online while the main primary server cluster is still operational.