Upgrading NetBackup in clustered replication configuration
In order for global failover to work correctly, both the primary and secondary site clusters must run the same version of NetBackup. This means that both clusters must be upgraded at the same time. The upgrade process requires the replication link to be disabled and each cluster to be upgraded independently. The following steps should be followed during the upgrade process:
To upgrade a global cluster, use the following steps:
- Disable global cluster failover for the duration of the upgrade.
- Suspend replication between the primary and secondary sites.
- Ensure that the secondary side cluster is isolated from the wider network so that it cannot contact the media servers and clients when it comes on-line.
- Upgrade NetBackup on the primary site master server cluster, following the standard upgrade procedures (refer to the NetBackup Upgrade Guide).
- In case of both NetBackup CA-signed and external CA-signed certificates, you need to manually configure active and inactive nodes after DR package recovery. Certificates for the virtual name are backed up with the DR package during catalog backup.
- Run basic backup and restore tests to confirm the upgrade has been successful.
- Bring the secondary side cluster on-line and mount the replicated catalog volume to it.
- Upgrade NetBackup on the secondary site master server cluster following the standard upgrade procedures (refer to the NetBackup Upgrade Guide).
- Do the following:
- Make the secondary site cluster offline. This avoids unnecessary and potentially time consuming post processing operations on the secondary site catalog volume.
- Re-connect the secondary side cluster to the wider network.
- Restart the replication process and allow the replicated volume to fully synchronize.
- Enable global cluster failover.
- Perform a failover to the secondary side and perform basic backup and restore tests to confirm the upgrade has been successful.
- If required, fail the global cluster back to the primary side.