Veritas-bu

[Veritas-bu] Error 84

2001-04-04 12:34:14
Subject: [Veritas-bu] Error 84
From: paul.weaver AT stratech DOT com (Weaver, Paul)
Date: Wed, 4 Apr 2001 12:34:14 -0400
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_01C0BD25.15AE54C0
Content-Type: text/plain;
        charset="iso-8859-1"


I have learned recently that status 84s and 85s are not always indicative of
media/tape problems but can include problems with a media server
communicating with the drive(s).  

You might want to check the headers/labels on a few of your tapes using the
following Veritas TechNote:
(http://seer.support.veritas.com/docs/232409.htm).  I have seen an instance,
in an SAN configuration running SSO, where the labels on some tapes had been
overwritten, which caused the status 84s and 85s the next time NBU attempted
to access the tapes for backups or restores.

Paul Weaver
Sr. Systems Engineer
Strategic Technologies


-----Original Message-----
From: Dennis Dwyer [mailto:dfdwyer AT tecoenergy DOT com]
Sent: Wednesday, April 04, 2001 11:36 AM
To: charles.somogyi AT bms DOT com; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Error 84


Define excessive? I'm running NBU 3.2 on a Solaris E450 with an L11000
library and I'm having similar problems. I usually freeze the tape in
question so it won't get mounted again. When the last image has expired, I
remove the tape from service. I have replaced several drives in the library
because it appeared that the failures were always occurring on the same two
drive here lately. However, I have also noticed that 99% of my tape problems
are with Fuji tapes (I have Fuji, Quantum and Compaq). There have been a
previous conversation that indicate all DLT tapes are created equal (and by
the same manufacturer) but I'm not sure I buy that. Especially when you
consider that the reason we bought the Fuji tapes in the first place was
because they were the least expensive. If all are created equal (i.e. by the
same manufacturer) why don't they cost the same and perform the same?

Regards,
Dennis

Quote: "Time is not a test of the truth"
Translation: Just because you've always done it that way, doesn't make it
right

Dennis F. Dwyer
Enterprise Storage Manager
Tampa Electric Company

(813) 225-5181  - Voice
(813) 275-3599  - FAX

Visit our corporate website at www.tecoenergy.com

>>> Charles R Somogyi <charles.somogyi AT bms DOT com> 04/04/01 11:21AM >>>
Hello All:

Anybody get an excessive amount of 84's in their 3.2 NB on HPUX
11.00 environment? We use STK's and HP L700's. Firmware is
recent. We have 4 other environments just like this one but the
84's are non-stop in this one environment.
Easy enough fix (clean drive or replace media and rerun job) but
we have the operators running around all night fixing these 84's.

Charlie Somogyi
Bristol Myers Squibb
Princeton, NJ
609-818-3589

_______________________________________________
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

------_=_NextPart_001_01C0BD25.15AE54C0
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>RE: [Veritas-bu] Error 84</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>I have learned recently that status 84s and 85s are =
not always indicative of media/tape problems but can include problems =
with a media server communicating with the drive(s).&nbsp; </FONT></P>

<P><FONT SIZE=3D2>You might want to check the headers/labels on a few =
of your tapes using the following Veritas TechNote: (<A =
HREF=3D"http://seer.support.veritas.com/docs/232409.htm"; =
TARGET=3D"_blank">http://seer.support.veritas.com/docs/232409.htm</A>).&=
nbsp; I have seen an instance, in an SAN configuration running SSO, =
where the labels on some tapes had been overwritten, which caused the =
status 84s and 85s the next time NBU attempted to access the tapes for =
backups or restores.</FONT></P>

<P><FONT SIZE=3D2>Paul Weaver</FONT>
<BR><FONT SIZE=3D2>Sr. Systems Engineer</FONT>
<BR><FONT SIZE=3D2>Strategic Technologies</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Dennis Dwyer [<A =
HREF=3D"mailto:dfdwyer AT tecoenergy DOT com">mailto:dfdwyer AT tecoenergy DOT 
com</A>=
]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 04, 2001 11:36 AM</FONT>
<BR><FONT SIZE=3D2>To: charles.somogyi AT bms DOT com; =
veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Veritas-bu] Error 84</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Define excessive? I'm running NBU 3.2 on a Solaris =
E450 with an L11000 library and I'm having similar problems. I usually =
freeze the tape in question so it won't get mounted again. When the =
last image has expired, I remove the tape from service. I have replaced =
several drives in the library because it appeared that the failures =
were always occurring on the same two drive here lately. However, I =
have also noticed that 99% of my tape problems are with Fuji tapes (I =
have Fuji, Quantum and Compaq). There have been a previous conversation =
that indicate all DLT tapes are created equal (and by the same =
manufacturer) but I'm not sure I buy that. Especially when you consider =
that the reason we bought the Fuji tapes in the first place was because =
they were the least expensive. If all are created equal (i.e. by the =
same manufacturer) why don't they cost the same and perform the =
same?</FONT></P>

<P><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>Dennis</FONT>
</P>

<P><FONT SIZE=3D2>Quote: &quot;Time is not a test of the =
truth&quot;</FONT>
<BR><FONT SIZE=3D2>Translation: Just because you've always done it that =
way, doesn't make it right</FONT>
</P>

<P><FONT SIZE=3D2>Dennis F. Dwyer</FONT>
<BR><FONT SIZE=3D2>Enterprise Storage Manager</FONT>
<BR><FONT SIZE=3D2>Tampa Electric Company</FONT>
</P>

<P><FONT SIZE=3D2>(813) 225-5181&nbsp; - Voice</FONT>
<BR><FONT SIZE=3D2>(813) 275-3599&nbsp; - FAX</FONT>
</P>

<P><FONT SIZE=3D2>Visit our corporate website at =
www.tecoenergy.com</FONT>
</P>

<P><FONT SIZE=3D2>&gt;&gt;&gt; Charles R Somogyi =
&lt;charles.somogyi AT bms DOT com&gt; 04/04/01 11:21AM &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>Hello All:</FONT>
</P>

<P><FONT SIZE=3D2>Anybody get an excessive amount of 84's in their 3.2 =
NB on HPUX</FONT>
<BR><FONT SIZE=3D2>11.00 environment? We use STK's and HP L700's. =
Firmware is</FONT>
<BR><FONT SIZE=3D2>recent. We have 4 other environments just like this =
one but the</FONT>
<BR><FONT SIZE=3D2>84's are non-stop in this one environment.</FONT>
<BR><FONT SIZE=3D2>Easy enough fix (clean drive or replace media and =
rerun job) but</FONT>
<BR><FONT SIZE=3D2>we have the operators running around all night =
fixing these 84's.</FONT>
</P>

<P><FONT SIZE=3D2>Charlie Somogyi</FONT>
<BR><FONT SIZE=3D2>Bristol Myers Squibb</FONT>
<BR><FONT SIZE=3D2>Princeton, NJ</FONT>
<BR><FONT SIZE=3D2>609-818-3589</FONT>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu </FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0BD25.15AE54C0--

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