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. Sign into the primary server on which you want to recovery the catalog. You must have root (administrative) privileges.

   The Catalog Recovery Wizard does not work when you connect to a primary server through a change server operation.

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

   • 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

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

   • Make the media that contains the catalog backup available to NetBackup: 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.

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

5. In the left pane, click NetBackup Management. Then in the right pane click Recover the catalogs.

   Note:

   This wizard is also available on the NetBackup web UI. To recover the catalogs, on the top right, click Settings > NetBackup Catalog Recovery or on the left pane, select Recovery, and then NetBackup Catalog Recovery.

6. Click Next.
7. 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.

   Note:

   On the NetBackup web UI, the disaster recovery file must be available on the local computer from where you launch the NetBackup Catalog Recovery Wizard.

   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.

8. NetBackup searches for the media that are required to recover the catalog. It then informs you of the progress and if it locates the necessary backup ID of the disaster recovery image. If the media is not located, NetBackup which media is needed to update the database.
   

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

   When all the required media sources are found, click Next.

9. By default, the Recover entire NetBackup catalog option is selected.
   

   Select a Job Priority if desired and then click Next to initiate the recovery of the entire NetBackup catalog.

   Note:

   Unlike in the NetBackup Administration Console, you may click Cancel to terminate the NetBackup catalog recovery process on the NetBackup web UI.

10. The Recovering Catalog panel displays the progress of the recovery of the various catalog components:

    • NBDB database (including the EMM database)

    • BMR database (if applicable)

    • NetBackup policy files

    • Backup image files to their proper image directories

    • Other configuration files

    
    Note that the relational database transaction log is not applied during full catalog recovery.

    Note:

    You can monitor the Catalog recovery progress under Recovery Status screen of catalog recovery workflow.

    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.

11. After the recovery completes, click Finish.
12. Important: After successful catalog recovery, you must set the disaster recovery package passphrase. The passphrase is not recovered during the catalog recovery.

    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.

    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.

13. 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, 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, you must freeze the media that contains the backups more recent than the date of the catalog from which you recovered. Otherwise, NetBackup may overwrite that media.

14. Clean up the allowed list cache on all hosts.

15. Stop and restart NetBackup services on the primary 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.
16. After the services are restarted, run one of the following commands:

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

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