To recover the entire catalog by using the Catalog Recovery Wizard

1. If NetBackup is not running, start all of the NetBackup services by entering the following:

   • On UNIX and Linux:

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

   • On Windows:

     install_path\NetBackup\bin\bpup

2. Start the NetBackup Administration Console.
3. If the catalog backup and the recovery devices are not available, do the following:

   a	Configure the necessary recovery device in NetBackup. 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: http://www.veritas.com/docs/DOC5332
   b	If the catalog backup was written to an immutable (MSDP WORM) storage server, add the storage server back to the master 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: http://www.veritas.com/docs/DOC5332

4. In the NetBackup Administration Console window, click NetBackup Management in the left pane and then Recover the catalogs in the right pane.

   The Catalog Recovery Wizard Welcome panel appears.

5. Click Next on the Welcome panel to display the Catalog Disaster Recovery File panel.
6. On the Catalog Disaster Recovery File panel, specify where the disaster recovery file is stored. You can browse to select the file or enter the full pathname to the disaster recovery file.

   In most cases, you specify the most recent disaster recovery information file available. If the most recent catalog backup is 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.)

   If some form of corruption has occurred, you may want to restore to an earlier state of the catalog.

   

   Click Next to continue. The Retrieving Disaster Recovery File panel appears

7. The wizard searches for the media that are required to recover the catalog, and Retrieving Disaster Recovery File panel informs you of the progress. It informs you if the necessary backup ID of the disaster recovery image is located. If the media is not located, the wizard lists which media is needed to update the database.
   

   If necessary, follow the wizard instructions to insert the media that is indicated and run an inventory to update the NetBackup database. The information that is displayed on this panel depends on whether the recovery is from a full backup or an incremental backup.

   When the required media sources are all found, click Next to display the Disaster Recovery Method panel.

8. By default, the Recover entire NetBackup catalog option is selected on the Disaster Recovery Method panel.
   

   Select a Job Priority if desired and then click Next to initiate the recovery of the entire NetBackup catalog. The Recovering Catalog panel appears.

9. The Recovering Catalog panel displays the progress of recovering the various catalog components, as follows:

   • NBDB database (including the EMM database)

   • BMR database (if applicable)

   • NetBackup policy files

   • Backup image files to their proper image directories

   • Other configuration files

   
   Your action depends on the outcome of the recovery, as follows:

   Not successful	Consult the log file messages for an indication of the problem. Click Cancel, fix the problem, and then run the wizard again.
   Successful	Click Next to continue to the final wizard panel.

   Caution:

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

   The following warning is displayed if the disaster recovery package passphrase is not set:

   WRN - Passphrase for the disaster recovery package is not set. You must set the passphrase for the catalog backups to be successful.

   See Disaster recovery packages.

   Do one of the following to set the passphrase:

   • In the NetBackup Administration Console, expand Security Management > Global Security Settings. In the details pane, click the Disaster Recovery tab and specify the passphrase.

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

10. On the panel that informs you that the recovery is complete, click Finish.

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 allowedlist cache on all hosts.

13. Stop and restart NetBackup services on the master server and other hosts, as follows:

    • 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

    If the NetBackup Administration Console is active on any of the hosts, the command that stops the NetBackup services shuts it down.
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.

    Recovery can include the following:

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