ADSM-L

Re: ANR1163 / 1173

2001-07-31 15:07:29
Subject: Re: ANR1163 / 1173
From: Tab Trepagnier <Tab.Trepagnier AT LAITRAM DOT COM>
Date: Tue, 31 Jul 2001 14:07:09 -0500
George,

We've had bursts of tape errors on our 3575-L18.  They had nothing to do
with cleanliness.

Two problems that afflicted our library were 1) worn drive head, and 2)
failed "analog" card in the library.  In both cases, the CE replaced the
defective card or drive and the problems went away.  Note however, that if
a tape was "garbaged" by the old equipment, on its next use the system
might have to rebuild the VCR.  Sometimes, it seems like the system logic
flips tapes to RO after doing that rebuild.  My experience is that you can
set that tape back to RW and it will work AOK.

We have three 3575s.  Don't overlook things like misalignment of the drive
and picker. That happens too, and can cause a trainwreck also.

Good luck.

Tab Trepagnier
TSM Administrator
Laitram Corporation






George Lesho <GLesho AT AFCE DOT COM>@VM.MARIST.EDU> on 07/31/2001 10:47:40 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  ANR1163 / 1173


%smers:
Early on, I learned that a bad tape in a primary storage pool had a big
effect on a secondary pool so I became cautious when resolving problems
with media. I have had problems with tapes used in my 3575L32. Over the
past year, I have had 21 tapes with excessive media errors which have had
to be removed from our inventory (out of approximately 500 tapes in the
inventory). I now do a "move data" to get what I can and then bring back
the copypool tape from vault storage (restore stgp) to fill out the
remaining data that needs to be recopied into the primary tape pool to make
it consistant with the copy tapepool. Having said that, I recently and all
at once, received errors on 11 volumes in the vault; ANR1163 / 1173
indicating that there were files on the vault versions that were unique.
After a year of operation, I had only had this problem once or twice and I
had caused it by not restoring the storage pool after partially moving the
data from a bad volume...

My question: What could or would cause this spate of errors? Could the data
base be corrupted? Many of the filesets are recent and do not correspond to
a primary copypool tape that was taken out of service due to errors... any
hints would be
appreciated.

Thanks -
George Lesho
AFC Enterprises
<Prev in Thread] Current Thread [Next in Thread>