Recovering the NetBackup database from a backup
You can recover the NetBackup (NBDB), NetBackup Authorization (NBAZDB), or Bare Metal Restore (BMRDB) databases from a backup. A valid database must exist before you can recover the catalog backup. Therefore, the steps that you follow to recover from a backup depend on the use case, as follows:
The database is not corrupted | If the database is available and the NetBackup Scale-Out Relational Database server is running, you do not need to create a database. Do only step 10 and step 12 in the following procedure. |
The database is corrupted | Follow all of the steps in the procedure only if the NBDB database has been corrupted or does not exist. You must create a valid, empty database, which is included in the full procedure. |
To recover the NetBackup database from a catalog backup
- If the NetBackup services are running, stop them as follows:
UNIX:
/usr/openv/netbackup/bin/bp.kill_all
Windows:
install_path\NetBackup\bin\bpdown
- Move the NBDB, NBAZDB, or BMRDB from the database directories to a temporary directory.
The following are the default locations for the database files:
install_path\NetBackupDB\data\nbdb install_path\NetBackupDB\data\nbazdb install_path\NetBackupDB\data\bmrdb /usr/openv/db/data/nbdb /usr/openv/db/data/nbazdb /usr/openv/db/data/bmrdb
- Start the NetBackup Scale-Out Relational Database server, as follows:
UNIX:
/usr/openv/netbackup/bin/nbdbms_start_stop start
Windows:
install_path\NetBackup\bin\bpup -e vrtsdbsvc_psql
- Create the database. The command that you run depends on your scenario, as follows:
Run the command from the following directory:
UNIX: /usr/openv/db/bin
Windows: install_path\NetBackup\bin
Normal scenario
create_nbdb -drop
The database was relocated or the environment is clustered
create_nbdb -data VXDBMS_NB_DATA -drop -staging VXDBMS_NB_STAGING
Obtain the values for VXDBMS_NB_DATA and VXDBMS_NB_STAGING from the
vxdbms.conffile in the temporary directory that you created in step 2.The database was relocated or the environment is clustered, and space constraints force you to create this temporary database in the final location
create_nbdb -drop -data VXDBMS_NB_DATA -staging VXDBMS_NB_STAGING
Obtain the values for the option arguments from the
vxdbms.conffile in the temporary directory that you created in step 2. - Start the NetBackup services, as follows:
UNIX:
/usr/openv/netbackup/bin/bp.start_all
Windows:
install_path\NetBackup\bin\bpup
- Load the default device protocols and settings into the NetBackup Enterprise Media Manager (EMM) database by running the following command:
UNIX:
/usr/openv/volmgr/bin/tpext -loadEMM
Windows:
install_path\Volmgr\bin\tpext -loadEMM
- If you used the nbdb_move command to relocate the NetBackup databases, recreate the directories where databases were located when you backed up the catalog. The following are the default locations into which the nbdb_move command moves the databases:
install_path\NetBackupDB\data\nbdb install_path\NetBackupDB\data\nbazdb install_path\NetBackupDB\data\bmrdb /usr/openv/db/data/nbdb /usr/openv/db/data/nbazdb /usr/openv/db/data/bmrdb
- Start the NetBackup device manager on the NetBackup primary server, as follows:
UNIX:
/usr/openv/volmgr/bin/ltid -v
Windows:
Use Windows Computer Management to start the NetBackup Device Manager service (ltid.exe).
- If the catalog backup and the recovery devices are not available, do the following:
a
Configure the necessary recovery device in NetBackup.
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:
b
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.
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:
Import the catalog backup from the media on which it resides.
See the NetBackup Administrator's Guide, Volume I:
- Recover the catalog by running the following command on the primary server:
UNIX:
/usr/openv/netbackup/bin/admincmd/bprecover -r -nbdb
Windows:
install_path\NetBackup\bin\admincmd\bprecover -r -nbdb
- Clean up allowedlist cache for all hosts.
- Stop and restart NetBackup services on the primary server and other hosts, as follows:
UNIX:
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
Windows:
install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup
- 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.