Hmmm. Are you saying that when you return the tapes from offsite, you relabel
them? I have a couple of ideas if this is the case.

Let me know.




From: Phil Chissell <phil.chissell AT NATPOWER DOT COM> on 07/14/98 05:50 PM GMT

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

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: ADSM)
Subject:  Re: Private/Scratch library tapes




The scenario is as follows:-
(1)     Everyday ADSM does a backup stgpool command
(2)     The backup stgpool tape(s) are checked out using a "checkout
libvol ... checklabel=yes" command and an "update volume ...
access=offsite" command
(3)     ADSM kicks off an "audit library ... checklabel=barcode" process
(4)     The tape is ejected and taken offsite and a scratch tape is put
into the eject port
(5)     ADSM issues a "label libvol ... checkin=scratch
labelsource=barcode overwrite=yes" command to checkin the scratch tape
(which may or may not already be labelled)
(6)             ADSM kicks off an "audit library ... checklabel=barcode"
process
(7)     Once a week, the offsite tapes are reclaimed and the above
process re-iterates.
Now the problem is that (very) infrequently, a tape appears in the
output of a "query libvol" command as being a private tape when it is
not a member of any storage pools nor is used as a database backup tape.
This tape then needs to be remarked as being scratch by issuing a
"update libvol ... status=scratch" command
That's about the size of it!
Regards
Phil
Phil Chissell
National Power plc
Windmill Hill Business Park
Whitehill Way
Swindon
Wilts. SN5 6PB
UK
Tel:  +44 (0)1793 894237
Fax: +44 (0)1793 894230
MailTo:Phil.Chissell AT natpower DOT com

> stuff deleted <