To recover the entire catalog by using the bprecover -wizard

1. Review the prerequisites before starting the catalog recovery.

   See Prerequisites for recovering the NetBackup catalog or NetBackup catalog image files.

2. If recovering the catalog to a new NetBackup installation, such as at a disaster recovery site, do the following:

   • Install NetBackup.

   • Configure the devices that are required for the recovery.

   • Add the media that are required for the recovery to the devices.

3. Start NetBackup using the following commands.

   • UNIX and Linux:

     /usr/openv/netbackup/bin/bp.start_all

   • Windows:

     install_path\NetBackup\bin\bpup.exe

4. If the catalog backup and the recovery devices are not available, do the following:

   a	Configure the necessary recovery device in NetBackup.
   b	If the catalog backup was written to an immutable (MSDP WORM) storage server, add the storage server back to the primary server's configuration with the CLI nbdevconfig command. See the NetBackup Commands Reference Guide for more information about the command.
   c	Make available to NetBackup the media that contains the catalog backup: Inventory the robot or the disk pool, add the media for standalone drives, configure the storage server and disk pool, or so on.

   For tape storage or BasicDisk storage, see the NetBackup Administrator's Guide, Volume I. For disk storage types, see the guide that describes the option. See the following website for NetBackup documentation:

   https://support.cohesity.com/s/article/article-100040135

5. Start the bprecover wizard by entering the following command:

   • UNIX and Linux:

     /usr/openv/netBbckup/bin/admincmd/bprecover -wizard

   • Windows:

     install_path\Veritas\NetBackup\bin\admincmd\bprecover.exe -wizard

   The following is displayed:

   Welcome to the NetBackup Catalog Recovery Wizard! 
   
   Please make sure the devices and media that contain catalog 
   disaster recovery data are available
   Are you ready to continue?(Y/N)

6. Enter Y to continue. The following prompt appears:

   Please specify the full pathname to the catalog disaster recovery file:

7. Enter the fully qualified pathname to the disaster recovery file for the backup that you want to restore. For example:

   /mnt/hdd2/netbackup/dr-file/Backup-Catalog_1318222845_FULL

   If the most recent catalog backup was an incremental backup, use the disaster recovery file from the incremental backup. (There is no need to first restore the full backup and then follow with the incremental backup.) Alternately, you can recover from earlier version of the catalog.

   If the pathname is to a valid DR file, a message similar to the following is displayed:

   vm2._1318222845
   All media resources were located
   Do you want to recover the entire NetBackup catalog? (Y/N)

   If the DR file or the pathname is not valid, the command-line wizard exits.

8. Enter Y to continue. The following is displayed:

   Do you want to startup the NetBackup relational database (NBDB) after the recovery?(Y/N)

   The image file is restored to the proper image directory and the NetBackup databases (NBDB, NBAZDB, and optionally BMRDB) are restored and recovered.

9. Enter Y or N to continue.

   The following is displayed while the restore is in progress:

   Catalog recovery is in progress. Please wait...
   
   Beginning recovery of NBDB.  Please wait...
   Completed successful recovery of NBDB on vm2.
   INF - Catalog recovery has completed.
   
   WRN - NetBackup will not run scheduled backup jobs until NetBackup 
   is restarted.
   
   For more information, please review the log file:
   /usr/openv/netbackup/logs/user_ops/root/logs/Recover1318344410.log
   

   When the recovery job is finished, each image file is restored to the proper image directory, and the NetBackup databases (NBDB, NBAZDB, and optionally BMRDB) have been restored and recovered.

10. Important: After successful catalog recovery, you must set the disaster recovery package passphrase, because the passphrase is not recovered during the catalog recovery.

    Do one of the following to set the passphrase:

    • Open the web UI. At the top, click Settings > Global security. On Disaster recovery tab specify the passphrase.

    • Use the nbseccmd -drpkgpassphrase command to specify the passphrase.

11. Before you continue, be aware of the following points:

    • If you recovered the catalog from removable media, NetBackup freezes the catalog media.

    • Before you restart NetBackup, Veritas recommends that you freeze the media that contains the backups more recent than the date of the catalog from which you recovered.

    • NetBackup does not run scheduled backup jobs until you stop and then restart NetBackup.

      You can submit backup jobs manually before you stop and restart NetBackup. However, if you do not freeze the media that contains the backups more recent than the date of the catalog from which you recovered, NetBackup may overwrite that media.

12. Clean up allowed list cache on all hosts.
13. Stop and restart NetBackup services on the primary server and other hosts, as follows:

    The following are the commands to stop and restart NetBackup:

    • On UNIX and Linux:

      /usr/openv/netbackup/bin/bp.kill_all
      /usr/openv/netbackup/bin/bp.start_all

    • On Windows:

      install_path\NetBackup\bin\bpdown
      install_path\NetBackup\bin\bpup

14. 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 runs successfully, proceed with the next step.

    • 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.

      Proceed with the next step.

15. If the catalog recovery is part of a server recovery procedure, complete the remaining steps in the appropriate recovery procedure.

    This procedure can include the following tasks:

    • Importing the backups from the backup media into the catalog

    • Write protecting the media

    • Ejecting the media and setting it aside

    • Freezing the media

    Note:

    A catalog recovery changes the configuration of NetBackup back to the point in time of the catalog backup. Any change to the configuration after the point-in-time of the catalog backup (For example: changes to policies, clients, storage units) must be re-applied if those changes are desired. These changes should be re-applied before new backups are taken. If the changes are not applied, they can affect what is protected and how the protection is managed.

    As an example, a storage unit might have been modified to require the use of WORM locking on new images. If WORM locking isn't re-applied, new backups do not have the desired WORM protections.