Upgrading a globally clustered (GCO) NetBackup master server to NetBackup 7.5

Article:HOWTO73064  |  Created: 2012-02-13  |  Updated: 2013-06-03  |  Article URL http://www.symantec.com/docs/HOWTO73064
Article Type
How To

Product(s)


A globally clustered master server consists of two master server cluster that use the same virtual host name with a replicating storage layer between them.  (Refer to the NetBackup Highly Available Environments Administrator's Guide for more details on global clusters.)  The two clusters that make up the global cluster are referred to as the primary site cluster and the secondary site cluster.  The primary site cluster is the one where the master server normally runs, and the secondary site cluster is the standby cluster which is only bought on-line when there is a problem at the primary site. 

The standard upgrade procedure for a global cluster is to upgrade the primary site cluster first and then the secondary site cluster.

An upgrade to NetBackup 7.5 involves a migration of all backup image metadata to the NetBackup relational database (NBDB).  Before you begin your upgrade, please refer to the NetBackup 7.5 Upgrade Guide for important planning information and migration method descriptions.

Upgrading NetBackup in the primary and the secondary master server cluster follows procedures that are outlined in the NetBackup installation guides and the NetBackup Clustered Master Server Administrator's Guide. For the upgrade to NetBackup 7.5, there are some additional steps for global clusters that are detailed in this document.

Note: The clusters at both sites must be upgraded at the same time because NetBackup will not start in a fail over situation if the secondary site is not running NetBackup 7.5.

Note: Symantec recommends always upgrading to the latest available release of NetBackup to ensure you have access to the latest features and bug fixes. 

 

Upgrading NetBackup in clustered replication configuration on Unix and Linux

On UNIX and Linux platforms, all nodes on the secondary master server cluster are considered to be passive during upgrade. 

 

To upgrade a UNIX or Linux global cluster

  1. Ensure that global cluster fail over is disabled for the duration of the upgrade.

  2. Suspend replication between the primary and secondary sites.

  3. Upgrade NetBackup on the primary site master server cluster first, following the standard upgrade procedures (refer to the NetBackup 7.5 Upgrade Guide).

  4. Ensure that the phase 1 and phase 2 image metadata migration processes have completed successfully before proceeding to upgrade the secondary site master server cluster.

  5. Restart the replication between the primary and secondary sites and re-enable the global cluster fail over. Be sure to take extreme care when re-establishing the replication link to ensure that the synchronization occurs in the correct direction (from the primary site to the secondary site).

 

Upgrading NetBackup in clustered replication configuration on Windows

On Windows, at least one node of the cluster must be active at the time of the upgrade. Unlike UNIX and Linux configurations, the secondary site cluster must be brought on-line for the upgrade to proceed.

Note: A problem has been identified in the Windows installer for NetBackup 7.5 which may result in upgrades of globally clustered master server failing. An Emergency Engineering Binary (EEB) has been developed to address this problem. Please obtain this fix by reviewing the link to document TECH185933 from the Related Articles section of this document.

To upgrade a Windows primary master server cluster

  1. Ensure that global cluster fail over is disabled for the duration of the upgrade.

  2. Suspend replication between the primary and secondary sites

  3. Upgrade NetBackup on the primary site master server cluster first, following the standard upgrade procedures (refer to the NetBackup 7.5 Upgrade Guide).

  4. Ensure that the phase 1 and phase 2 image metadata migration processes have completed successfully before proceeding to upgrade the secondary cluster.

  5. To update the secondary cluster, isolate the secondary master server cluster from the rest of the network. 

  6. Present the upgrade volume to the appropriate mount point. If no upgrade volume is available, see the note following this procedure.

  7. Upgrade NetBackup using the standard upgrade procedures in the NetBackup installation guides. 

  8. Stop NetBackup.

  9. Dismount the upgrade volume.
  10. Reconnect the secondary master server cluster to the rest of the network.

  11. Restart the replication between the primary and secondary sites and re-enable the global cluster fail over. Be sure to take extreme care when re-establishing the replication link to ensure that the synchronization occurs in the correct direction (from the primary site to the secondary site).

Note: If no upgrade volume is available, consider using the following approach during the upgrade:

  • Before upgrading the primary cluster, stop the replication between the primary and secondary clusters so that the target volume can be mounted to the secondary cluster (refer to your replication documentation).

  • At step 5 of the upgrade procedure, present the replication target volume to the secondary cluster as the upgrade volume. 

 




Article URL http://www.symantec.com/docs/HOWTO73064


Terms of use for this information are found in Legal Notices