I get these all the time. However,
when I first put in SSO, I had an unusually high # of them, like more than 50
every night. I’m trying to remember what Veritas support had me do
to get these down to a more reasonable # and I think it was adding
SSO_SCAN_ABILITY = 9 to /usr/openv/volmgr/
erine ASent: Wednesday, March 01, 2006 12:12 PMTo:
Justin PiszczCc: veritas-bu@mailman.eng.auburn.eduSubject:
RE: [Veritas-bu] Re-queuing jobs due to busy resources(134)
What version of
NetBackup are you running?
There are some
entries you can put into bp.conf:
WAIT_IN_QUEUE =
YESQUEUE_ON_
erine ASent: Wednesday, March 01, 2006 12:12 PMTo:
Justin PiszczCc: veritas-bu@mailman.eng.auburn.eduSubject:
RE: [Veritas-bu] Re-queuing jobs due to busy resources(134)
What version of
NetBackup are you running?
There are some
entries you can put into bp.conf:
WAIT_IN_QUEUE =
YESQUEUE_ON_
Title: Message
What version of
NetBackup are you running?
There are some
entries you can put into bp.conf:
WAIT_IN_QUEUE =
YESQUEUE_ON_ERROR = YES
And there is
a touch file you can put in:
/usr/openv/volmgr/DISABLE_RESOURCES_BUSY
~Kate
-Original Message-
Title: Message
Justin
Only
time I see this is when there are no more tape drives available for Netbackup to
use (ie: 50 jobs running, all using the tape drives and 20 queueing because
resources are busy).
How
many jobs is your netbackup running concurrently when you get these
messages?
