Veritas NetBackup™ Troubleshooting Guide

To recover the catalog image files 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. 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:
   b	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:
   c	Create symbolic links to match those in the original environment. See About NetBackup catalog recovery and symbolic links.

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

4. Click Next on the Welcome panel to display the Catalog Disaster Recovery File panel.
5. 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.

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

   The Disaster Recovery Method panel appears.

7. On the Disaster Recovery Method panel, do the following:

   • Select Recover only NetBackup catalog image and configuration files.

   • Specify a job priority.

   To continue, click Next.

   The Recovering Catalog panel appears.

8. The Recovering Catalog panel displays the recovery progress.

   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.

9. On the final wizard panel, click Finish

   When the recovery job is finished, each image file is restored to the proper image directory and the configuration files are restored.

10. Export the image metadata from the relational database in the staging directory, as follows:

    cat_export -all -staging -source_master source-master-server-name

    The export is required so that the image metadata can be imported into the relational database. A catalog image file recovery does not recover the relational database.

11. Import the image metadata into the relational database, as follows:

    cat_import -all -replace_destination

12. If you recovered the catalog from a disk device, you may have to fix the disk media ID references in the image headers. The image headers were recovered from the catalog backup.

    To fix the disk media IDs in the image headers, run the following command:

    nbcatsync -backupid image_id -dryrun

    Replace image_id with the ID of the catalog backup. You can find the image ID of the catalog backup by examining the DR file.

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

    • Because this operation is a partial recovery, you must recover the relational database portion of the catalog.

14. Stop and restart NetBackup on all the servers, 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

15. After the services are restarted, run the following command:

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

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