Well, at least you know the root cause ;-)

You can set the media mount timeout value.  I would suggest you don't set 
it to anything less than 30 minutes.  Longer if you can.  That will allow 
the mount request to eventually terminate (a status 52 will be generated), 
then the rest of the jobs will kick off.

HTH
-Tim

On Mon, 6 Dec 2004, Jeff McCombs wrote:

> 
>     Kinda a weird issue, since I don't think most people would experience it
> if they knew what they were doing. :) I sent a new guy out to swap tapes a
> few weeks ago from our Neo 2000 and he wasn't paying a whole lot of
> attention. He managed to pull the catalog tape out of the library and put it
> into our offsite rotation.. (ugh).
> 
>     Now that's prolly not something y'all can help with, seein as how it's
> more of an issue where Ijust need to smack someone. However one thing that I
> did notice, is that with the catalog tape being unavailable, backups hang.
> Seems that netbackup hangs forever too, and blocks on all new jobs that come
> into the system... I didn't catch this for almost 3 weeks, which is kind of
> scary if you think about it...  I didn't even get a job failure notice until
> I stoped/started the netbackup services...
> 
>     Does anyone know of a way to stop this from happening in the future? Can
> a timeout or something be set on media requests, and I just don't know where
> to look? 
>