BUG REPORT: At and unable to delete or cancel jobs that show up as ghost jobs or status 50 in the activity monitor.

  • Article ID:100006954
  • Last Published:
  • Product(s):NetBackup


This is an additional issue that has been discovered and will manifest itself similarly to some of the scenarios described in the Related Article below in the regard that the ghost jobs can't be deleted and may exit reporting status code 50 (client process aborted).


This issue is caused by a bug in the NetBackup code.  The problem is triggered by the following events:

1.  A long running backup job is started, jobid 1, and joins a new MPX group.

2.  Another backup job is added to the mpx group, jobid 2.

3.  Jobid 2  completes successfully and is removed from the activity monitor.

4.  The first jobid is canceled.  In this case bpbrm will incorrectly send the terminiation messages to jobid 2.   This will cause jobid 2 to be recreated in the database with minimal information.



The formal resolution to this issue (Etrack 2588430) is included in the following release:

  • NetBackup 7.1 Maintenance Release 3 (

More information on NetBackup is available in the Related Article linked below.

Work Around:

Ghost job Cleanup

If ghost jobs are seen, Administrators must manually remove the jobs by following the directions below:

If you have a large number of jobs to clean
• Shutdown NetBackup Master AND Media Server processes
• Verify no active NetBackup processes on the Master server
• Verify no active NetBackup processes on all Media servers
• Remove all files from the jobs directory, except “jobid”
          Windows: <install_path>\NetBackup\db\jobs
          UNIX: /usr/openv/netbackup/db/jobs
• Do not remove the “jobid” file, unless you want your job numbers to start from 1
• This procedure will cause job history to be lost in Activity Monitor.

Else, if you have few jobs to clean you may consider
• Shutdown NetBackup Master AND Media Server processes
• Verify no active NetBackup processes on the Master server
* Verify no active NetBackup processes on all Media servers
• Run bpjobd -r <jobid> for each ghost jobid.

Note:       If NetBackup Media server processes are NOT terminated,
and Media server processes for a Job remain active
and either of these workarounds are implemented,
then there is a window of opportunity for new ghost jobs to appear after restarting the NetBackup Master server.
This falls under the scenario proposed in Item 4 at the top of this document.


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.

BUG REPORT: In NetBackup 7.1, ghost job may occur that can't be deleted, and that have a state of "waiting for retry" and an "exit status 50".

Was this content helpful?

Get Support