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

  • Article ID:100022623
  • Modified Date:
  • Product(s):


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


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 6.5 (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 cannot be a storage server for SharedDisk storage.

3.             The host name and IP address of the old and new hardware must be the same.

4.             The version of Windows on the old and new master servers does not matter, nor does the bit count, provided they are both supported by NetBackup.  Thus a 32 bit Windows 2003 master server can be replaced by a 64 bit Windows 2008 master server provided both are running NetBackup 6.5.4.

5.             The NetBackup paths and directory structures must be the same on the old master server and new 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 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. F:\ on the old master server must be mounted as F:\ 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.  If the migration is between 32 bit Windows and 64 bit Windows and OpenStorage is used ensure that correct OpenStorage plug in used in each case (see article TECH77812, linked below).

3.             Install the same version of NetBackup on the new master as the version on the old master server.  Ensure the installation is made to the same path as the one used on the old master server  (a catalog backup made from C:\program files\veritas\netbackup cannot be restored to E:\program files\veritas\netbackup).  

Note:  Specify all the other servers in the domain when prompted because the catalog restore does not recover the registry hive containing the server list.

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.  

5. Once the catalog has been restored confirm the basic operation of NetBackup by running test backup and restore jobs.

6. If the master server is also a media server, run the device discovery wizard to update the locally presented devices and storage units.  

Note:  When using this procedure with NetBackup 6.5.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.


Related Articles

6.5 Troubleshooting Guide

Was this content helpful?

Get Support