Veritas NetBackup™ in Highly Available Environments Administrator's Guide

To prepare for full catalog restore

1. On UNIX and Linux master servers, create copies of the bp.conf and vm.conf files.
2. Run the bprecover command to recover the entire catalog.

   Note:

   The DR master server must have the same name and topology as the production master server. If the production master server is a cluster then the DR master server must also be a cluster. The number of member nodes and the names of the nodes can be different.

   Note:

   If a catalog backup that was created on a separate media server is used, then a media server with the same name is required for the catalog recovery.

3. After you run the bprecover command, set a passphrase for disaster recovery package for the subsequent catalog backups to be successful.

   See Disaster recovery packages.

4. During catalog recovery, security certificates for cluster nodes are not recovered. Only the virtual name certificate is recovered.

   For successful host communication, you must deploy host name-based and host ID-based certificates on all cluster nodes after a disaster.

   For more details, refer to the Generating a certificate on a clustered master server after disaster recovery installation chapter from the NetBackup Security and Encryption Guide.

   https://www.veritas.com/docs/DOC5332

5. Deactivate all the backup policies to prevent backups from starting automatically.

   • You can do this manually using the NetBackup Adminstration Console

   • Or run the bpplinfo <policy> -modify -inactive CLI.

6. Shut down NetBackup.
7. On UNIX and Linux master servers, replace the bp.conf and the vm.conf files that were restored from the catalog backup with the copies created in step 1.
8. Start the NetBackup Relational Database Manager, NetBackup PBX, and EMM services on the new master server.

   • On UNIX and Linux master servers, run the following commands:

     • /usr/openv/netbackup/bin/nbdbms_start_stop start

     • start /opt/VRTSpbx/bin/pbx_exchange

     • /usr/openv/netbackup/bin/nbemm

   • On Windows master servers, start the following Windows services:

     • NetBackup Relational Database Manager

     • Veritas Private Branch Exchange

     • NetBackup Enterprise Media Manager

     Note:

     The PBX process may already be running because the NetBackup commands do not stop and start PBX.

     For more information about NetBackup Relational Database Manager service, see the NetBackup Troubleshooting Guide.

9. Deactivate the media servers that are not part of the DR environment. Run the following command:

   nbemmcmd -updatehost -machinename <Media Server> -machinestateop set_admin_pause -machinetype media -masterserver <Master Server>

10. Delete all the tape devices from the EMM database. Run the following command:

    nbemmcmd -deletealldevices -allrecords

11. Restart NetBackup.
12. Using the Device Configuration wizard create the new tape drive and library configuration.
13. If bar code masking rules were used at step 8, ensure that the same rules are set here. If necessary, add them.
14. Using the NetBackup Adminstration Console, verify if all the recovery media are set to non-robotic.

15. • If some recovery media still need to be set to non-robotic, do the following:

    • Select the robotic media, right-click and select Move.

    • Change the robot field to Standalone.

    • Click OK to save the changes.

16. Once all the recovery media are set to non-robotic, in the Inventory all the tape libraries field ensure that the media are identified in the correct library.