Netbackup 7.1.0.2 with JOB state UNKNOWN

altho' I thought that issue was supposed to be fixed in 7.1.0.2?

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.
http://www.symantec.com/business/support/index?page=content&id=TECH146990

***EDIT***

Unless caused by Item 2 or 4?

FORMAL RESOLUTION:

For Item 1:  This issue is addressed in the NetBackup 7.1.0.2 maintenance update.

For Item 2:  The solution is for operators to wait a minute between restarting jobs and deletion of the original jobids.  

For Item 3:  This issue is addressed in NetBackup 7.1.0.2.

For Item 4:   Administrators should recycle the media servers when a master server is recycled.

... and we had never another, since patche aplied.

more strange than the UNKNOWN state, are the JOBS that never end, and cant be canceled.

It look like the JOB is finished, but not acknowledge, and for some reason the state in not updated, after some time (long time) it assumes the UNKNOWN state...

... it looks like Symantec does not resolved this in 7.1.0.2:

http://www.symantec.com/business/support/index?page=content&id=TECH173179

This issue is scheduled to be resolved in the following NetBackup version:

• 7.1.0.3

We are setting up new environment and notice some quirks including UNKNOWN job status so guess we'll have to wait for the latest update.

& dealt with them in the same way as the "50's"

Used something along the line of:

DOCUMENTATION: How to manually remove jobs from the NetBackup Activity Monitor which are in a queued or stopped state, and cannot be canceled, deleted, or removed by cycling the NetBackup services/daemons.
http://www.symantec.com/business/support/index?page=content&id=TECH43177

but there was another method that was posted, I'll see if I can find it.....

.... couldn't find it specifically, but turned out the command I was looking for was in the T/N that Malak posted: bpjobd -r <jobid> (but read the T/N for the full run down!)

... and everytime we need to stop server it's complicated.

This solution of:

For Windows master, when backups, restores and duplications are not running (we don't have this :( .... ), please do the following on the master server:

1. stop NetBackup (bpdown) in the default folder: C:\Program Files\VERITAS\NetBackup\bin

2. bpps, then kill the remaining NetBackup processes

3. cd to install_path\veritas\netbackup\db\jobs

4. delete the bpjobd.act.db file  (Note: For Windows 2008, uncheck 'Hide extensions for known file types')

5. cd up to the restart folder

6. delete all files

7. cd..\trylogs

8. delete all files

9. cd..\ffilelogs

10. delete all files

11. restart NetBackup (bpup) in the default folder: C:\Program Files\VERITAS\NetBackup\bin

OR

• 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.

Everytime we need to stop NetBackup services it's a real mess, We need a "online" solution or a definitive solution for this.

Wrobbins,

do you already have the 7.1.0.3 running?  Still having "UNKNOWNS"....

We've installed the 7.1.0.2 last week, but I think that .0.3 is still to recent to get into production.... I'm not that sure.

Hi

I dont know to an online solution for any version

While jobs are running you cant deal with the active jobs database and without removing that and the try jobs etc. i dont think you will get rid of them.

It is also good practice to do a weekly clean up if possible

Try and schedule in a reboot or bpdown on all servers to give you the chance to get rid of any orphaned processes - especially extra bpdbm and bpbrm processes

Bear in mind that these unknown and status 50 - waiting for retry jobs could potentiall prevent policies re-running until they have bee dealt with

Have to checked to make sure everything that should run has been running?

Hope this helps

This is a good question:

"Have to checked to make sure everything that should run has been running?"

we have arround 10.000 jobs a day, I can check if all the ones that are hang, have been rescheduled, Thank you for this reminder.

Mark, your call was really in a good time :)

Some of this JOBs were hanged for one week, and during the weekend we have the FULL policies running...

Thank you for the "heads up".

Malak