D'oh! Don't know what I was thinking, of course you are correct. And yes,
while this is theoretically possible, it's not something that most users
would wish to do.

Thanks!

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Robert L. Rippy" <robert_rippy AT KINDREDHEALTHCARE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/24/2002 11:31
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: TSM Policy Model



How would the files expire once you deleted them off the server if you had
unlimited retention? Wouldn't that negate the necessity for unlimited
retention? I was only showing that it could be done, but I wouldn't
suggest
it.

Thanks,
Robert Rippy.



From: Andrew Raibeck <storman AT US.IBM DOT COM> on 12/24/2002 11:31 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: TSM Policy Model

Even unlimited copies/retention wouldn't guarantee this: if someone
deleted a bunch of files on their client drive, then they will be expired
during the next incremental backup. If the deleted files happen to
comprise 95% of a tape, the voile! you now have a full volume with only 5%
valid data.

The best way to deal with this is to be more aggressive with reclamation,
i.e. set the storage pool's reclamation threshold to something like 60 or
75 rather than 90 or 95. But the trade-off is that you will be doing
reclamation more frequently. Since reclamation uses TSM server resources
(tape drives, CPU, etc.), you'll have to balance your reclamation needs
with other TSM management requirements.

In general, I would recommend reading the Admin Guide from cover to cover
(if you haven't done so already) to familiarize yourself with how TSM
works. In particular, you can read up on reclamation in the chapter on
"Managing Storage Pools and Volumes".

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.


-----Original Message-----
From: Robert L. Rippy [mailto:robert_rippy AT KINDREDHEALTHCARE DOT COM]
Sent: Tuesday, December 24, 2002 10:28 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Policy Model


Its possible. Just create retention policies that retain unlimited copies
with a nolimit retention. That way once a volume is full, it will stay
full
because nothing will expire. Not that I would recommend it, but it is
possible.

Thanks,
Robert Rippy.



From: "Remeta, Mark" <MRemeta AT SELIGMANDATA DOT COM> on 12/24/2002 10:23 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: TSM Policy Model

That is impossible. It's the way TSM works.


-----Original Message-----
From: Mario Behring [mailto:mariobehring AT YAHOO DOT COM]
Sent: Sunday, December 22, 2002 4:39 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM Policy Model


Hi list,

Where can I find some documented examples of TSM policies for backup and
archive operations ?

I have to create a policy that does not create the situation where you
have
a tape with only 5% of real data stored and 95% marked for reclamation.

Thanks.