07-20-2017 07:31 AM
The following occurs when a Hot_Catalog backup job runs:
Info 07/20/2017 08:38:51 MasterServer 0 backup job submission request (jobid=27226) for client MasterServer, policy Hot_Catalog, schedule Full
Info 07/20/2017 08:38:53 MasterServer MasterServer 27226 Backup started backup job for client MasterServer, policy Hot_Catalog, schedule Full on storage unit MasterServer-hcart2-robot-tld-0
Info 07/20/2017 08:39:36 MasterServer MasterServer 27226 begin writing backup id MasterServer_1500554332, copy 1, fragment 1, to media id TAPE0155 on drive IBM.ULTRIUM-TD4.000 (index 0)
Info 07/20/2017 08:42:02 MasterServer MasterServer 27226 Backup successfully wrote backup id MasterServer_1500554332, copy 1, fragment 1, 293309 Kbytes at 2093.898 Kbytes/sec
Info 07/20/2017 08:42:05 MasterServer MasterServer 27226 BackStat (the requested operation was successfully completed)
Error 07/20/2017 08:42:07 MasterServer 0 General Database validation failed for database NBAZDB.
Error 07/20/2017 08:42:07 MasterServer 0 General Database validation failed for database NBAZDB.
Error 07/20/2017 08:42:07 MasterServer 0 General Database validation failed for database NBDB.
Error 07/20/2017 08:42:07 MasterServer 0 General Database validation failed for database NBDB.
Info 07/20/2017 08:42:08 MasterServer MasterServer 27225 (the requested staging operation failed)
Error 07/20/2017 08:42:10 MasterServer MasterServer 27224 Backup catalog backup exited with status 2 (none of the requested files were backed up)
Info 07/20/2017 08:42:10 MasterServer MasterServer 27224 BackStat (none of the requested files were backed up)
Following commands run without error:
nbdb_admin -dba nbusql
nbdb_admin -validate NBAZDB
nbdb_admin -validate
Any suggestions?
Glen
07-20-2017 08:24 AM
Hi,
Could you check this TN? As soon as send us the bpdbm logs
https://www.veritas.com/support/en_US/article.000083214
Regards,
Thiago
07-21-2017 12:43 AM
Please tell us more about the catalog backup process - how many jobs are started?
Has the catalog backup completed successfully before?
Have you checked for sufficient space in the filesystem where NBU is installed?
I am confused about the clearly successful part of the backup to tape:
Info 07/20/2017 08:42:02 MasterServer MasterServer 27226 Backup su
And then the failed staging afterwards:
Info 07/20/2017 08:42:08 MasterServer MasterServer 27225 (the requested staging operation failed)
Catalog Backup normally consists of 4 jobs:
1. A parent job that controls and monitors the progress of the catalog backup and then 3 child jobs:
2. First child job: stages the databases to a staging area - the netbackup, bmr databases etc.
3. The second child job then backs up up the staged (dumped) databases.
4. The third child job backs up all of the files under netbackup\db area (images and configuration files)
Please try to run a manual backup of the relational databases (similar to the 1st child job that stages the relational databases):
Create a temp directory, e.g. C:\tmp
In cmd window, cd to <install_path>\NetBackup\bin\ and run:
nbdb_backup -online C:\tmp
What is the result?
For further troubleshooting, you will need bpdbm log as mentioned by @Thiago_Ribeiro.
If the folder does not exist under ...netbackup\logs, create it and restart NBU.