This is a multi-part message in MIME format.
------_=_NextPart_001_01C5514D.4FD5CAF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
=20
Use the correct tape drivers, thats the only reason other than a broke =
leader,
On the veritas install CD select addtional + tape device drivers + =
install
all netbackup drivers on all drives + ATL this will help avoid cleaning =
errors, 81, 84, 82 error or more - check your application logs - most =
people think that tape write or read error are tape related even with =
new tapes, not even close, these are mostly tape drive driver related =
- new tapes are fine for 1000 mounts, put on netbackup tape device =
drivers and all backups will run better and faster...
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
To: Paul Keating
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Sent: 5/4/2005 6:14 AM
Subject: Re: [Veritas-bu] LTO2 stuck tape
Paul Keating wrote:
> Anyone had any issues?
> =20
> back when I was using DLT7000 drives, we had the Dude from Quantum in=20
> every couple of weeks to extract a stuck tape, or reset a "swallowed=20
> leader".
> =20
> I've been using these LTO2 drives since July for testing, and since=20
> November in production, and for the first time, a drive went down and=20
> when I "upped" the drive in the GUI, it went back down.....there's a=20
> tape in the drive....can't reset the drive, powercycling the drive
does=20
> nothing...the drive is not responding.....(SAN attached to two
different=20
> servers....same message on both)
> =20
>
> Any trick for freeing the tape other than calling STK?
Paul,
Powercycling the drive has worked most of the time. If there
are red lights on the front of the drive, you need to call in
to STK to have them remove and possible replace the drive.
Once I had a tape snap the leader spindle off with 1/4 the tape
in the drive. It shredded the tape completely. I've had a few
other tapes almost snap, and had to be removed by STK. I did not
return the tapes to use.
--=20
Dan
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C5514D.4FD5CAF0
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 =
6.5.7226.0">
<TITLE>RE: [Veritas-bu] LTO2 stuck tape</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>Use the correct tape drivers, thats the only reason =
other than a broke leader,</FONT>
</P>
<P><FONT SIZE=3D2>On the veritas install CD select addtional + tape =
device drivers + install</FONT>
<BR><FONT SIZE=3D2>all netbackup drivers on all drives + ATL this will =
help avoid cleaning errors, 81, 84, 82 error or more - check your =
application logs - most people think that tape write or read error are =
tape related even with new tapes, not even close, these are =
mostly tape drive driver related - new tapes are fine for 1000 mounts, =
put on netbackup tape device drivers and all backups will run better and =
faster...</FONT></P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>To: Paul Keating</FONT>
<BR><FONT SIZE=3D2>Cc: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Sent: 5/4/2005 6:14 AM</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Veritas-bu] LTO2 stuck tape</FONT>
</P>
<P><FONT SIZE=3D2>Paul Keating wrote:</FONT>
<BR><FONT SIZE=3D2>> Anyone had any issues?</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> back when I was using DLT7000 drives, we had the =
Dude from Quantum in </FONT>
<BR><FONT SIZE=3D2>> every couple of weeks to extract a stuck tape, =
or reset a "swallowed </FONT>
<BR><FONT SIZE=3D2>> leader".</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> I've been using these LTO2 drives since July for =
testing, and since </FONT>
<BR><FONT SIZE=3D2>> November in production, and for the first time, =
a drive went down and </FONT>
<BR><FONT SIZE=3D2>> when I "upped" the drive in the GUI, =
it went back down.....there's a </FONT>
<BR><FONT SIZE=3D2>> tape in the drive....can't reset the drive, =
powercycling the drive</FONT>
<BR><FONT SIZE=3D2>does </FONT>
<BR><FONT SIZE=3D2>> nothing...the drive is not responding.....(SAN =
attached to two</FONT>
<BR><FONT SIZE=3D2>different </FONT>
<BR><FONT SIZE=3D2>> servers....same message on both)</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Any trick for freeing the tape other than =
calling STK?</FONT>
</P>
<P><FONT SIZE=3D2>Paul,</FONT>
<BR><FONT SIZE=3D2>Powercycling the drive has worked most of the =
time. If there</FONT>
<BR><FONT SIZE=3D2>are red lights on the front of the drive, you need to =
call in</FONT>
<BR><FONT SIZE=3D2>to STK to have them remove and possible replace the =
drive.</FONT>
</P>
<P><FONT SIZE=3D2>Once I had a tape snap the leader spindle off with 1/4 =
the tape</FONT>
<BR><FONT SIZE=3D2>in the drive. It shredded the tape =
completely. I've had a few</FONT>
<BR><FONT SIZE=3D2>other tapes almost snap, and had to be removed by =
STK. I did not</FONT>
<BR><FONT SIZE=3D2>return the tapes to use.</FONT>
</P>
<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Dan</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
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";>http:/=
/mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C5514D.4FD5CAF0--
|
