Please enter search query.
Search <book_title>...
Veritas NetBackup™ in Highly Available Environments Administrator's Guide
Last Published:
2021-01-01
Product(s):
NetBackup (9.0)
- About in this guide
- NetBackup protection against single points of failure
- About site disaster recovery with catalog backup and recovery
- About site loss protection with auto image and catalog replication
- About NetBackup catalog replication
- Deploying NetBackup master servers with full catalog replication
- About non-clustered NetBackup master server with catalog replication
- About globally clustered NetBackup master servers with catalog replication
- Installing and configuring a globally clustered NetBackup master server with catalog replication
- Using NetBackup to perform backups and restores in a cluster
Upgrading NetBackup master server in a non-clustered replicated 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:
Upgrading NetBackup master server in a non-clustered replicated configuration
- Suspend replication between the primary and secondary sites.
- Upgrade NetBackup on the primary site master server by following the standard upgrade procedures (refer to the NetBackup Upgrade Guide).
- Run basic backup and restore tests to confirm that the upgrade has been successful.
- Ensure that the secondary site master server is isolated from the wider network so that it cannot contact the media servers and clients when it comes online.
- Bring the secondary side master server on-line and mount the replicated catalog volume to it.
- Upgrade NetBackup on the secondary site master server following the standard upgrade procedures (refer to the NetBackup Upgrade Guide).
- Once the upgrade is complete take the secondary site master server off-line. Doing this will avoid unnecessary and potentially time consuming post processing operations on the secondary site catalog volume.
- Re-connect the secondary side master server to the wider network.
- Restart the replication process and allow the replicated volume to fully synchronize.