Hot catalog backup fails with "status code 2" during validation of NBAZDB

Problem

During a hot catalog backup the automatic validation of the NBAZDB may fail, causing a status code 2 for the backup. This occurs even though the checks for BMRDB and NBDB are both validated successfully.

If validation is manually disabled, the validation during a catalog backup is successful.

Error Message

The job details when this occur will be similar to the following:

The bpdbm log will show the following error:

12:02:34.068 [8528.1512] <4> validate_database: Executing D:\Applications\Basic\prg\VERITAS\NetBackupDB\Win64\dbvalid -q -fx -c "UID=dba;PWD=******;ENG=validation_eng;LINKS=shmem;START=D:\Applications\Basic\prg\VERITAS\NetBackupDB\Win64\dbeng11 -c 25M -ch 500M -cl 25M \"D:\Applications\Basic\prg\VERITAS\NetBackupDB\staging\NBAZDB.db\" -ds \"D:\Applications\Basic\prg\VERITAS\NetBackupDB\staging\""
12:02:34.645 [8528.1512] <16> validate_database: Database validation failed for database NBAZDB
12:02:34.645 [8528.1512] <4> db_error_add_to_file: Database validation failed for database NBAZDB.
12:02:34.645 [8528.1512] <4> validate_database: Exiting. rc = 11

Cause

The can be caused if the AZ_DB_PASSWORD information is missing or corrupt in the <install_path>\Veritas\NetBackupdb\data\vxdbms.conf file.

Solution

From Install_path\Veritas\Netbackup\bin

1.  Run:
nbdb_admin -dba nbusql
***This should create the missing AZ_DB_PASSWORD password line in vxdbms.conf

Note: For 8.1.x and later, this command only changes the password for NBDB and BMRDB, to change the password for NBAZDB we need to instead use command: nbdb_admin -dba <password> -dbn NBAZDB

2. Run:
nbdb_admin -validate BMRDB; nbdb_admin -validate NBAZDB; nbdb_admin -validate

***This will manually validate all databases.

3.  If the validation in #2 succeeds, attempt to run a hot catalog backup. It should complete successfully for all databases available.

Additional steps:

1. Occasionally, the NetBackup services need to stopped and restarted to allow the backup to complete successfully.

2. Check to see if multiple instances of nbproxy.exe are running on the system. They may need to be manually killed if they persist beyond a restart of the NetBackup Services.

Applies To

Windows Master servers.