If there are jobs which appear “hung” in the NetBackup Activity Monitor, it is possible a stop and restart of the NetBackup services/daemons may not clear them. If a queued job cannot be canceled or killed, note the job ID (for the example, assume the job ID 397084), and then do the following:
1. When there are no backup or restore jobs running, stop all NetBackup services/daemons on the master server
2. Delete any files with 397084 in the name from the /usr/openv/netbackup/db/jobs/trylogs/ and /usr/openv/netbackup/db/jobs/ffilelogs/ directories on the master server (the <install_path>\veritas\netbackup\db\jobs\trylogs and <install_path>\veritas\netbackup\db\jobs\ffilelogs directories on a Windows master server).
3. Delete the /usr/openv/netbackup/db/jobs/bpjobd.act.db file (the <install_path>\veritas\netbackup\db\jobs\bpjobd.act.db file on a Windows master server)
4. Restart the NetBackup services/daemons
Because the bpjobd.act.db file contains active and queued jobs, deleting it will only remove the unwanted job, since no other jobs were running at the time that the NetBackup services/daemons were stopped. Completed jobs are stored in bpjobd.db file, so do not remove it.