Phil,
I run into this kind of thing once in awhile, although I typically see
hung jobs in a "mounting" state if there's a problem, and for some
reason my media mount timeout doesn't kill the job.  Did you experience
something similar?
 
One way to go about scripting a job would be to "bpdbjobs -report" and
grep on "Mounting".  You can get a elapsed time from the report too, and
using that time, you should be able to page out based on your threshold.
 
Just my thoughts...
 
Cheers,
Jon
 


________________________________

From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of "Koster,
Phil"
Sent: Tuesday, September 26, 2006 7:55 AM
To: veritas-bu
Subject: [Veritas-bu] Monitoring for Locked jobs


NBU 6 MP2 on Win2K Srvr.

Over the weekend, all our jobs locked up on the back up server
essentially stopping all backups beginning around 9 AM Saturday. All NBU
processes (Windows) continued to run normally which did not allow our
Nagios Monitoring system to notify us (it all seemed just fine). So my
question is, is there anything we can monitor, even if by manual script,
to let us know when jobs get hung?


Can we do like a bpdbjobs and see how long the jobs have been running
and use a script to evaluate that information? Anyone doing something
like that already?


What I am thinking is at the very least just get something that can
monitor the jobs automatically (like a once per hour check) and if the
jobs get over x hours active then it sends some e-mails out to our cell
phones and inboxes. I tried to play around with bpdbjobs last night but
ran out of time before our back ups finished. (Took to long getting the
kids to bed ;-)


Thanks.

Phil Koster
Network Administrator
City of Grand Rapids
Direct: 616-456-3136
Helpdesk: 456-3999

************************************************************************
***************************** This message has been prepared on
resources owned by the City of Grand Rapids, MI. It is subject to the
Acceptable Use Policy and Procedures of the City of Grand Rapids. The
information contained herein is confidential and is intended solely for
the addressee. Access by any other party is unauthorized without the
express written permission of the sender. If you are not the intended
recipient, please contact the sender and delete this message.
************************************************************************
*****************************
 
     This message may contain privileged and/or confidential information.  If 
you have received this e-mail in error or are not the intended recipient, you 
may not use, copy, disseminate or distribute it; do not open any attachments, 
delete it immediately from your system and notify the sender promptly by e-mail 
that you have done so.  Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060927/74f9151a/attachment.html