Search <book_title>...

Veritas NetBackup™ Troubleshooting Guide

Last Published: 2020-09-14

Product(s): NetBackup (8.3.0.1)

Recovering the NetBackup relational database files from staging

During a catalog backup, NetBackup copies the relational database files to the staging directory. The recovery option that restores the image files and the configuration files also restores the relational database files to the staging directory.

See About recovering the NetBackup catalog image files.

You can recover the NetBackup NBDB relational database files from the staging directory. You can also use NetBackup commands process the NBDB relational database files further.

See About processing the relational database in staging.

When the relational database is recovered from staging, NetBackup also applies the current online transaction log during the recovery. Applying the transaction log ensures that the database is as consistent as possible with the currentdb/images directory.

Two recovery procedures from the staging directory exist, as follows:

The database is not corrupted	See “To recover relational database files from staging if the database is not corrupted”.
The database is corrupted	See “To recover relational database files from staging if the database is corrupted”.

To recover relational database files from staging if the database is not corrupted

Run the following command on the master server to recover NBDB from staging:
UNIX: /usr/openv/db/bin/nbdb_restore -dbn NBDB -recover -staging
Windows: install_path\NetBackup\bin\nbdb_restore -dbn NBDB -recover -staging

Stop and restart NetBackup, 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

To recover relational database files from staging if the database is corrupted

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 *.db and *.log files from the following database file directories to a temporary directory:
UNIX: /usr/openv/db/data
Windows: C:\Program Files\Veritas\NetBackupDB\data
Configure SQL Anywhere so that it does not try to start automatically when the host is started, as follows:
Linux: /usr/openv/db/bin/nbdb_admin -auto_start NONE
Windows: install_path\NetBackup\bin\nbdb_admin -auto_start NONE
Start the SQL Anywhere server, as follows:
UNIX: /usr/openv/netbackup/bin/nbdbms_start_stop start
Windows: install_path\NetBackup\bin\bpup -e SQLANYs_VERITAS_NB
Create an empty database, as follows:
UNIX: /usr/openv/db/bin/create_nbdb -drop
Windows: install_path\NetBackup\bin\create_nbdb -drop

Stop and restart NetBackup, as follows:

UNIX and Linux:

/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

Run the NetBackup tpext command to update the device mapping files, as follows:
UNIX: /usr/openv/volmgr/bin/tpext -loadEMM
Windows: install_path\Volmgr\bin\tpext -loadEMM
If you used the nbdb_move command to relocate NetBackup database files, re-create the directories where the files were located when you backed up the catalog.
Start the NetBackup Device Manager, as follows:
UNIX: /usr/openv/volmgr/bin/ltid -v
Windows: Start the device manager service.
Run the following command on the master server to recover NBDB from staging:
UNIX: /usr/openv/db/bin/nbdb_restore -dbn NBDB -recover -staging
Windows: install_path\NetBackup\bin\nbdb_restore -dbn NBDB -recover -staging
Clean up whitelist cache for all hosts.

Stop and restart NetBackup services on all 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, 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:
  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.