Recovering the NetBackup catalog image files using bprecover -wizard
You must have root (administrative) privileges to perform this procedure.
You must be logged on to the master server on which you want to recover the catalog. The Catalog Recovery Wizard does not work after you perform a change server operation.
This wizard relies on the disaster recovery file that was generated during the catalog backup. The path to the disaster recovery file is specified in the catalog backup policy.
During the catalog recovery process, services may be shut down and restarted. If NetBackup is configured as a highly available application (cluster or global cluster), freeze the cluster before starting the recovery process to prevent a failover. Then unfreeze the cluster after the recovery process is complete.
Do not run any client backups before you recover the NetBackup catalog.
To recover the catalog image file using bprecover -wizard
- Start NetBackup by entering the following:
If your configuration includes an EMM server that is separate from the master server, do the following: start NetBackup on the EMM server before starting NetBackup on the master server.
- On UNIX and Linux:/usr/openv/netbackup/bin/bp.start_all
- On Windows:install_path\NetBackup\bin\bpup
- Start the bprecover wizard by entering the following command:
bprecover -wizardThe 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)
- Enter Y to continue. The following prompt appears:
Please specify the full pathname to the catalog disaster recovery file:
- 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_FULLIf 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 you specified a DR file for a full backup, a message similar to the following is displayed:
vm2.symantecs.org_1318222845 All media resources were located Do you want to recover the entire NetBackup catalog? (Y/N)If you specified a DR file for an incremental backup, a message similar to the following is displayed:
vm2.symantec.org_1318309224 All media resources were located The last catalog backup in the catalog disaster recovery file is an incremental. If no catalog backup images exist in the catalog, a PARTIAL catalog recovery will only restore the NetBackup catalog files backed up in that incremental backup. However, all of the catalog backup images up to the last full catalog backup are restored. Then you can restore the remaining NetBackup catalog files from the Backup, Archive, and Restore user interface. If catalog backup images already exist, all files that were included in the related set of catalog backups are restored. Do you want to recover the entire NetBackup catalog? (Y/N)
- Enter N to continue. The following is displayed:
A PARTIAL catalog recovery includes the images directory containing the dotf files and staging of the NetBackup relational database (NBDB) for further processing. Do you also want to include policy data?(Y/N)
- Enter Y or N to continue. The following is displayed:Do you also want to include licensing data?(Y/N)
- Enter Y or N to continue. The following is displayed:
Catalog recovery is in progress. Please wait... Completed successful recovery of NBDB in staging directory on vm2.symantecs.org This portion of the catalog recovery has completed. Because this was a PARTIAL recovery of the NetBackup catalog, any remaining files included in the catalog backup can be restored using the the Backup, Archive, and Restore user interface. The image metadata that is stored in NBDB in the staging directory can be exported using "cat_export -staging", and, imported using "cat_import". The "nbdb_unload -staging" command can be used to unload one or more database tables from NBDB in the staging directory. The "nbdb_restore -recover -staging" command can be used to replace NBDB in the data directory with the contents from the staging directory. 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/Recover1318357550.log
- When the recovery job is finished, each image file is restored to the proper image directory and the configuration files are restored. If you chose to recover the policy data and licensing data, it is restored also.
- 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, Symantec 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.
- If the catalog recovery is part of a server recovery procedure, complete the remaining steps in the appropriate recovery procedure.