Veritas-bu

[Veritas-bu] error code 134

2005-11-03 09:31:51
Subject: [Veritas-bu] error code 134
From: KEagle AT wilmingtontrust DOT com (Eagle, Kent)
Date: Thu, 3 Nov 2005 09:31:51 -0500
Hi Frank,

I don't think you have yet stated what NB version you're on or what OS
you're using?

We experienced jobs failing with 134's instead of 196's after upgrading
our Master & Media servers to 5.1 MP2 on Win2K. The issue was fixed by
upgrading to 5.1 MP3(It also fixed exit status 41 errors we were getting
when backing up servers that were running Legato Diskxtender). You'll
probably want to upgrade straight to 5.1 MP3A, to fix the Java
vulnerability, if this applies to you.

Good luck,

Kent C. Eagle
Systems Engineer, MCP, MCSE
Tech Services / SMSS

--__--__--

Message: 6
Subject: RE: [Veritas-bu] error code 134
Date: Wed, 2 Nov 2005 19:36:09 -0800
From: "Rockey Reed" <rockey_reed AT symantec DOT com>
To: "Penny Carr" <penelope_carr AT symantec DOT com>,
<bobby.l.walker AT lmco DOT com>,
   <Frank.H.Wooten AT l-3com DOT com>, <veritas-bu AT mailman.eng.auburn DOT 
edu>

The 134 error can be reduced if not eliminated by ensuring the shared
memory of the NBU server is set properly.  Also, you may notice 134 when
there is no storage unit readily available, meaning in use by another
backup/restore job when the backup starts; however, this should go away
when the resource becomes available.  I have noticed that the if the job
opens without a resource available and then the start window closes
before the resource becomes available you will get the 134 error instead
of the expected 196.  HTH

Thanks,
Rockey J. Reed
Sr. Solutions Specialist
Consulting Services
Symantec Corporation
www.symantec.com
-----------------------------------------------------
Office: 936.273.5021
Mobile: 832.567.0057
Fax: 214.722.0248
Email: rockey_reed AT symantec DOT com 

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Penny Carr
Sent: Wednesday, November 02, 2005 2:29 PM
To: bobby.l.walker AT lmco DOT com; Frank.H.Wooten AT l-3com DOT com;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] error code 134

You only use that parameter for 3.4.  Once 4.5 FP3 came out that
parameter is no longer valid.

Penelope

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
<veritas-bu-admin AT mailman.eng.auburn DOT edu>
To: Wooten, FH Frank (3934) @ IS <Frank.H.Wooten AT l-3com DOT com>;
veritas-bu AT mailman.eng.auburn DOT edu <veritas-bu AT mailman.eng.auburn DOT 
edu>
Sent: Wed Nov 02 13:37:28 2005
Subject: RE: [Veritas-bu] error code 134

Put a touch file named DISABLE_RESOURCES_BUSY  in /usr/openv/volmgr and
kick all the NB services.. It will stop logging it.. 

 

  _____  

From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Wooten, FH
Frank (3934) @ IS
Sent: Wednesday, November 02, 2005 1:23 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] error code 134

 

This is about to drive me crazy so hopefully someone has seen this
before. We are getting error code 134 (unable to process request because
the server resources are busy). I cannot tell if this is the server or
the network. 

 

Any help is greatly appreciated.

 

Thanks

 

Frank

 

Frank Wooten

E-mail Server Group

L-3 Integrated Systems

903-457-3934


***********************************************************************************
Investment products are not insured by the FDIC or any other governmental 
agency, are not deposits of or other obligations of or guaranteed by Wilmington 
Trust or any other bank or entity, and are subject to risks, including a 
possible loss of the principal amount invested. This e-mail and any files 
transmitted with it may contain confidential and/or proprietary information.  
It is intended solely for the use of the individual or entity who is the 
intended recipient.  Unauthorized use of this information is prohibited.  If 
you have received this in error, please contact the sender by replying to this 
message and delete this material from any system it may be on.
***********************************************************************************
~~ 




<Prev in Thread] Current Thread [Next in Thread>