NetBackup™ Troubleshooting Guide

To recover the catalog image files using the NetBackup catalog recovery wizard

1. Run the nbgetconfig command and save the output. This output can be used after the catalog recovery to recover the host-specific information that is overwritten during the catalog recovery.

   For example:

   ./nbgetconfig > sample.txt

2. Review the prerequisites before starting the catalog recovery.

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

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

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

   • Configure the necessary recovery device in NetBackup.

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

   • Create symbolic links to match those in the original environment.

     See About NetBackup catalog recovery and symbolic links.

   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:

5. Open the NetBackup web UI.
6. At the top, click Settings > NetBackup catalog recovery.
7. 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.

8. NetBackup searches for the media that are required to recover the catalog. It then informs you of the progress and locates the necessary backup ID of the disaster recovery image. If the media is not located, NetBackup indicates 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.

9. Select Recover only NetBackup catalog image and configuration files.

   Select a Job priority if wanted and then click Next to initiate the recovery.

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

11. After the recovery completes, click Sign Out.

    Each image file is restored to the proper image directory and the configuration files are restored.

12. If you want to recover the image header information without recovering the entire NetBackup database, perform the following steps:

    • Step a - Back up the target database. Run the following command.

      nbdb_backup -online directory

      Make sure that you do not specify the staging folder as the output directory. (The staging folder contains the schema data and configuration data for the NetBackup database from the catalog backup. Image .f and configuration files are recovered to their final destinations.)

    • Step b - Recover the NetBackup database from the staging directory.

      nbdb_restore -recover -staging

    • Step c - Export the image header data that you want to import from the backup.

      For example, the following command exports export all image header data. The data is exported to the netbackup/db.export directory.

      cat_export -all

    • Step d- Recover the NetBackup database with the following command.

      nbdb_restore -recover directory

      Make sure that you specify the same directory as in step a.

    • Step e- Run the cat_import command to import the image header data that you extracted in step c.

      cat_import -all -replace_destination -delete_source

      The command does the following:

      • Imports all of the image header data in the netbackup/db.export directory.

      • Replaces any image header data that was exported that already exists in the target database.

      • Removes the image header data that resides in the netbackup/db.export directory.

    • Step f- If you recovered the catalog from a disk device, you may have to fix the disk media ID references. Run the following command:

      nbcatsync -sync_dr_file DR file path -dryrun

      Replace DR file path with the path to the catalog DR file.

    • Step g - If the result of the dry run is satisfactory, run the following command:

      nbcatsync -sync_dr_file DR file path

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 database portion of the catalog.

14. Recover the host settings that you backed up in step 1. Run the following command.

    ./nbsetconfig sample.txt

15. Stop and restart the NetBackup services on the primary server, 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

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

    On a non-clustered setup:

    Windows:

    install_path\netbackup\bin\nbcertcmd -renewcertificate

    UNIX:

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

    On a clustered setup:

    Windows:

    install_path\netbackup\bin\nbcertcmd -renewcertificate -cluster

    UNIX:

    /usr/openv/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.

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.