Video Screencast Help

Unknown job state Netbackup 7.5

Created: 09 Jan 2013 • Updated: 05 Feb 2013 | 7 comments
This issue has been solved. See solution.

We are running Windows 2008 R2 and Netbackup

Daily we get several jobs in Activity Monitor with Job State, Unknown.  Nothing in the job or anything.

We can right-click and cancel and delete them, but does anyone know why this is happening?  I thought it was some job so we deactivated all jobs, rebooted the master server and still they occur.

Discussion Filed Under:

Comments 7 CommentsJump to latest comment

Marianne's picture

Any third-party monitoring or reporting software?

Here EMC DPA was found to cause the problem:

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

policeman51's picture

yes, i saw both posts.  The problem isn't they can't be deleted, I can remove them.  I just want to know why they are happening and how to stop it.

We have NOM running, thats the only reporting sowtware.  I hope that's not 3rd party.

Marianne's picture

Please check the TN for troubleshooting steps.

NOM or OpsCenter?
You should really be using OpsCenter on same version as master server (

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Andy Welburn's picture

Same/similar to EC=50 issues, not sure if these reasons are still applicable in 7.5 (two of them certainly shouldn't be) & may or may not be relevant here:

Item 2 seemed to be the most common for us or just cancelling a (probably manual) job immediately after it had started.

Quite suprised you "can right-click and cancel and delete them" as in a lot of instances they persist & require you to follow the procedures documented (altho' you do go on to say "The problem isn't they can't be deleted" !!) - so maybe not quite the same issue here.

Just as a slight aside we do see 'ephemeral' unknown jobs appear just as a new job is starting prior to the Activity Monitor being populated with the correct information, which seems in a way to tally with Item 2 (for us at least)


Also found the following 'untidy' T/N:

Jobs goes into an Unknown Job State when job priority is changed

(Not sure if this manifests itself in the Activity Monitor and also *possibly* only relevant to & RHEL5.6)

policeman51's picture

Thanks for your reply.  The second article sounds really familiar to what is happening with us.

And I'm wondering if OpsCenter (installed on the master server) has something to do with it.