To recover the user-directed online catalog from the command line interface

1. Verify the location of the disaster recovery files that are created from Full and Incremental Hot Catalog backups. These files can be stored in a specified path of the file system on the master server and in email attachments to the NetBackup administrator.
2. Set up each master server and media server in the same configuration as the configuration that is used during the last catalog backup. The master server and media servers have the following same properties as the backed up catalog configuration: name, NetBackup version, operating system patch level, and path to storage devices.

   Configure any devices and volumes you may need for the recovery.

3. Locate the latest DR image file corresponding to the backups that are used for recovery. Open the file in an editor and find values for the following:

   master_server	Use the exact name that is specified in NetBackup configuration for the master server .
   media_server	The location of the robot or disk storage unit that is used for catalog backup.
   timestamp	The four most significant digits in the DR file name and six zeroes attached.
   media	The location of the catalog backup media as specified by the disaster recovery file under the FRAGMENT keyword.
   backup_id	Found in the DR file under BACKUP_ID.

   Example:

   file: Hot_Backup_1122502016_INCR

   timestamp: 1122000000

4. Create the DR recovery directory on the master server.

   UNIX:

   /usr/openv/netbackup/db/images/master_server/timestamp/tmp

   Windows:

   C:\Program Files\VERITAS\NetBackup\db\images\master_server 
   \timestamp\tmp

   Copy the DR file to the newly created directory.

5. Edit the DR file in netbackup/db/images/master_server/timestamp/tmp as follows:

   • Change the value of IMAGE_TYPE to 1.

   • Change the value of TIR_INFO to 0.

   • Change the value of NUM_DR_MEDIAS to 0.

   • Remove ALL lines containing DR_MEDIA_REC.

6. If your catalog recover media is on tape, run the vmquery command to assign the media to the media server.

   vmquery -assigntohost media timestamp master_server
   

   Example:

   vmquery -assigntohost DL005L 1122000000 klingon

7. To recover the catalog .f file from the hot catalog backup, run a Phase II import on the media that is specified by the disaster recovery file .

   bpimport -server master_server -backupid backup_id
   

8. If your catalog backup was incremental, recover all the other catalog backup images up to and including the most recent Full Catalog backup.

   • Open the Backup, Archive, and Restore client interface for NetBackup. Select NBU-Catalog as the policy type. Set the source clients and destination clients to your master server.

   • Search the backups and restore all files that are located in the following directory:

        install_path/netbackup/db/images/master_server
     

   • Verify that all files are restored successfully on the master server.

9. Restore your critical data by using the Backup, Archive, and Restore client interface or the command line.

   • Restore the catalog backup images for each media server which requires data recovery.

   • To restore the backup images, select NBU-Catalog as the policy type. Source and destination clients should be your master server. Refresh your view in the BAR GUI. Traverse the file system for the master server to the following:

     install_path/netbackup/db/images

     Restore the images for each configured media server. Verify that your images are present by searching for them in the catalog.

10. Recover backup data from each media server in the previous step. Change the Policy Type, Source, and Destination client to match the client that is used to back up the desired data. Select the desired files from the Backup, Archive, and Restore client interface and restore them.
11. To recover the NetBackup relational database, run the following:

    bprecover -r -nbdb

    This command restores NetBackup media usage information, ensure that media containing backups are not overwritten, and restore the storage unit configuration.

    You cannot recover the NetBackup relational database to a configuration that is not identical to the configuration on which the catalog was backed up. Instead, you must import each piece of backup media.

12. If your catalog recovery media is on tape, freeze the media that contains the catalog backup that is used for recovery. This action protects the media from being reused:

    bpmedia -freeze -m media -h master_server
    

    Run bpmedialist to verify that the media is frozen.

13. Recover your policies and configuration data on each master server and media server.

    Before recovering NetBackup policy files, ensure that you have recovered all of your critical data, or protected the media that contains your critical data. When policy information is recovered, NetBackup starts to run the scheduled jobs that may overwrite the media that was written after the last catalog backup.

    Open the Backup, Archive, and Restore client interface for NetBackup and select NBU-Catalog as the policy type.

    For each server to be restored, set the source clients and destination clients to your server, starting with the master server.

    Restore all files that are backed up by the hot catalog backup on each server.

14. Clean up allowedlist cache for all hosts.
15. Stop and restart the NetBackup services on all hosts.
16. After the services are restarted, run the following command:

    • If NetBackup (or host ID-based) certificates are used in your NetBackup domain, do the following:

      On a non-clustered setup:

      UNIX:

      /usr/openv/netbackup/bin/nbcertcmd -renewcertificate

      Windows:

      install_path\netbackup\bin\nbcertcmd -renewcertificate
      

      On a clustered setup:

      UNIX:

      /usr/openv/netbackup/bin/nbcertcmd -renewcertificate -cluster

      Windows:

      install_path\netbackup\bin\nbcertcmd -renewcertificate -cluster

    • If external CA-signed certificates are used in your NetBackup domain, do the following:

      On a non-clustered setup

      UNIX:

      /usr/openv/netbackup/bin/nbcertcmd -enrollCertificate

      Windows:

      install_path\netbackup\bin\nbcertcmd -enrollCertificate

      On a clustered setup:

      UNIX:

      /usr/openv/netbackup/bin/nbcertcmd -enrollCertificate -cluster

      Windows:

      install_path\netbackup\bin\nbcertcmd -enrollCertificate -cluster

    If the command fails with the exist status 5988, refer to the following topic:

    See Steps to carry out when you see exit status 5988 during catalog recovery.