ADSM-L

Re: 3494 Volume Stealing

2002-03-18 11:14:07
Subject: Re: 3494 Volume Stealing
From: Allen Barth <allen_barth AT SCUDDER DOT COM>
Date: Mon, 18 Mar 2002 10:09:07 -0600
It wasn't stolen.  I have seen where the 3494 will eject a cart all on its
own for various reasons.  This action is not sent to TSM.  Perhaps the
operators saw the tape in the IO door and just pulled it out and put it
back in without letting anyone know.  Mine have done that several times,
the volume is then in FF00 category (free for all).    In your case
another TSM could have claimed this tape, and a later AUDIT LIBRARY on the
rightful owner would leave the 3494 and the TSM's in the state you
mention.





"Orville L. Lantto" <orville.lantto AT DTREND DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/15/02 04:43 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: 3494 Volume Stealing


The volume which was "stolen" was checked in to another TSM server with
that server's scratch category code (verified by mtlib).  Yes, this is
very disturbing!


Orville L. Lantto
Datatrend Technologies, Inc.  (http://www.datatrend.com)
121 Cheshire Lane #700
Minnetonka, MN 55305
Email: Orville.Lantto AT dtrend DOT com
V: 952-931-1203
F: 952-931-1293
C: 612-770-9166




"Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/15/02 03:15 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: 3494 Volume Stealing


Yes and no.  Once a tape is ejected from the library, when it is
reinserted,
it is anybody's game because it does not belong to a specific TSM server.
It is in FF00 status.  So, if you do a checkin command with a range,
search=yes, another TSM Server could get it.  This is why I do checkin
commands with a specific volume id when I checkin each tape.

At Share we have asked for a function to be added in general to setup an
include table for each TSM server.  This include table would limit what
ranges of tapes are allowed to be picked up by that TSM server instance.

Now, if the tapes are already in the library and assigned a scratch or
private category and the tapes can be stolen, that is a major problem that
support needs to know about.  I have never tried to see if I can cause one
TSM to steal tapes from another TSM server this way.

<Prev in Thread] Current Thread [Next in Thread>