ADSM-L

Re: Previewing Expiration

2005-09-06 09:40:18
Subject: Re: Previewing Expiration
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 6 Sep 2005 09:40:03 -0400
Also, if you start the GUI and click RESTORE, browse to the files you
are interested in, on the FAR RIGHT of the window you will see the
management class they backed up to, if you want to check the result of
your DIRMC implementation.

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Alexander Lazarevich
Sent: Saturday, September 03, 2005 1:42 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Previewing Expiration


On Sat, 3 Sep 2005, David le Blanc wrote:

> Hi enlightened list members,
>
>
> I have a number of policy changes to make, including the
implementation
> of an
> client optionset containing a 'DIRMC' to redirect directories globally
> to a disk
> storage pool with lowered retention.
>
>
> The problem I have is the database appeared to grow more quickly than
> anticipated
> and I've finally clicked that TSM has made an unfortunate choice for
> DIRMC, where
> it has selected a management class set up for a TDP with 60day
> archives... Whoever
> set it up made the (otherwise unused) backup copygroup nolimit for all
> parameters.
>
> As you could imagine, we now have likely a billion versions of a
billion
> directories
> across the enterprise.
>
> If I make the changes I think need to happen, how can I 'preview' the
> expiration process
> to make certain there are no surprises??

Only way I know how to do that is run dsm GUI from the client that has
the modified include-exclude (or dsm.opt) file, then proceed to run a
manual backup, and see what is red-x'ed out and what isn't, make sure it
matches what you think it should do. You don't actually have to run a
manual backup to do this though.

Alex

<Prev in Thread] Current Thread [Next in Thread>