I've had the exact same problem a couple of times before -- I had to reboot
the master server to recover the ability to run restores. However, I run
NBU on Windows 2003 servers, so I have to reboot regularly anyway. I've
actually attributed it to too many simultaneous instances of the service
that manages restores at one specific time, after which even one instance
won't start properly -- the only way I can get it to return to normal is to
restart all services at the Windows level (essentially rebooting).
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <veritas-bu@mailman.eng.auburn.edu>
Sent: Monday, March 06, 2006 8:59 AM
Subject: [Veritas-bu] Third times the charm (I hope)
I have asked this question twice before with no answers so I thought I'd
try again.
How can I tell why a restore job is queued? I submit restore jobs and they
sit in the queue forever. There are plenty of tape drives, the necessary
tape is in the library. There are no pending mount requests. A restore to
the same client earlier today worked with no problem. I am at my wits end
trying to figure this out. Any feedback would be welcome, even if it is
just to let me know someone actually read this.
Regards,
Patrick Whelan
_______________________________________________
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
