From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
Behalf Of Tuncel Mutlu (B.T.S.Y.G.)
>I have a management class backup which should retain files for 
>5 years even if they are deleted.
>
>Policy Domain Name WINNTPD 
>Policy Set Name ACTIVE 
>Mgmt Class Name MC_5YIL 
>Copy Group Name STANDARD 
>Versions Data Exists NOLIMIT 
>Versions Data Deleted NOLIMIT 
>Retain Extra Versions 1825 
>Retain Only Version 1825 
>Copy Mode MODIFIED 
>Copy Serialization SHRDYNAMIC 
>Copy Frequency 0 
>Copy Destination BACKUPPOOL2 
>
>But today I see 350,000 files expire and the admin of the box 
>says me that he has deleted the files because they are kept in 
>TSM for 5 years.
>
>How is that possible, why did the files expire ?

You misunderstand how TSM uses retention rules. When you delete a file
from a TSM client, the file goes to inactive status during the next
backup. When you go to inactive status, you go from NOLIMIT number of
copies to 1825. Thus the expiration.

If you want to be able to delete files and still keep copies of them
within TSM, you need to run an archive, not a backup.

--
Mark Stapleton (stapleton AT berbee DOT com)
IBM Certified Advanced Deployment Professional
Tivoli Storage Management Solutions 2005
Office 262.521.5627