Recovering the entire NetBackup catalog using bprecover -wizard
The bprecover -wizard command is an alternative to using the NetBackup Administration Console wizard. You must have root (administrative) privileges to perform this procedure.
The relational database transaction log is not applied during full catalog recovery.
You must have root (administrative) privileges to perform these procedures.
You must be logged on to the master server on which you want to recover the catalog.
Note:
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.
Note:
Full catalog recovery restores the device and the media configuration information in the catalog backup. If you must configure storage devices during the recovery, Veritas recommends that you recover only the NetBackup image files.
Warning:
Do not run any client backups before you recover the NetBackup catalog.
To recover the entire catalog by using bprecover -wizard
If recovering the catalog to a new NetBackup installation, such as at a disaster recovery site, do the following:
Install NetBackup.
Configure the devices that are required for the recovery.
Add the media that are required for the recovery to the devices.
- Start NetBackup.
The following are the commands to start NetBackup:
UNIX and Linux:
/usr/openv/netbackup/bin/bp.start_all
Windows:
install_path\NetBackup\bin\bpup.exe
- The following is displayed:
Start the bprecover wizard by entering the following command:
UNIX and Linux:
/usr/openv/netBbckup/bin/admincmd/bprecover -wizard
Windows:
install_path\Veritas\NetBackup\bin\admincmd\bprecover.exe -wizard
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_FULL
If 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 the pathname is to a valid DR file, a message similar to the following is displayed:
vm2.example.com_1318222845 All media resources were located Do you want to recover the entire NetBackup catalog? (Y/N)
If the DR file or the pathname is not valid, the command-line wizard exits.
- Enter Y to continue. The following is displayed:
Do you want to startup the NetBackup relational database (NBDB) after the recovery?(Y/N)
The image file is restored to the proper image directory and the NetBackup relational databases (NBDB and optionally BMRDB) are restored and recovered.
- Enter Y or N to continue.
The following is displayed while the restore is in progress:
Catalog recovery is in progress. Please wait... Beginning recovery of NBDB. Please wait... Completed successful recovery of NBDB on vm2.example.com INF - Catalog recovery has completed. 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/Recover1318344410.log
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.
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.
When the recovery job is finished, each image file is restored to the proper image directory, and the NetBackup relational databases (NBDB and optionally BMRDB) have been restored and recovered.
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.
- Stop and restart NetBackup.
The following are the commands to stop and restart NetBackup:
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
- 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.
- If the catalog recovery is part of a server recovery procedure, complete the remaining steps in the appropriate recovery procedure.
This procedure can include the following tasks:
Importing the backups from the backup media into the catalog
Write protecting the media
Ejecting the media and setting it aside
Freezing the media