There is a specific db validate log, I think that is the one that will be needed.
Hopefully, it's set up the same in Windows as Unix, so lets give this a go.
The log location should be :
It is enabled via a touch file:
Create this empty file (make sure Windows doesn't add some suffix to the filename)
You can add further detail by increasing the log level for BPDBM, this can be done in the GUI, Host Properties.
I think we could stop NBU processes and remove the file - certainly the messages make it look like it could be an issue, but looking in the code it seems that the lock file is used by 'other processes, to prevent certain operations' during a catalog backup, as opposed to stopping another catalog backup running.
Also, the nbdb_backup –online failed, which is unrelated to the lock file. So whilst not impossible that the lock file is an issue, it doesn’t appear to be, although it needs to be removed.
I would set up the db validate log as explained above, and then in <install>\veritas\netbackup\bin run NbDbAdmin (should be a GUI) and run a full DB validate. When you logintop NbDbAdmin, the passwd should be nbusql
Let's then see what is in the validate log.
Any update from your side?
Have you been able to look into enabling db validate log?
Please also tell us more about your environment.
The NBU binaries seem to be on a different drive letter (D:\) to the databases (E:\).
Is your NBU installation clustered?
Or were databases moved manually?
Is VXDBMS_NB_DATA in the registry pointing to correct location for databases?
And vxdbms.conf in same folder as NBDB.db?