You should be able to set the Retain Extra Versions to 60, Version Data
Exists and the Versions Data Deleted to nolimit and the server will,
defacto, allow TSM to keep versions based on their age. This is what you
would do to enable point-in-time restores as well. Of course, this will
mean more storage usage.

>>> brett.whitlock AT COUNTRYFINANCIAL DOT COM 4/22/2008 10:50 AM >>>
I have a SQL user who creates a nightly backup with an older version
of
litespeed.  They only want to retain 60 days.  The problem is each
nightly backup has a unique date/time stamp.  Therefore TSM sees every
file as an active version.  Since each version is active I am just
keeping everything.  The files don't get deleted nor are  they
triggered
to be inactive so I can't use the retain only or verdelete.  How do I
convince TSM, using the backup copygroup (not archive) to just keep a
file 60 days?
A newer version of litespeed allows SQL to use the archive copygroup.
However if I can make this work with the backup copygroup this will
defer testing and implementing.

We are on TSM 5.3.3 windows server.


IMPORTANT NOTICE:  This message and any included attachments are from East 
Jefferson General Hospital, and is intended only for the addressee(s), and may 
include Protected Health (PHI) or other confidential information.  If you are 
the intended recipient, you are obligated to maintain it in a secure and 
confidential manner and re-disclosure without additional consent or as 
permitted by law is prohibited.   If you are not the intended recipient, use of 
this information is strictly prohibited and may be unlawful.  Please promptly 
reply to the sender by email and delete this message from your computer. East 
Jefferson General Hospital greatly appreciates your cooperation.