Veritas-bu

[Veritas-bu] Too many Error 213's - Storage Unit not Available - SUMMARY

2002-08-16 13:12:13
Subject: [Veritas-bu] Too many Error 213's - Storage Unit not Available - SUMMARY
From: Mark.Donaldson AT experianems DOT com (Donaldson, Mark)
Date: Fri, 16 Aug 2002 11:12:13 -0600
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_01C24548.10696660
Content-Type: text/plain;
        charset="iso-8859-1"

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.  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: Donaldson, Mark 
Sent: Monday, July 29, 2002 10:11 AM
Subject: Too many Error 213's - Storage Unit not Available


I get the Error 213 (Storate Unit Not Available) way too frequently.  It
often occurs on weekends, usually when my offsite duplication process is
occurring.

My best guess is that the duplication process ties up the drives in a way
different from the NB scheduler, so when the drives are busy with
duplication, the scheduled Full or Incremental is not queued, it errors out
with this error.  Can somebody comment on this?

I have two storage units built, one is an on-demand-only disk pool and the
other is my tape pool (4xDLT-7k).  This is NB 3.4.3 on Sol 2.6.  The
class/policy that has the most frequent errors is set to us "Any Available"
as a storage unit.

-Mark

-----------------------------------------------------------------------
   Mark Donaldson - Sr. Systems Engineer
   Experian - Denver Colorado
----------------------------------------------------------------------- 
        There are 10 kinds of people in this world, those
          that understand binary and those that don't. 
-----------------------------------------------------------------------

------_=_NextPart_001_01C24548.10696660
Content-Type: text/html;
        charset="iso-8859-1"
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=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Too many Error 213's - Storage Unit not Available - =
SUMMARY</TITLE>
</HEAD>
<BODY>

<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.&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>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Donaldson, Mark </FONT>
<BR><FONT SIZE=3D2>Sent: Monday, July 29, 2002 10:11 AM</FONT>
<BR><FONT SIZE=3D2>Subject: Too many Error 213's - Storage Unit not =
Available</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>I get the Error 213 (Storate Unit Not Available) way =
too frequently.&nbsp; It often occurs on weekends, usually when my =
offsite duplication process is occurring.</FONT></P>

<P><FONT SIZE=3D2>My best guess is that the duplication process ties up =
the drives in a way different from the NB scheduler, so when the drives =
are busy with duplication, the scheduled Full or Incremental is not =
queued, it errors out with this error.&nbsp; Can somebody comment on =
this?</FONT></P>

<P><FONT SIZE=3D2>I have two storage units built, one is an =
on-demand-only disk pool and the other is my tape pool =
(4xDLT-7k).&nbsp; This is NB 3.4.3 on Sol 2.6.&nbsp; The class/policy =
that has the most frequent errors is set to us &quot;Any =
Available&quot; as a storage unit.</FONT></P>

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

<P><FONT =
SIZE=3D2>---------------------------------------------------------------=
--------</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Mark Donaldson - Sr. Systems =
Engineer</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Experian - Denver Colorado</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
-------- </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; There are =
10 kinds of people in this world, those</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that =
understand binary and those that don't. </FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
--------</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C24548.10696660--

<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] Too many Error 213's - Storage Unit not Available - SUMMARY, Donaldson, Mark <=