[Veritas-bu] Maximum mounts for an LTO-1 tape

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_01C5318A.E020B6C4
Content-Type: text/plain

For what it's worth we have LTO-2 drives (IBM) in an STK library and I set
the max usage count to 5000 for this media. Why? The only info I could find
on media usages for LTO-2 was an IBM publication on the technical specs for
LTO-2 drives and media and it stated a duty cycle of 5000 load/unload
cycles. Currently I have tapes with 300+ mounts and no sign of any problems.
Of course we do have NBU jobs that cough up an occasional read/write or
position error - but so far in almost every case the error is bogus because
further testing of the tape shows no media problem. My standard is that if a
tape spits out any hard write errors - I degaus & toss it. For read errors
I'm more tolerant, but have processes by which I track such errors by volser
so I know the history (if any) of past events. Hope this info helps...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#!/usr/steve green :: TDS storage admin :: 608.664.8210 (desk) ::
608.219.2106 (cell)
It's not that I'm so smart, it's just that I stay with problems longer.  A.
Einstein


------_=_NextPart_001_01C5318A.E020B6C4
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.2657.88">
<TITLE>RE: [Veritas-bu] Maximum mounts for an LTO-1 tape</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">For what it's worth we have LTO-2 =
drives (IBM) in an STK library and I set the max usage count to 5000 =
for this media. Why? The only info I could find on media usages for =
LTO-2 was an IBM publication on the technical specs for LTO-2 drives =
and media and it stated a duty cycle of 5000 load/unload cycles. =
Currently I have tapes with 300+ mounts and no sign of any problems. Of =
course we do have NBU jobs that cough up an occasional read/write or =
position error - but so far in almost every case the error is bogus =
because further testing of the tape shows no media problem. My standard =
is that if a tape spits out any hard write errors - I degaus &amp; toss =
it. For read errors I'm more tolerant, but have processes by which I =
track such errors by volser so I know the history (if any) of past =
events. Hope this info helps...</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D1 =
FACE=3D"Arial">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=
~~~~</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D1 FACE=3D"Arial">#!/usr/steve green =
:: TDS storage admin :: 608.664.8210 (desk) :: 608.219.2106 =
(cell)</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D1 FACE=3D"Arial">It's not that I'm =
so smart, it's just that I stay with problems longer.&nbsp; A. =
Einstein</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C5318A.E020B6C4--