How to clear and delete "waiting for retry" status 50 job?

Have you tried deleting the job from install_path\netbackup\db\jobs. Check the job id on console and delete it from ffilelogs, restart and trylogs folders. Restart the services.

which closely matches your issue & I'm sure I followed similar method in the early 6.5 days (or was it 5.1? sorry!)

This involves stopping netbackup & killing off any remaining processes as you state, but also deleting the pempersist file before restarting netbackup:

BUG REPORT: A parent job receives a Status 50 (client process aborted) and enters a "Waiting for Retry" state even though the child jobs have successfully completed. The parent job cannot be canceled.

I would sincerely hope that this BUG hasn't resurfaced with 6.5.5 - maybe it would still be worth that call to Symantec?

Thanks for this info; still no go though despite a full stop/restart of NetBackup Master Server processes. 

I have logged a call with Symantec

I've seen a few of these of late (under v6.5.3.1) but a full restart of the NBU Master Server processes put the job in a failed state which you could work with.

Now, under v6.5.5 nothing seems to work.  I have logged a call with Symantec

It'd be nice to see what the resolution is.

Spent a good deal of time on the phone with Symantec today going though this.

We ended up using updatedb and locate to find all occurrences of the job id file under <install_path>/netbackup/db/jobs which we then deleted and then, after making sure there were no active jobs, we stopped netbackup and then deleted the job database!  After that it was a simple matter of restarting netbackup which re-creates a nice clean empty job database.

Downside is that you loose your job monitor history so you end up with a blank screen until NBU activity kicks in.

The problem seems to be inside the (progress?) database which you can't get in to to fix.  I would contend under v6.5.3, on restart, NBU cleaned up this sort of thing automatically.  This doesn't appear to happen anymore.

I will be monitoring this and if I see this again I am able to escalate through the support specialist and provide more info this time.  The trick seems to be in my case; don't delete the job the parent job was waiting for!

Malcolm

but it'd already died it shouldn't matter! :-s

Work Around

UNIX:
netbackup stop
bp.kill_all
bpps -a
(verify all procs have exited)
 rm /usr/openv/netbackup/db/jobs/bpjobd.act.db
netbackup start

WINDOWS
bpdown -v -f
bpps
(verify all procs have exited)
del c:\Program Files\VERITAS\Netbackup\db\jobs\bpjobd.act.db
bpup -v

This will remove the jobs that were waiting for retry, active, incomplete or suspended when you stopped the server. 
It WILL NOT remove all the job history except for the fore mentioned jobs.

I did this first (with Symantec); I'm afraid it didn't work.  On restart the jobs were still there.  We had to delete the bpjobd.db file which is why we lost the history.

I use my activity monitor DB for populating an external DB for historical data.  This is not a good solution.  Does anybody know if this shows up in 7.0?