As others said you can use mig delay and other settings.
However, since you have that much space would a File class type pool not
work better? Then you could basically treat it like a tape pool, with
reclamation, etc. (I know it's not exactly the same, but similar)
You might want to start with a small pool, and do some testing, and
playing with settings until you get the desired effect.
See Ya'
Howard
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Eric Thompson
> Sent: Wednesday, April 15, 2009 12:46 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] High Mig Pct & Low Mig Pct = 100%
>
> A "plain disk storage pool".
>
> The diskpool (DP2) is 8 TB, next storage pool is tape (TP2).
>
> My goal is to have all data sit on the diskpook (DP2), not migrate to
> TP2.
> The data will remain on disk (DP2) until expired, deleted, etc.
>
> If DP2 fills-up to 100%, then I'd like the data to be written to tape
> (TP2), the next storage pool.
> The "excess" data on tape (TP2), if exists, will be reviewed. A
> decision will then be made to either increase the size of the diskpool
> (DP2) and move the data there, delete it, etc.
>
> It sounds like the best I can do is set HIGHMIG = 100 & LOWMIG=99 ?
> Is there anything else that I need to consider?
>
> Thanks for the replies.
>
> Eric Thompson
> Senior Storage Engineer
> www.it-lifeline.com
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Howard Coles
> Sent: Wednesday, April 15, 2009 10:31 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] High Mig Pct & Low Mig Pct = 100%
>
> TSM will not let you set high and low migration thresholds to the same
> levels. I tried that once or twice (and again today just to be sure).
> However, you can set "hi=100 lo=99".
>
> My question is are you creating a "File" class storage pool or just a
> plain disk storage pool?
>
> See Ya'
> Howard
>
>
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf
> > Of Eric Thompson
> > Sent: Wednesday, April 15, 2009 12:20 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] High Mig Pct & Low Mig Pct = 100%
> >
> > Thanks for the reply.
> >
> > If I don't set the LOWMIG=100, then when the storage pool hits 100%,
> > won't it start a migration process that will continue until it hits
> the
> > LOWMIG value?
> >
> > My thought was that if I set both to 100, then a migration would not
> > take place ever. I would then depend on my secondary pool to accept
> > any
> > unexpected "excess data". (which shouldn't occur, since we size our
> > primary storage pools (disk) to handle all data, but occasionally we
> > get
> > an unexpected influx that we want to overflow to tape temporarily
> until
> > it can be "looked at").
> >
> > Thanks again.
> >
> > Eric Thompson
> > Senior Storage Engineer
> > www.it-lifeline.com
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf
> > Of
> > Colin Dawson
> > Sent: Wednesday, April 15, 2009 10:07 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] High Mig Pct & Low Mig Pct = 100%
> >
> > Howdy,
> >
> > We've seen many cases where folks set HIGHMIG=100. I can't
say
> > that
> > I've seen much where LOWMIG=100 is set or used in this fashion
> > though...
> > Generally, HIGHMIG=100 is all that is needed to prevent migration
> from
> > trying to migrate the data from a given storage pool.
> >
> > The decision to overflow to the NEXT pool is done at the time
> that
> > the
> > server is trying to reserve space in a given pool. If there is not
> > sufficient space available to reserve based on the incoming store
> > request,
> > it is at that point that the server will traverse to the NEXT pool
> and
> > attempt reservation/allocation in that pool. The reservation and
> > allocation processing in this regard is pretty well independent of
> the
> > HIGHMIG setting for the storage pool.
> >
> > -----------------------------------------------------
> > Colin Dawson
> > TSM Server Development
> > colind AT us.ibm DOT com
> >
> >
> > |------------>
> > | From: |
> > |------------>
> >
> >
>
>----------------------------------------------------------------------
> > -
> >
>
----------------------------------------------------------------------|
> > |Eric Thompson <ethompson AT ITLIFELINE DOT NET>
> > |
> >
> >
>
>----------------------------------------------------------------------
> > -
> >
>
----------------------------------------------------------------------|
> > |------------>
> > | To: |
> > |------------>
> >
> >
>
>----------------------------------------------------------------------
> > -
> >
>
----------------------------------------------------------------------|
> > |ADSM-L AT VM.MARIST DOT EDU
> > |
> >
> >
>
>----------------------------------------------------------------------
> > -
> >
>
----------------------------------------------------------------------|
> > |------------>
> > | Date: |
> > |------------>
> >
> >
>
>----------------------------------------------------------------------
> > -
> >
>
----------------------------------------------------------------------|
> > |04/15/2009 09:55 AM
> > |
> >
> >
>
>----------------------------------------------------------------------
> > -
> >
>
----------------------------------------------------------------------|
> > |------------>
> > | Subject: |
> > |------------>
> >
> >
>
>----------------------------------------------------------------------
> > -
> >
>
----------------------------------------------------------------------|
> > |[ADSM-L] High Mig Pct & Low Mig Pct = 100%
> > |
> >
> >
>
>----------------------------------------------------------------------
> > -
> >
>
----------------------------------------------------------------------|
> >
> >
> >
> >
> >
> > I want to keep all data on the primary storage pool (disk), yet
allow
> > for overflows to the secondary pool (tape) in the event more data is
> > backed up than expected.
> >
> >
> >
> > Has anyone ever set both High & Low Mig Pct = 100% ?
> >
> >
> >
> > If I do this, will the data still overflow to the secondary storage
> > pool
> > during a backup if the primary storage pool is full (100%)? Or will
> I
> > get the "out of storage space" message.
> >
> >
> >
> > Thanks. Eric
|
