Veritas-bu

[Veritas-bu] Failures with status code 219

2002-10-29 12:36:27
Subject: [Veritas-bu] Failures with status code 219
From: Mark.Donaldson AT experianems DOT com (Donaldson, Mark)
Date: Tue, 29 Oct 2002 10:36:27 -0700
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C27F71.B5AAD920
Content-Type: text/plain

I had this problem a lot with v3.4 during duplications, too.  The
duplication doesn't register itself well with the scheduler so the scheduler
tries to run backups unaware that the drives are taken up.  You should check
your general storage unit availability, too.

I reduced the 219's due to duplication by adding the following to bp.conf
(from a previous post):

-----------------

I decided to send a quick summary since others have told me that they were
having similar issues.  My original posting is below.

I've managed to make the error 213's go away.  

Step one: Change any classes using "Any Available" as a storage pool to
point directly to the tape pool.  The settings on the disk unit weren't
going to let it be picked anyway (it's set to on-demand only).  This seemed
to change a 213 to a 219.

Step two: Add this to the bp.conf file:
  QUEUE_ON_ERROR
  WAIT_IN_QUEUE
  TIMEOUT_IN_QUEUE = 43200

..which seems to combat the 219's by getting them to resubmit on error.

Backups seem more stable.

-Mark
-----Original Message-----
From: Koduru, Kishan [mailto:KKoduru AT ea DOT com]
Sent: Tuesday, October 29, 2002 9:09 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Failures with status code 219


All of my backups started failing with status code 219. Anyone has an idea
why? All help is appreciated. 
 
NBU 3.4
Sol 2.6
 
Thanks
Kishan

------_=_NextPart_001_01C27F71.B5AAD920
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] Failures with status code 219</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I had this problem a lot with v3.4 during =
duplications, too.&nbsp; The duplication doesn't register itself well =
with the scheduler so the scheduler tries to run backups unaware that =
the drives are taken up.&nbsp; You should check your general storage =
unit availability, too.</FONT></P>

<P><FONT SIZE=3D2>I reduced the 219's due to duplication by adding the =
following to bp.conf (from a previous post):</FONT>
</P>

<P><FONT SIZE=3D2>-----------------</FONT>
</P>

<P><FONT SIZE=3D2>I decided to send a quick summary since others have =
told me that they were having similar issues.&nbsp; My original posting =
is below.</FONT></P>

<P><FONT SIZE=3D2>I've managed to make the error 213's go away.&nbsp; =
</FONT>
</P>

<P><FONT SIZE=3D2>Step one: Change any classes using &quot;Any =
Available&quot; as a storage pool to point directly to the tape =
pool.&nbsp; The settings on the disk unit weren't going to let it be =
picked anyway (it's set to on-demand only).&nbsp; This seemed to change =
a 213 to a 219.</FONT></P>

<P><FONT SIZE=3D2>Step two: Add this to the bp.conf file:</FONT>
<BR><FONT SIZE=3D2>&nbsp; QUEUE_ON_ERROR</FONT>
<BR><FONT SIZE=3D2>&nbsp; WAIT_IN_QUEUE</FONT>
<BR><FONT SIZE=3D2>&nbsp; TIMEOUT_IN_QUEUE =3D 43200</FONT>
</P>

<P><FONT SIZE=3D2>..which seems to combat the 219's by getting them to =
resubmit on error.</FONT>
</P>

<P><FONT SIZE=3D2>Backups seem more stable.</FONT>
</P>

<P><FONT SIZE=3D2>-Mark</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Koduru, Kishan [<A =
HREF=3D"mailto:KKoduru AT ea DOT com">mailto:KKoduru AT ea DOT com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, October 29, 2002 9:09 AM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Failures with status code =
219</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>All of my backups started failing with status code =
219. Anyone has an idea why? All help is appreciated. </FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>NBU 3.4</FONT>
<BR><FONT SIZE=3D2>Sol 2.6</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Thanks</FONT>
<BR><FONT SIZE=3D2>Kishan</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C27F71.B5AAD920--

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