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

Issue

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 Symantec Consulting Services.

This tech note 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 Symantec 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 (e.g. if the old master server is running NetBackup 6.5.4, install NetBackup 6.5.4 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.  Note that additional steps are required when moving to or from a Red Hat Linux master server running NetBackup 6.x (i.e. all versions of NetBackup 6.0 and 6.5). These additional steps are required because of differences in the EMM database configuration between Red Hat Linux and other operating systems in NetBackup 6.x and are not required for NetBackup 7.0 and above.

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 and IP address 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 6.5.4, install NetBackup 6.5.4 on the new master server).  
4. If either the old or new master server is Red Hat Linux and the version of NetBackup is 6.x, make a copy of the file /usr/openv/var/global/server.conf on the new master server before restoring the catalog backup to it.
5. 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. 
6. If either the old or new master server is Red Hat Linux and the version of NetBackup is 6.x then, once the catalog has been restored, stop NetBackup and  replace the file /usr/openv/var/global/server.conf on the new master server with the copy created at step 4 and then restart NetBackup.
7. Once the catalog has been restored confirm the basic operation of NetBackup by running test backup and restore jobs.
8. If the master server is also a media server, run the device discovery wizard to update  the locally presented devices and storage units.
9. 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. 

Warning:  If steps 4 and 6 are missed during a move from or to Red Hat Linux on NetBackup 6.x the effect will be either that (if the new server is Red Hat Linux) the performance of nbemm will be severely impacted or (for all other Linux and UNIX operating systems) nbemm will simply fail to start.

Note:  When using this procedure with NetBackup 6.x some backup policies, particularly file system policies that use directives and run multiple data streams, the first backup that runs after the catalog has been recovered will backup all the data – even if it is an incremental backup.   This may result in backups running longer and media usage being higher than normal during that first backup period and customers should take this into account when planning a hardware refresh.  This problem does not affect environments running NetBackup 7.0 and higher versions.

Original Link: