Recovering a NetBackup user-directed online catalog backup from the command line

This procedure recovers the catalog manually through the command line interface (CLI) without a Phase 1 import when the disaster recovery (DR) file is available. You must have root (administrative) privileges to perform this procedure.

Note:

Use this procedure only if you want to restore the minimal NetBackup catalog information that lets you begin to recover critical data.

To recover the user-directed online catalog from the command line interface

Verify the location of the disaster recovery files that are created from full and incremental hot catalog backups. These files can be stored in a specified path of the file system on the primary server and in email attachments to the NetBackup administrator.
Set up each primary server and media server in the same configuration as the configuration that is used during the last catalog backup. The primary server and media servers have the following same properties as the backed up catalog configuration: name, NetBackup version, operating system patch level, and path to storage devices.
Configure any devices and volumes you may need for the recovery.

Locate the latest DR image file corresponding to the backups that are used for recovery. Open the file in an editor and find values for the following:

master_server	Use the exact name that is specified in the NetBackup configuration for the primary server.
media_server	The location of the robot or disk storage unit that is used for catalog backup.
timestamp	The four most significant digits in the DR file name and six zeroes attached.
media	The location of the catalog backup media as specified by the disaster recovery file under the FRAGMENT keyword.
backup_id	Found in the DR file under BACKUP_ID.

Example:

file: Hot_Backup_1122502016_INCR

timestamp: 1122000000

Create the DR recovery directory on the primary server.

UNIX:

/usr/openv/netbackup/db/images/primary_server/timestamp/tmp

Windows:

C:\Program Files\VERITAS\NetBackup\db\images\primary_server 
\timestamp\tmp

Copy the DR file to the newly created directory.

Edit the DR file in netbackup/db/images/primary_server/timestamp/tmp as follows:
- Change the value of IMAGE_TYPE to 1.
- Change the value of TIR_INFO to 0.
- Change the value of NUM_DR_MEDIAS to 0.
- Remove ALL lines containing DR_MEDIA_REC.
If your catalog recover media is on tape, run the vmquery command to assign the media to the media server.
```
vmquery -assigntohost media timestamp primary_server
```
Example:
```
vmquery -assigntohost DL005L 1122000000 klingon
```
To recover the catalog .f file from the hot catalog backup, run a Phase II import on the media that is specified in the disaster recovery file.
```
bpimport -server primary_server -backupid backup_id
```
If your catalog backup was incremental, recover all the other catalog backup images up to and including the most recent full catalog backup.
- Open the NetBackup web UI and click Recovery. Then on the Regular recovery card click Start recovery. Or, use the Backup, Archive, and Restore client interface.
- Select NBU-Catalog as the policy type.
- Set the source client and destination client to your primary server.
- Search the backups and restore all files that are located in the following directory:
```
   install_path/netbackup/db/images/primary_server
```
- Verify that all files are restored successfully on the primary server.
Restore your critical data.
- Open the NetBackup web UI and click Recovery. Then on the Regular recovery card click Start recovery. Or, use the Backup, Archive, and Restore client interface.
- Select NBU-Catalog as the policy type.
- Set the source client and destination client to your primary server.
- (Backup, Archive, and Restore interface) Refresh the view.
- Restore the catalog backup images for each media server which requires data recovery.
- Browse for the following directory on the primary server.
```
install_path/netbackup/db/images
```
- Restore the catalog backup images for each media server which requires data recovery. Verify that your images are present by searching for them in the catalog.
Recover backup data from each media server in the previous step.
- Open the NetBackup web UI and click Recovery. Then on the Regular recovery card click Start recovery. Or, use the Backup, Archive, and Restore client interface.
- Select the policy type to match the data you want to restore.
- Set the source client and destination client to match the client that backed up the data.
- (Backup, Archive, and Restore interface) Refresh the view.
To recover the NetBackup database, run the following:
```
bprecover -r -nbdb
```
This command restores NetBackup media usage information, ensure that media containing backups are not overwritten, and restore the storage unit configuration.
You cannot recover the NetBackup database to a configuration that is not identical to the configuration on which the catalog was backed up. Instead, you must import each piece of backup media.
If your catalog recovery media is on tape, freeze the media that contains the catalog backup that is used for recovery. This action protects the media from being reused:
```
bpmedia -freeze -m media -h primary_server
```
Run bpmedialist to verify that the media is frozen.
Recover your policies and configuration data on each primary server and media server.
Before recovering NetBackup policy files, ensure that you have recovered all of your critical data, or protected the media that contains your critical data. When policy information is recovered, NetBackup starts to run the scheduled jobs that may overwrite the media that was written after the last catalog backup.
- Open the NetBackup web UI and click Recovery. Then on the Regular recovery card click Start recovery. Or, use the Backup, Archive, and Restore client interface.
- Select NBU-Catalog as the policy type.
- Set the source client and destination client to your primary server.
- For each additional server that you want to restore, set the source client and destination client to that server.
- Restore all files that are backed up by the hot catalog backup on each server.
Clean up the allowed list cache for all hosts.
Stop and restart the NetBackup services on all hosts.
After the services are restarted, renew the certificates:
- If NetBackup (or host ID-based) certificates are used in your NetBackup domain, do the following:
  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 external CA-signed certificates are used in your NetBackup domain, do the following:
  On a non-clustered setup
  UNIX:
```
/usr/openv/netbackup/bin/nbcertcmd -enrollCertificate
```
  Windows:
```
install_path\netbackup\bin\nbcertcmd -enrollCertificate
```
  On a clustered setup:
  UNIX:
```
/usr/openv/netbackup/bin/nbcertcmd -enrollCertificate -cluster
```
  Windows:
```
install_path\netbackup\bin\nbcertcmd -enrollCertificate -cluster
```
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.

Recovering a NetBackup user-directed online catalog backup from the command line

Feedback

Feedback