09-08-2015 08:27 PM
I am new to Netbackup and am running version 7.0 on Redhat Linux 5.8
My Catalog Backups are failing with a status of 2. I have performed a database consistency check and there were no errors.
Here is some output from one of the 2 jobs that were launched:
requesting resource <name-redacted>, NBU_CATALOG.MAXJOBS
granted resource <name-redacted>, NBU_CATALOG.MAXJOBS
estimated 0 kbytes needed
begin Parent job
begin Catalog Backup: Start Notify Script
started process RUNCMD (pid=10536)
ended process 0 (pid=10536)
Operation Status: 0
end Catalog Backup: Start Notify Script, elapsed time 0:00:00
begin Catalog Backup: Database Manager Query
Operation Status: 2
end Catalog Backup: Database Manager Query, elapsed time 0:00:03
begin Catalog Backup: Stop On Error
Operation Status: 0
end Catalog Backup: Stop On Error, elapsed time 0:00:00
begin Catalog Backup: End Notify Script
started process RUNCMD (pid=10552)
ended process 0 (pid=10552)
Operation Status: 0
end Catalog Backup: End Notify Script, elapsed time 0:00:00
Operation Status: 2
end Parent Job, elapsed time 0:00:03
none of the requested files were backed up (2)
=============================================================
There is a second job launched at the same time. The output from that job is:
info bpdbm (pid=10541) staging relational database files for catalog backup
info bpdbm (pid=10541) staging NBDB backup to /usr/openv/db/staging
info bpdbm (pid=10541) done staging NBDB backup to /usr/openv/db/staging
none of the requested files were backed up (2)
If you can provide locations of any log files where I could get further info, or possible solutions to the problem, I would greatly appreciate it.
09-08-2015 08:48 PM
09-09-2015 05:17 PM
OK, the nbdb_admin -validate -full shows an error:
Database validation failed for page d96a2000 of database file "/usr/openv/db/data/EMM_DATA.db"
followed by 7 other lines similar to above but with a different page number.
09-09-2015 06:57 PM
The nbdb_backup command worked successfully.
I did recently try to change the destination of the backup, but I've checked the config against a working system on another network and can't find any obvious problem.