I call it the "orphaned job bug." It's great to hear that it may have finally been addressed in 7.5.0.4!! I too have always done bpjobd -r <job id>
The only way I have been able to get rid of these in 7.1 was to bring NBU down and run "bpjobd -r <job id>" on every one. I just upgraded to 7.5.0.4 yesterday, and it seems to be much cleaner, meaning, none of these have shown up yet. I did see some empty jobs that I was able to delete as well.From: "Klebba, Don" <DonKlebba AT quickenloans DOT com>To: "veritas-bu AT mailman.eng.auburn DOT edu" <veritas-bu AT mailman.eng.auburn DOT edu>Date: 11/08/2012 12:41 PMSubject: [Veritas-bu] orphaned jobSent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu
I have a windows 2008 R2 master server running Netbackup 7.1.01. I have 1 job in the console that shows a status 50 (client process aborted), however the job state is waiting for retry. I tried cancelling the job and it never dies. I’ve rebooted the master a number of times and the job is still there. Anyone have any ideas? Thanks
| Don Klebba | Sr. SAN Engineer | x34263
|
| Desk: (313) 373-4263 | Mobile: (734) 634-7486 | Fax: (877) 380-0121 |
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
"PLEASE NOTE: The preceding information may be confidential or privileged. It only should be used or disseminated for the purpose of conducting business with Parker. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation."
