ADSM-L

Re: 3494 Library Sharing for ADSM sites

1999-08-03 11:10:45
Subject: Re: 3494 Library Sharing for ADSM sites
From: Rodrigo Cordovil Gazzaneo <rgazzaneo AT INFOLINK.COM DOT BR>
Date: Tue, 3 Aug 1999 10:10:45 EST
That's another big point.

Library checkin is the moment when tapes will be assigned to each servers,
so the other won't see it. Operation policies will have to be set so this
kind of problems won't happen.

Thanks again. Now I can see clearly many other problems that come with this
solution and will have to be adressed.

best regards,
Rodrigo

>Yes, that would be a way to visibly distinguish one ADSM servers tapes fro
>the other. But I have had customers run a
>checkin libvol lib_name search=yes stat=scratch...
>and accidentally grab the second ADSM server's tapes that were stuck in th
>Entry/Exit door and had as of yet not been checked into the first ADSM
>server.
>What really needs to be done is to develop a policies and procedures run
>book for operations to follow step-by-step in regard to tape movement. I
>have had great success whenever I have left my customers with this type of
>documentation.
>Joshua S. Bassi
>Storage Management Team Lead
>AIX / ADSM Certified Specialist
>Dickens Services Group
>(404) 386-9848
>jbassi AT gloryworks DOT com
>www.TeamDSG.com
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
>Kelly J. Lipp
>Sent: Monday, August 02, 1999 7:17 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: 3494 Library Sharing for ADSM sites
>Get two distinctly different sequence numbers for you tapes. One site we'v
>set up uses volsers starting with UX for one and LN for the other server.
>In addition, consider different color tape labels or even tapes from more
>than one vendor. Make it as difficult at possible to check in the wrong
>tape to the wrong server.
>Kelly
>-----Original Message-----
>From: Joshua Bassi [SMTP:jbassi AT GLORYWORKS DOT COM]
>Sent: Monday, August 02, 1999 4:48 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: 3494 Library Sharing for ADSM sites
>Rodrig,
>Be very careful not to checkin one ADSM server's private tapes to the othe
>ADSM server! This is the biggest "opportunity" of a problem arising with
>two or more ADSM servers sharing a 3494. You can visit www.adsm.org and do
>a search on sharing the 3494 if you need more info.
>Joshua S. Bassi
>Storage Management Team Lead
>AIX / ADSM Certified Specialist
>Dickens Services Group
>(404) 386-9848
>jbassi AT gloryworks DOT com
>www.TeamDSG.com
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
>Rodrigo Cordovil Gazzaneo
>Sent: Monday, August 02, 1999 12:46 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: 3494 Library Sharing for ADSM sites
>Hi,
>Does anybody on the list have any experience with 3494 Lib
>sharing
>between ADSM Servers ? I am studying the IBM redbook about it,
>which is
>a little old (1996) but has the major issues adressed.
>As far as I have read, basic points are :
>- define /dev/lcmp0 for both connected machines
>- define 3590 drives for separate machines (dedicated drives for
>each
>server)
>My big doubt is about tape control. I understand ADSM will assign
>new
>category numbers for private and scratch volumes (like 300 and
>301 for
>first server, 400 and 401 for next server) so both volume
>inventories
>won't share tapes. The redbook doesn't go deep into ADSM, so I am
>asking
>for a little help.
>Will I have to load tapes for both the inventories separately,
>first one
>load for one server and then another for the other ? They will
>only be
>registered to the library once, labeled and checked in for only
>one
>server. Has anybody seen/written scripts for automating this
>procedure ?
>If anybody has had any experience with this problem, please show
>me the
>path towards ilumination !
>TIA,
>Rodrig
<Prev in Thread] Current Thread [Next in Thread>