>From TSMLM2, define the library as shared and all the drives. Checkin all the >tapes as PRIVATE.
>From TSM2T, define the shared library and point your device class(es) to the >shared library. Now just AUDIT LIBR <shared library name> CHECKL=B. This will populate the volume history on TSMLM2 with all the volume information, change the ownership to all the checked in volumes to TSM2T. Then you can do a Q LIBV on the TSMLM2 and any tape still with the ownership of TSMLM2 is probably a scratch tape. Check the volhist on TSM2T to make sure, but then just UPD LIBV <shared lib name> <volume> STATUS=SCRATCH. The big kicker seems to the the AUDIT LIBR from the library client populating the volhist on the library manager with all the known volume information. If you look at the volhistory entry for one of those tapes you'll see that the TYPE is 'REMOTE' and the LOCATION is '<library client name>'. Bill Boyer "Some days you're the bug, some days you're the windshield" - ?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of fred johanson Sent: Tuesday, April 04, 2006 9:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Migrating to a Library Manager AND remember to print, or otherwise save a list of PRIVATE, SCRATCH, DBB, DBS, and whatever other sorts of tapes you may have, for reference if one of your experiments goes wrong. At 08:10 PM 4/3/2006 -0400, you wrote: > >> On Mon, 3 Apr 2006 15:32:22 -0500, Bill Kelly <[EMAIL PROTECTED]> said: > > > > 1) check the tapes out of tsm2t > > 2) delete the library (and drives and paths) from tsm2t > > 3) define the library (and drives and paths) in tsmlm2, and as a > > shared library in tsm2t > > 4) check the tapes in to tsmlm2. > >What he said; I've done this. > >Additional knob-polishing, lily-gilding, etc: > >Remember that you don't have to REMOVE the volumes on checkout, and >that you don't have to check the label when you check them in. This >can really accellerate experiments. > >Remember also that it's easy to get back to the state of "everything >checked out, and library gone", so you can get it wrong several times, >and ry again with very little cost. > >While this is an intimidating process since it's so uncommon, it's not >really either complex or dangerous. > > >- Allen S. Rout Fred Johanson ITSM Administrator University of Chicago 773-702-8464
