How to use catalog backup and recovery to transfer NetBackup catalogs between UNIX or Linux master servers as part of a hardware refresh

Problem

Using catalog backup and recovery to transfer NetBackup catalogs between UNIX or Linux master servers as part of a hardware refresh

Solution

It is sometimes necessary for a customer to replace the hardware they use for their master server. For example they may need to replace a 32-bit master server with a newer model 64-bit master server. In most cases this just involves replacing the existing master server with a newer machine of a similar type but a higher specification and can be accomplished without assistance from Veritas Consulting Services.

This article explains how catalog backup and recovery can be used as part of a hardware refresh process provided the following conditions are observed.

If one or more of these conditions is not met please contact Veritas Consulting Services or your Business Critical Account Manager for assistance.

1. The version of NetBackup installed on the old and new hardware must be the same release update of NetBackup (i.e. if the old master server is running NetBackup 8.1.1, install NetBackup 8.1.1 on the new master server).
2. The master server must not be a storage server for SharedDisk storage.
3. The host name of the old and new hardware must be the same.
4. The type and version of O/S on the new master server does not matter provided it supports the version of NetBackup used on the old master server. For example this procedure may be used to replace a Solaris 9 SPARC master server with a Solaris 10 X64 master server. However, use caution if any filesystem extended attributes were in use on the original master server. In such a case, it will likely be necessary that the new server be partitioned using the same filesystem type that existed on the old master server.

The following procedure should be used when replacing hardware:

1. Make a full catalog backup of the old master server and shut it down.
2. Prepare the new master server using the same host name as the old master server (ensure that the conditions stated above are met). If the master server is also a storage server for AdvancedDisk volumes ensure that the volumes are presented to the same mount points on the new master server (i.e. /disk1 on the old master server must be mounted as /disk1 on the new master server). If the old master server has access to OpenStorage and PureDisk deduplication devices ensure that the new master server can access the same devices using the same storage server name.
3. Install the same version of NetBackup on the new master as the version on the old master server (i.e. if the old master server is running NetBackup 8.1.1, install NetBackup 8.1.1 on the new master server). The same NetBackup related directories, partitions, and symbolic links should be present on the new server, so that NetBackup can be installed exactly like it is installed on the old server. If the NetBackup version is 8.1 or later, insure that a DR Installation is selected and that the DR package file is available.
4. Restore the catalog backup created from the old master server to the new master server. Details of the catalog restore process can be found in the Disaster Recovery section of the NetBackup Troubleshooting Guide. For 8.x reference: Veritas NetBackup™ Troubleshooting Guide
5. For a successful disaster recovery in all environments, you must know:
   • The location of the disaster recovery package.
     Note: See Disaster recovery packages.
   • The passphrase for that specific disaster recovery package.
     Note: If the passphrase is lost, refer to KB article http://www.veritas.com/docs/100033743 to get the host identity back.
6. Once the catalog has been restored confirm the basic operation of NetBackup by running test backup and restore jobs.
7. If the master server is also a media server, run the device discovery wizard to update the locally presented devices and storage units.
8. If the operating system has changed (for example from Solaris to AIX) run the command:
   nbemmcmd -updatehost -machinename <master server name> -machinetype master -operatingsystem <new_O/S>
   Running this command updates the operating system field in the EMM master server record to reflect the new operating system. A list of valid operating systems can be found in the on-line help for the nbemmcmd -updatehost command.