Orphan job failed in STATUS 50 and "waiting for retry" state cannot be deleted from the NetBackup Activity Monitor

  • Article ID:100000783
  • Modified Date:
  • Product(s):

Problem

Orphan job failed in STATUS 50 and "waiting for retry" state cannot be deleted from the NetBackup Activity Monitor.

Error Message

STATUS 50
Waiting for retry

Solution

There are potentially several ways to remove an orphan job in STATUS 50 and "Waiting for retry" state from Activity Monitor.  Unfortunately, some of these methods do not work all the time.  Follow the steps below in order until the job disappears.
  1. Get the job ID from Activity Monitor or by running the following command:

      Unix: /usr/openv/netbackup/bin/admincmd/bpdbjobs -report
      Windows: <install-path>\VERITAS\NetBackup\bin\admincmd\bpdbjobs -report

  2. Run the following command to delete the orphan job:  

      Unix: /usr/openv/netbackup/bin/admincmd/bpdbjobs -delete <jobID>
      Windows: <install-path>\VERITAS\NetBackup\bin\admincmd\bpdbjobs -delete <jobID> 

  3. If the bpdbjobs -delete command does not remove the stale orphan job from Activity Monitor:

    Stop all NetBackup services on the master server at a moment when nothing is running in NetBackup:

      Unix: /usr/openv/netbackup/bin/goodies/netbackup stop
      Windows: <install-path>\VERITAS\NetBackup\bin\bpdown -v

    Delete (or move) the following file:

      Unix: /usr/openv/netbackup/db/jobs/bpjobd.act.db
      Windows: <install-path>\VERITAS\NetBackup\db\jobs\bpjobd.act.db

    Delete (or move) all the files whose names include the job ID of the orphan job in the following directory tree:

      Unix: /usr/openv/netbackup/db/jobs/
      Windows: <install-path>\VERITAS\NetBackup\db\jobs\

    Start all NetBackup services with the command:

      Unix: /usr/openv/netbackup/bin/goodies/netbackup start
      Windows: <install-path>\VERITAS\NetBackup\bin\bpup -v

    Warning: deleting the bpjobd.db file will remove ALL ENTRIES from Activity Monitor, not just the orphan job.

  4. As a last resort, if all other methods fail to remove the orphan job from Activity Monitor, run the same commands as in step 3, but delete (or move) both the  bpjobd.act.db  file and the  bpjobd.db  file.  


Related Articles

BUG REPORT: At NetBackup versions 6.5.5, 6.5.6, 7.0, 7.0.1 and 7.1, ghost jobs or numerous jobs with status 50's may be seen in the activity monitor that can't be deleted.

Was this content helpful?

Get Support