Randy,
That sounds like a reasonable technique. However, doesn't the Magstar have
an 'automatic' option where you can preload the magazine and it will pull
from the magazine as tapes are needed? When in 'MANUAL' mode, does ADSM
require a reply to continue??
Doug
> -----Original Message-----
> From: Eggert, Randall [SMTP:REggert AT WIS.TWC DOT COM]
> Sent: Monday, October 26, 1998 9:50 AM
> Subject: Re: Defining two 3590s to a storage pool
>
> Dwight,
> I agree with Doug on this. I left an environment with AIX 4.1.4 & ADSM
> 2.1.5.18 with 2 3590-B11 drives (Magstar with the self-contained 10 cell
> "mini" library).
> When I defined each 3590 as a mini-library (containing 10
> volumes),
> each would have to be defined in its own storage pool. Thus work could
> not
> be thrown from one tape to another when the first was busy. This required
> a
> good effort to predefine backup volume and time to properly distribute the
> load between the two drives.
> Since this was in the same room as our 24/7 mainframe shop, I
> scrapped the second storage pool, redefined both 3590 drives as MANUAL,
> and
> stuck them both in the same storage pool. Disadvantage: all tapes had to
> be
> manually loaded. Advantage: both drives were in use if the backups in
> session required them.
>
> Randy Eggert
>
> -----Original Message-----
> From: Agnew, Doug [mailto:dagnew AT CHARLOTTEPIPE DOT COM]
> Sent: Monday, October 26, 1998 7:43 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Defining two 3590s to a storage pool
>
>
> Dwight,
>
> I had the same environment, and the same question, but had not tried
> anything. Called support and discussed scenario with them. They agree
> with
> Jennifer -- it just don't work that way, as much as we would like for it
> too. Seems like either I am going to have to break my backup into 2
> dataspace backups (using Informix) to two different managment classes or
> replace the 3590s with a true multi-drive library system.
>
> Running SAP 3.1H/Informix 7.23 on HP-UX with ADSM v2 on AIX4.1
>
>
> Doug Agnew
>
> > -----Original Message-----
> > From: Jennifer Davis [SMTP:jedavis AT DFW DOT NET]
> > Sent: Sunday, October 25, 1998 9:55 PM
> > Subject: Re: Defining two 3590s to a storage pool
> >
> > Dwight,
> >
> > If memory serves me correct, your scenario would yield messages to the
> > effect of
> > ANRXXXXE No Drives Available in Library
> > for whatever process needs the drive (like migration from the top level
> > pool).
> >
> > It NOT simply trigger a roll to the next pool.
> >
> > Like I said, it's been a while since I encountered this, but I'm pretty
> > sure that would be the result. If you find differently, please repost.
> >
> > Best Regards,
> >
> > Jenn
> >
> > At 12:26 AM 10/23/98 -0500, you wrote:
> > > WHat happens if you set up three storage pools
> > > lib1stg
> > > lib2stg
> > > lib3stg
> > > then a forth
> > > ptrstg of type disk but don't give it any disk but do give it a
> next
> > > of lib1stg, then set lib1stg's next to lib2stg, then set lib2stg's
> > > next to lib3stg and have your management class pointed to
> ptrstg...?
> > >
> > > An out of space condition will trigger a roll to the next but will
> > an
> > > out of drives also trigger a roll to a next if it exists ? ? ?
> > >
> > > all my drives are in a 3494 or I'd try... or if I had a system
> with
> > > multiple 8mm could also but I'm still out of luck... I'd think it
> > is
> > > worth a whirl
> > >
> > > later,
> > > Dwight
> > >
> > >
> > >
> > >______________________________ Reply Separator
> > _________________________________
> > >Subject: Re: Defining two 3590s to a storage pool
> > >Author: anthony.k.k.chin at
> > >unix,mime/DD.RFC-822=anthony.k.k.chin AT ssi.shell.com DOT my
> > >Date: 10/22/98 1:23 AM
> > >
> > >
> > >Many thanks for the reply from Doug, Ben and Daniel.
> > >
> > >I tried Ben's suggestion but still getting the same error. Grateful
> for
> > >any further advice. Following is the ADSM definitions and log.
> > >
> > >Regards,
> > >Chin
> > >
> > >==================================================
> > >adsm> q drive
> > >
> > >Library Name Drive Name Device Type Device
> > >Element
> > >------------ ------------ ----------- ----------------
> > >-------
> > >LIB_3590_1 DRV_3590_3 3590 /dev/rmt0
> > > 16
> > >LIB_3590_2 DRV_3590_2 3590 /dev/rmt1
> > > 16
> > >LIB_3590_3 DRV_3590_3 3590 /dev/rmt2
> > > 16
> > >
> > >======================================================
> > >adsm> q drive f=d
> > >
> > > Library Name: LIB_3590_1
> > > Drive Name: DRV_3590_3
> > > Device Type: 3590
> > > Device: /dev/rmt0
> > > Element: 16
> > >Last Update by (administrator): SYSADM
> > > Last Update Date/Time: 09/10/98 12:27:59
> > >
> > > Library Name: LIB_3590_2
> > > Drive Name: DRV_3590_2
> > > Device Type: 3590
> > > Device: /dev/rmt1
> > > Element: 16
> > >Last Update by (administrator): SYSADM
> > > Last Update Date/Time: 02/09/97 01:02:38
> > >
> > > Library Name: LIB_3590_3
> > > Drive Name: DRV_3590_3
> > > Device Type: 3590
> > > Device: /dev/rmt2
> > > Element: 16
> > >Last Update by (administrator): SYSADM
> > > Last Update Date/Time: 09/08/98 16:47:29
> > >
> > >======================================================
> > >adsm> q devclass
> > >
> > >Device Device Storage Device Format Est/Max
> > >Mount
> > >Class Access Pool Type
> > >Capacity Limit
> > >Name Strategy Count
> > >(MB)
> > >--------- ---------- ------- ---------
> > >------ -------- -----
> > >DEVC_359- Sequential 6 3590 3590C 30,720.0
> > > 2
> > > 0_1
> > >DEVC_359- Sequential 5 3590 3590C 30,720.0
> > > 1
> > > 0_2
> > >DEVC_BAC- Sequential 0 FILE 1,800.0
> > > 1
> > > KUPDB
> > >DISK Random 0
> > >
> > >========================================================
> > >09/29/98 13:10:11 ANR0403I Session 3153 ended for node KLLLL13
> (AIX).
> > >09/29/98 13:10:11 ANR0403I Session 3150 ended for node KLLLL12
> (AIX).
> > >09/29/98 13:10:12 ANR0400I Session 3154 started for node KLLLL13
> > >(AIX).
> > >09/29/98 13:10:12 ANR0400I Session 3155 started for node KLLLL12
> > >(AIX).
> > >09/29/98 13:10:15 ANR0403I Session 3155 ended for node KLLLL12
> (AIX).
> > >09/29/98 13:10:16 ANR0400I Session 3156 started for node KLLLL12
> > >(AIX).
> > >09/29/98 13:10:24 ANR8447E No drives are currently available in
> > >library
> > > LIB_3590_1.
> > >09/29/98 13:10:24 ANR1401W Mount request denied for volume P00031 -
> > >mount
> > > failed.
> > >09/29/98 13:10:24 ANR0525W Transaction failed for session 3154 for
> > >node
> > > KLLLL13 (AIX) - storage media inaccessible.
> > >09/29/98 13:10:25 ANR0403I Session 3154 ended for node KLLLL13
> (AIX).
> > >09/29/98 13:10:52 ANR0400I Session 3157 started for node KLLLL12
> > >(AIX).
> > >=========================================================
> > >>----------
> > >>From: bbullock[SMTP:bbullock AT MICRON DOT COM]
> > >>Sent: 14 October 1998 00:17
> > >>To: ADSM-L AT VM.MARIST DOT EDU
> > >>Subject: Re: Defining two 3590s to a storage pool
> > >>
> > >>I'm not sure about what you are trying to accomplish here. Did new
> > library
> > >>definition , with it's own unique scratch and private categories? or
> did
> > you
> > >>add your new drive into the current library and now you want it to be
> > >>utilized?
> > >> If it is the latter, you want to make sure that you updated the
> device
> > so
> > >>that it's "mount limit" reflects that you have one more drive. You can
> > see
> > >>this by using the "query dev" command and then a command like "update
> > dev
> > >>3590 mountl=2" if it needs to be upped.
> > >>
> > >>Ben
> > >>
> > >> -----Original Message-----
> > >> From: Chin, Anthony SAIS-ASCI
> > >>[SMTP:anthony.k.k.chin AT SSI.SHELL.COM DOT MY]
> > >> Sent: Monday, October 12, 1998 6:09 PM
> > >> To: ADSM-L AT VM.MARIST DOT EDU
> > >> Subject: Defining two 3590s to a storage pool
> > >>
> > >> >I have installed another 3590 and would like to use it as a
> > second
> > >>library of
> > >> >a storage pool so that I can have two concurrent backup
> > sessions.
> > >>However,
> > >> when the 2nd session was started (while the first dirve was
> > still
> > >>being
> > >> >used by the first session), ADSM did not use the second
> > >>drive/library and
> > >> >displayed message :
> > >> >
> > >> >"ANR8447E No Drive are currently available in the library"
> > >> >
> > >> >How do I resolve this problem ? Grateful for any advice. I
> am
> > >>using ADSM
> > >> >version 2.1.
> > >> >
> > >> >Regards,
> > >> >Chin
> > >> >
> > >>
> > >
> > >
|
