I had already tried that.  When I do an Audit Library, those 15 tapes get
dropped from the inventory since they can't be found.  But then I can do a
'checkin libv ibm3494 xxxxxx checkl=no status=scratch' for those tapes and
they will check back in again.  Is that weird or what?

I need to try 'checkin libv ibm3494 xxxxxx checkl=yes status=scratch'
instead, to see if it fails if it has to actually mount the tape to check it
in.  I don't have a tape drive free at the moment, but when I do I will try
it.

Best Regards,

John D. Schneider
Sr. System Administrator - Storage
Sisters of Mercy Health System
3637 South Geyer Road
St. Louis, MO.  63127
Email:  [EMAIL PROTECTED]
Office: 314-364-3150, Cell:  314-486-2359


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Wednesday, January 17, 2007 12:15 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Emergency help:ANR1405W even w/ plenty of scratch ta
pes


How about an AUDIT LIBRARY ?  I have had issues with tapes being "lost to
TSM" in my 3494 and doing an audit cleared things up....




Mark Stapleton <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 01/17/2007 01:06
PM Please respond to
"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] Emergency help:ANR1405W even w/ plenty of scratch ta pes






From: ADSM: Dist Stor Manager on behalf of Schneider, John Thanks for
everybody who responded, but when you reply to a post on this list, please
try to make sure you know what you are talking about.  Of the 5 responses I
got, 4 of them made no sense.  Like the guy who recommended I upgrade to TSM
5.1.9, when I stated I was running TSM 5.2.7.1 already.


...which all goes toward what I used to say in the TSM FAQ: post and read
for awhile, and you'll learn whose answers are generally worth listening to,
and whose aren't.

Something in the library is not keeping TSM abreast of scratch status.
Upgrading probably won't fix the issue in that case; checking firmware
levels on the library is more likely to fix it.

Try running CHECKOUT LIBV to remove the scratch tapes, and then run CHECKIN
LIBV on those volumes. Does that fix it permanently? Temporarily?

--
Mark Stapleton ([EMAIL PROTECTED])
Senior consultant

Reply via email to