Deleting invalid entries in NBU job monitor

This procedure should be used for jobs with Status Code 50 with "waiting for retry" or for ghost jobs, which are jobs that do not have policy, client or other details in the activity monitor and which can't be deleted by any other means.

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 cancelled or killed, note the jobid and perform the following steps:

Solaris

For Unix master, when backups, restores and duplications are not running, please do the following on the master server:

  1. Make note of the jobids that need to be deleted (for this example jobids 84838 and 106680049 will be used).
  2. Stop Netbackup on the master and media servers.
    # /usr/openv/netbackup/bin/goodies/netbackup stop
  3. Check all Netbackup processes have stopped:
    # /usr/openv/netbackup/bin/bpps -a
    If processes are still running, run
    # bp.kill_all
    If any processes are still active, manually kill them.
  4. Change directory to the jobs directory
    # cd /usr/openv/netbackup/db/jobs
  5. Remove the bpjobd.act.db
    # rm bpjobd.act.db
    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.
  6. change path to the restart directory and remove the files with the jobid's in the
    # cd restart
    # rm *84838* *106680049*
  7. change path to the trylogs directory, and remove the affected jobid's
    # cd ../trylogs
    # rm 84838.t 106680049.t
  8. change path to the ffilelogs directory and remote the correlating jobids
    # cd ../ffilelogs
    # rm 84838.f 106680049.f
  9. Restart Netbackup.
    # /usr/openv/netbackup/bin/goodies/netbackup start

Windows

For Windows master, when backups, restores and duplications are not running, please do the following on the master server

  1. Make note of the jobids that need to be deleted. For this example jobids 84838 and 106680049 will be used
  2. Stop Netbackup (bpdown) in the default folde on the master and media serversr:
    C:\> <install_path>\VERITAS\Netbackup\bin\bpdown
    It may be neccessary to run bpdown more than one time.
  3. Run bpps to verify all processes are down.
    C:\> <install_path>\VERITAS\Netbackup\bin\bpps
    If needed, stop them using the Windows Task Manager.
  4. Change to the Netbackup db/jobs folder
    C:\> cd <install_path>\VERITAS\Netbackup\db\jobs
  5. Delete the bpjobd.act.db
    del bpjobd.act.fb
    NOTE: This file may appear to be named bpjobd.act if 'Hide extensions for known file types' if checked in Windows Explorer options/
  6. Change directory to the restart folder and remove the affected jobids
    cd restart
    del *84838* *106680049*
  7. change path to the trylogs directory and remote the affected jobid's
    cd ..\trylogs
    del 84838.t 106680049.t
  8. Change path to the ffilelogs folder and remove the correlating jobid's
    cd ..\ffilelogs
    del 84883.f 106680049.f
  9. Restart Netbackup (bpup)
    <install_path>\VERITAS\Netbackup\bin\bpup

References: