Recovering the NetBackup catalog image files using bprecover -wizard
The bprecover -wizard command is an alternative to using the NetBackup catalog recovery wizard.
Warning:
Do not run any client backups before you recover the NetBackup catalog.
To recover the catalog image files using bprecover -wizard
- 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
- Review the prerequisites before starting the catalog recovery.
See Prerequisites for recovering the NetBackup catalog or NetBackup catalog image files.
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.
Create symbolic links to match those in the original environment.
Start the NetBackup services on the primary server by entering the following command:
On Windows:
install_path\NetBackup\bin\bpup
On UNIX and Linux:
/usr/openv/netbackup/bin/bp.start_all
- Start the bprecover wizard by entering the following command:
bprecover -wizard
The 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. You are prompted to enter the full path name of the disaster recovery file, as follows:
Please specify the full pathname to the catalog disaster recovery file:
- Enter the fully qualified path name 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 you specified a DR file for a full backup, a message similar to the following appears:
vm2.example.com_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.example.com_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... Gathering configuration information. Waiting for the security services to start operation. Generating identity for host 'vm2.example.com_1318309224' Setting up security on target host: vm2.example.com_1318309224 nbatd is successfully configured on NetBackup Primary Server. Operation completed successfully. Completed successful recovery of NBDB in staging directory on vm2.example.com 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 Backup, Archive, and Restore user interface. 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. WRN - Local or global-level settings that you have configured on the master server before catalog recovery are overwritten. It is recommended that you re-configure the required settings after the services are 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.
- 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
.fand 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.exportdirectory.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.exportdirectory.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.exportdirectory.
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
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, Cohesity 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.
- Clean up allowed list cache for all hosts.
- Recover the host settings that you backed up in step 1. Run the following command.
./nbsetconfig sample.txt
Stop and restart NetBackup services on the primary server and other hosts, as follows:
On Windows:
install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup
On UNIX:
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
- After the services are restarted, run the following command:
If NetBackup (or host ID-based) certificates are used in your NetBackup domain, do the following:
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 external CA-signed certificates are used in your NetBackup domain, perform the following steps.
Non-clustered setup:
UNIX:
/usr/openv/netbackup/bin/nbcertcmd -enrollCertificate
Windows:
install_path\netbackup\bin\nbcertcmd -enrollCertificate
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.
- 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