Are these regular backups, or are you using database extensions? If you are,
you should know that extension jobs don't queue. They just run and fail and
run and fail and run and fail. If a drive doesn't become available pretty
soon, they just stop trying with a 134 error. We have our Exchange/database
backups start an hour before the rest of our backups so that they don't have
to compete for drives.

-----Original Message-----
From: Eduardo Camareno [mailto:eduardo AT quantumbe DOT com]
Sent: Thursday, September 25, 2003 10:30 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 134 Unable to process request because the server
resources are busy


Hello all:
I'm receiving this type of error everytime I sumit two or more schedules 
to run. I have an L25 with two drive in a SAN environment using 6 media 
server and 1 Master/media sharing the two drive, with the share storage 
option. I verify all the /etc/system tunable parameter and they look ok.

Any other ideas....?

Thanks;
Ed

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


If you have received this e-mail in error or wish to read our e-mail disclaimer 
statement and monitoring policy, please refer to 
http://www.drkw.com/disc/email/ or contact the sender.