I have experienced the same problems. The way I got around it was the brute
force and Unix way.
I have written a number of ksh and awk scripts that through query drmedia, move
drmedia, and a number of tapeutil commands (I'm using a 3575 L24), check the
barcode on the tape before issuing the move drmedia commands.
All our operators have to do is to put the tapes two at a time in the IO slots,
and the script reads the barcode, checks that the tape is in the correct DR
state, then issues the mode drmedia commands to change the state, and last of
all, a checkin libvolume. After each tape is checked in, it looks to see whether
there is a tape in the RHS IO slot, moves the tape to the LHS slot, and repeats
the process. If a wrong tape is inserted, then the process will stop, issuing an
error to a nearby console.
It's not perfect. In particular, I have some timing problems where some of our
operators stand over the library, and insert tapes immediatly, and some check
back every half hour or so. With a little more work, I could probably get it to
give some sort of warning if tapes that are due to be checked in are not.
I cannot post the scripts to the forum, but I am prepared to mail them to
interested parties. The one caveat at the moment is that they have only been
checked at server levels up to 2.1.5.18, not version 3.
Please note that I read my mail every 2-3 days, so you may not get them sent
immediatly.
Peter Gathercole
Open Systems Consultant
peter.gathercole AT virgin DOT net
Loon, E.J. van - SPLXM wrote:
> Hi Wanda!
> I guess Guy has the same problem as I have with DRMedia.
> ADSM offers you two ways to checkin your DRM tapes back from the vault:
> CHECKIN LIBV libname SEARCH=BULK STATUS=SCRATCH CHECKLABEL=BARCODE
> This just checks the barcode on the tapes. It does NOT check whether this
> tape should be inserted in the library or not.
> Better is to use the following command:
> MOVE DRMEDIA * WHERESTATE=VAULTRETRIEVE TOSTATE=ONSITERETRIEVE
> CMD="CHECKIN LIBVOLUME 3575LIB &VOL STATUS=SCRATCH"
> CMDFILENAME="/usr/lpp/adsmserv/bin/checkin.mac"
> and then do a MACRO /usr/lpp/adsmserv/bin/checkin.mac.
> This way you know for sure that the right tapes are inserted by the
> operator, because ADSM issues a mount request for each tape. The downside is
> that one has to reply after inserting each tape in the I/O slot one at the
> time. For whatever reason ADSM development has decided not to allow you to
> use the SEARCH=BULK along with VOLNAME, nor is one allowed to use
> CHECKLABEL=BARCODE along with VOLNAME.
> This makes checking in your DRM tapes VERY difficult to automate.
> Kindest regards,
> Eric van Loon
>
> -----Original Message-----
> From: Prather, Wanda [mailto:PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU]
> Sent: Wednesday, November 25, 1998 19:54
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: (DRM) Managing offsite tapes
>
> I'm not sure this will help you, because I'm not sure I understand your
> problems.
> I also am working with ADSM on AIX hosts, not NT, so there may be something
> I"m missing here.
> I am also assuming that you are running the 9730 with the ADSM SCSI drivers.
>
> But if this doesn't answer your questions, maybe you can make your questions
> more specific:
>
> 1) TO get a list of tapes to be returned:
> Q DRMEDIA WHEREST=VAULTRETRIEVE
>
> All you have to do is to pipe the output of that command into a file, and
> that IS the list of tapes that should be returned from the vault.
> The ADSM V3 admin ref, Chap. 3, explains how to invoke the dsmadmc command
> from an OS prompt and redirect output into a file.
>
> 2) Q DRMEDIA WHEREST=COURRIERRETRIEVE cmd= cmdfile=
> You can use this to generate a list of the tapes to be checked in AND send
> them to a file AND format the output into the appropriate CHECKIN command!
> Then just execute the generated file as a macro.
>
> Another alternative for CHECKIN with an automated SCSI libary is this:
>
> CHECKIN LIBV xxxxx SEARCH=BULK STATUS=SCRATCH CHECKLABEL=BARCODE
>
> SEARCH=YES causes ADSM to search the library for anything that hasn't been
> checked in already and check it in.
> SEARCH=BULK causes ADSM to search the I/O port for anything that hasn't been
> checked in already and check it in.
> ADSM just uses the barcodes for the checkin, so you don't really have to
> care about getting the right VOLSERS into the checkin command!
>
> 3) LABEL LIBV xxx SEARCH=YES LABELSOURCE=BARCODE CHECKIN=SCRATCH
> ADSM will check everything in the libary, using the barcodes, and write
> labels matching the barcodes, without having to enter any REPLYs.
>
> Also note there is now a BULK option on both CHECKIN and CHECKOUT.
> That causes ADSM to CHECKIN or EJECT tapes without issuing REPLY's.
>
> BULK is a new option, if you have the older documentation BULK may not be in
> it, check the version of the ADMIN REF that is available on the web site.
>
> Hope this helps some...
> ***************************************************************
> Wanda Prather
> The Johns Hopkins Applied Physics Lab
> 443-778-8769
> wanda_prather AT jhuapl DOT edu
>
> "Intelligence has much less practical application than you'd think" -
> Scott Adams/Dilbert
> ***************************************************************
>
> .
>
> > -----Original Message-----
> > From: Guy Sheppard [SMTP:guy_sheppard AT uk.cu DOT com]
> > Sent: Wednesday, November 25, 1998 7:59 AM
> > To: ADSM-L AT vm.marist DOT edu
> > Subject: (DRM) Managing offsite tapes
> >
> > Dear All,
> >
> > Hiya and help please..
> >
> > I've setup an NT ADMS server (3.1.2.0) backing up a number of SP nodes,
> > various levels of AIX. The server is using an STK9730 with 4*DLT4000 tape
> > drives. No problems at all thus far.
> >
> > However, One thing I find missing from ADSM is the ability to
> > 'automatically'
> > control the issue of moving the disaster tape copies off, and then back
> > onsite.
> >
> > Whilst I realise that the commands are there MOVE DRM, Q DRM, etc there
> > is
> > nothing to actually tie all this together for the people that have the
> > responsibility to actually use the product to move the tapes offsite and
> > back
> > on again, when the time is right.
> >
> > Does anyone have any code (REXX etc) to tie all this up into a usable
> > application. I've got code to find what needs to go offsite(Q DRM) and
> > eject
> > the tapes through the ejection/entry port but I'm interested in the
> > following:
> >
> > (1) Tape lists: What needs to be requested back from the offsite vault.
> > Then MOVE DRM * WHEREST=VAULTR
> >
> > (2) Once tapes return onsite.
> > Then MOVE DRM * WHEREST=COURIERR and CHECKIN.
> >
> > (3) Ability to label LABEL LIBVOL extra tapes etc. Without having to
> > manually
> > use the REPLY command. (Want to be using the ejection/entry port).
> >
> > I'm sure I'm not the first person to require this function. What does
> > everyone
> > else do?
> >
> > Thought I'd ask before I write it all myself!
> >
> > Also, if IBM are listening when are you guys going to be adding this type
> > of
> > useability function. If it was there ADSM would get a 10/10 as far as I'm
> > concerned.
> >
> >
> >
> >
> >
> >
> > Guy Sheppard
> > Storage Management
|
