Hi all,
you will need to touch file /usr/openv/volmgr/DISABLE_RESOURCES_BUSY on the
master/media servers to resolve this issue.
Regards,
Adam
----- Original Message -----
From: "dayal singh" <dayalsd AT lycos DOT com>
To: "Marelas, Peter" <MarelP AT australia.stortek DOT com>
Cc: <Veritas-bu AT mailman.eng.auburn DOT edu>
Sent: Friday, October 19, 2001 11:41 AM
Subject: RE: [Veritas-bu] Error code 134
> Peter,
> WOnderful response. Now the question is what resources we are
talking about ? Looks like Veritas people are telling us to suppress the
warning, instead suggeting a solution(as per the technote 235839). If they
had elaborated a little on why we are getting this warning or what resources
we are running out, it would have been different.
>
> Thanx again
>
> Dayal
> --
>
> On Thu, 18 Oct 2001 23:41:39
> Marelas, Peter wrote:
> >I look at 134 as a warning, not an error.
> >
> >Its saying, at the time I attempted to run the backup I couldnt get
> >any resources, so I will issue this error (warning!) and put myself back
on
> >the queue.
> >
> >In previous versions of Netbackup you would get NO SUCH feedback.
> >Rather, the job would alot of the time sit in the mounting state until
the
> >mount
> >timeout was exceeded or a resource became available.
> >Then you would pick up the phone and ring your tape vendor.
> >
> >Question, "Why is the robot taking ages to mount a tape? Netbackup
> >says its been trying to mount a tape for 2 hours".
> >
> >Response, "Sir, the robot hasent even received a mount request".
> >
> >Question, "Why am I getting heaps of mount timeouts?"
> >
> >Response, "Sir, the robot hasent even received a mount request. A
> >mount can not timeout if it was never issued".
> >
> >So 134 I believe is a good thing. It gives you a feel of how
> >well your backup window is coping in line with the resources
> >available.
> >
> >If you implement the workaround as suggested in the
> >technote, you will end up with the old behaviour which
> >Im convinced is a bad thing.
> >
> >Regards
> >Peter Marelas
> >
> >-----Original Message-----
> >From: dayal singh [mailto:dayalsd AT lycos DOT com]
> >Sent: Thursday, 18 October 2001 1:50 AM
> >To: Veritas-bu AT mailman.eng.auburn DOT edu
> >Subject: [Veritas-bu] Error code 134
> >
> >
> >NBU GURUs,
> > I am getting error code 134 in the job monitor. "
> >Unable to process request, because server resources are busy". But it
never
> >stops the backups. This shows up whenever I do full backups. Anybody has
> >seen this error before ? This is an undocumented error code
> >
> >I appreciate y'r response
> >
> >TIA
> >
> >Dayal
> >
> >
> >Make a difference, help support the relief efforts in the U.S.
> >http://clubs.lycos.com/live/events/september11.asp
> >_______________________________________________
> >Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> >http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >_______________________________________________
> >Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> >http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
>
>
> Make a difference, help support the relief efforts in the U.S.
> http://clubs.lycos.com/live/events/september11.asp
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
|
