[Veritas-bu] Media Write Errors, Exit Status 84

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4F342.70808451
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I've run across a similar problem.  Even with a good cleaning schedule.
The problem is you may have one or two tapes that are filthy.  Those
tapes are used by the drives which pass the dirt to another tape.  You
can try downloading "dltsage" from quantum.  It will let you test your
drives and tapes.  Good luck
=20
Best Regards,
Darby Moses
=20


________________________________

        From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
Cierkowski, Wayne
        Sent: Wednesday, January 05, 2005 9:07 AM
        To: veritas-bu AT mailman.eng.auburn DOT edu
        Subject: [Veritas-bu] Media Write Errors, Exit Status 84
=09
=09

        I'd like to get some feed back as to everyone's experience
concerning Media write errors. I have 4 sites that are almost identical,
Compaq servers, Compaq HBA's, STK L700's and SDLT320 drives. The only
difference between these sites would be number of processors in the
server, amount of memory in the server and the number of SDLT drives.
One site in particular has racked up over 182 frozen tapes since I
implemented the backup solution which is only 22 months old.=20

        =20

        First question, does 182 frozen media in only 22 months seem to
be a high rate? Media is always brand new and either Fuji or Quantum.

        =20

        STK has been working with us to try to resolve this issue and
actually gave us 120 brand new tapes last week. We pulled out all of our
existing tapes and loaded up the 120 new ones. Over the weekend we had 3
CRC's media write errors. The percentage seems kind of high.=20

        =20

        I'm running NetBackup 4.5 at the MP6 level.=20

        =20

        Is this a normal level for CRC's with SDLT?=20

        =20

        Is it the technology?=20

        =20

        Anyone else out there having similar issues?=20

        =20

        We are actually at the point of considering changing technology
to LTO drives and media. We have another small site due for replacement
and so far that seems to be the road we are taking because of the SDLT
CRC issue.=20

        =20

        Many thanks =20

        =20
        =20
        ******************************************************=20
=09
        CONFIDENTIALITY NOTICE: This E-Mail is intended only for the use
of the individual or entity to whom it is addressed and may contain
information that is privileged, confidential and exempt from disclosure
under applicable law. If you have received this communication in error,
please do not distribute and delete the original message. Please notify
the sender by E-Mail at the address shown. Thank you for your
compliance.=20


------_=_NextPart_001_01C4F342.70808451
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:eXclaimer =3D "http://www.exclaimer.co.uk"; xmlns:msxsl =3D=20
"urn:schemas-microsoft-com:xslt" xmlns:exc =3D=20
"http://www.exclaimer.co.uk/rtf";><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
        COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
        page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D651260016-05012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I've run across a similar problem.&nbsp; Even =
with a good=20
cleaning schedule.&nbsp; The problem is you may have one or two tapes =
that are=20
filthy.&nbsp; Those tapes are used by the drives which pass the dirt to =
another=20
tape.&nbsp; You can try downloading "dltsage" from quantum.&nbsp; It =
will let=20
you test your drives and tapes.&nbsp; Good luck</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Darby Moses</FONT></DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> =
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
  [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of=20
  </B>Cierkowski, Wayne<BR><B>Sent:</B> Wednesday, January 05, 2005 9:07 =

  AM<BR><B>To:</B> veritas-bu AT mailman.eng.auburn DOT 
edu<BR><B>Subject:</B>=20
  [Veritas-bu] Media Write Errors, Exit Status 84<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I&#8217;d like to get =
some feed back as=20
  to everyone&#8217;s experience concerning Media write errors. I have 4 =
sites that=20
  are almost identical, Compaq servers, Compaq HBA&#8217;s, STK =
L700&#8217;s and SDLT320=20
  drives. The only difference between these sites would be number of =
processors=20
  in the server, amount of memory in the server and the number of SDLT =
drives.=20
  One site in particular has racked up over 182 frozen tapes since I =
implemented=20
  the backup solution which is only 22 months old. </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">First question, does 182 =
frozen=20
  media in only 22 months seem to be a high rate? Media is always brand =
new and=20
  either Fuji or Quantum.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">STK has been working =
with us to=20
  try to resolve this issue and actually gave us 120 brand new tapes =
last week.=20
  We pulled out all of our existing tapes and loaded up the 120 new =
ones. Over=20
  the weekend we had 3 CRC&#8217;s media write errors. The percentage =
seems kind of=20
  high. </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I&#8217;m running =
NetBackup 4.5 at the=20
  MP6 level. </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is this a normal level =
for CRC&#8217;s=20
  with SDLT? </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is it the technology?=20
  </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Anyone else out there =
having=20
  similar issues? </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">We are actually at the =
point of=20
  considering changing technology to LTO drives and media. We have =
another small=20
  site due for replacement and so far that seems to be the road we are =
taking=20
  because of the SDLT CRC issue. </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Many thanks=20
  &nbsp;</SPAN></FONT></P></DIV></DIV>
  <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
  <DIV><FONT=20
  face=3D"Courier =
New">******************************************************</FONT>=20
  </DIV>
  <DIV><FONT face=3D"Courier New">
  <DIV style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Courier New"><FONT =
color=3Dblack=20
  size=3D2>CONFIDENTIALITY NOTICE: This E-Mail is intended only for the =
use of the=20
  individual or entity to whom it is addressed and may contain =
information that=20
  is privileged, confidential and exempt from disclosure under =
applicable law.=20
  If you have received this communication in error, please do not =
distribute and=20
  delete the original message. Please notify the sender by E-Mail at the =
address=20
  shown. Thank you for your compliance.</FONT>=20
</DIV></FONT></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4F342.70808451--