Failing over to secondary master server cluster
You need to failover to the secondary master server cluster when:
All the nodes of the primary master server cluster fail.
Access to the primary 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 secondary master server cluster.
Failing over to secondary master server cluster
- Stop NetBackup on the primary master server cluster.
- Stop or reverse the replication of the catalog volume.
- If necessary, update the DNS with the new virtual IP address for the master server.
- Start NetBackup on the secondary master server cluster.
Note:
Step 1 and 2 occur automatically if the primary site fails.
In globally clustered environment the process of failing over to secondary master server can be automated. To automate the process, multiple heartbeat connections must exist between the clusters. Failure of the heartbeat network can cause the secondary master server cluster to come online while the primary master server cluster is still operational.