ADSM-L

Re: [ADSM-L] Sropping expiration for specific clients

2007-10-22 13:22:49
Subject: Re: [ADSM-L] Sropping expiration for specific clients
From: Ben Bullock <bbullock AT MICRON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 22 Oct 2007 11:04:02 -0600
Been there, done that. There is no way to stop expiration for only some
nodes. It is either all or nothing. 

A few options:
- export the data on the clients you do NOT want to expire. That would
keep them on their own, but you would need to import it with relative
dates when you wanted to look at it.
- If the data is all archived to it's own management class, you could
raise the retention on that MC to keep it around longer.

Ben 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Joy Hanna
Sent: Monday, October 22, 2007 10:59 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Sropping expiration for specific clients

Hello,
  Due to a legal request we are being asked not to expire any data for
some specific TSM clients. Is there a way to exclude a group of clients
from expiring any data for a time period? I see there is a way to do
this for archived data. I'm talking incremental backup data. If I stop
expiring altogether I think it wouldn't be long before I put my whole
environment at risk. The only way I can think of to do this would be to
rename all filespaces where I suspect there might be data I do not want
to expire. This however would cause all those renamed filespaces to back
up in full tonight. We're talking several TB of file server data. Any
ideas? Sincerely, Joy 
 
Joy Hanna
Enterprise Storage Group
I.T. Computer Operations
(503)745-7748
Joyhanna AT freightliner DOT com