Maybe
mph999 can help to interpret this...
I see the following in bpdbm log:
16:57:15.360 [5572.42908] <2> image_db: Q_IMAGE_CATALOG_BACKUP
16:57:15.360 [5572.42908] <2> read_legacy_touch_file: Found E:\NetBackupDB\data\vxdbms.conf; requested from (vxdbms_conf.cpp.1528).
16:57:15.407 [5572.42908] <16> ImageCatalogBackup::executeQuery: ManageLockFile(D:\Program Files\Veritas\NetBackup\bin\catbackup.lock) failed to set lock
16:57:15.423 [5572.42908] <16> DbmOdbcConnect::commitTransaction: (-1) Cannot commit since transaction was never initiated
16:57:15.438 [5572.42908] <4> jmcomm_UpdateActionStatus: Sending status: 2520 back to parent JobID: 0
16:57:15.438 [5572.42908] <16> jmcomm_UpdateActionStatus: Invalid Parmeter
16:57:15.438 [5572.42908] <2> jmcomm_UpdateActionStatus: returning
16:57:15.438 [5572.42908] <16> image_db: error sending status back to jobmgr for job 0: 20
16:57:15.438 [5572.42908] <2> process_request: request complete: exit status 2520 Cannot trigger current catalog backup; another catalog backup in progress; query type: 160
Is there a leftover lock file (D:\Program Files\Veritas\NetBackup\bin\catbackup.lock) in place from a previous failed catalog backup?
And this is causing the last message saying that another catalog backup is already in progress?