Nico,
I have done it the other way. I define the number of versions I need and put
NOLIMIT to the retention. This means that even if a file is deleted TSM
keeps the last 3 versions forever.
This may not be the best solution as the TSM DB grows larger and larger. But
at least I'm sure that the files will be there even when deleted. Here's an
example:

Policy Domain Name BOC_DOMAIN_A
Policy Set Name BOC_POLICYSET_A
Mgmt Class Name BOC_MGC_A
Copy Group Name STANDARD
Versions Data Exists 5
Versions Data Deleted 3
Retain Extra Versions NOLIMIT
Retain Only Version NOLIMIT

Call me if you need anything, at 22-848523.
Yiannakis


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Nicolas Savva
Sent: Monday, March 28, 2005 10:52 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Backup expiration


Hi to all

I have the following management class:

 Policy Domain Name            SVCY185_POLICYDOMAIN

 Policy Set Name               SVCY185_POLICYSET

 Mgmt Class Name               CY185MGMT

 Copy Group Name               STANDARD

 Versions Data Exists          NOLIMIT

 Versions Data Deleted         NOLIMIT

 Retain Extra Versions         31

 Retain Only Version           2

 Copy Mode                     MODIFIED

 Copy Serialization            SHRSTATIC

 Copy Frequency                0

 Copy Destination              DISKPOOL

 Last Update Date/Time         2004-09-07
                               13:58:56.000000

 Last Update by                ADMIN
 (administrator)

 Managing profile              -




If i am correct, based on the above mc an inactive file will be deleted
after 33 days. What about the active backup? for example i am trying to
restore a file that i took backup, and i can't see any of inactive/active
backup versions of this file. Based on manuals, i know that the active
backup version should be existed. (active backup version never expired).

Do i need to change something?

Tsm server: 5.1.5
Tsm client: 5.1.5

Thanks