Brett,
There are no automatic way from TSM server side to do this. However you
can use the following method to manually delete the backup files every
60 days.
1) Rename the filespace to fsname_mmddyy where _mmddyy is expiry date of
files after 60 days.
2) After 60 days delete the earlier renamed fsname_mmddyy filespace.
3) After deleting the old filespace, rename the current filespace to
fsname_mmddyy where _mmddyy is again expiry date of files after 60 days.
Repeat steps 2 & 3 every 60 days. This may not be a very elegant
solution, but it serves the purpose with least effort.
Regards, Samiran
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Whitlock, Brett
Sent: Tuesday, April 22, 2008 11:51 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Backup Copygroup setting
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.
--------------------------------------------------------
This message w/attachments (message) may be privileged, confidential or
proprietary, and if you are not an intended recipient, please notify the
sender, do not use or share it and delete it. Unless specifically indicated,
this message is not an offer to sell or a solicitation of any investment
products or other financial product or service, an official confirmation of any
transaction, or an official statement of Merrill Lynch. Subject to applicable
law, Merrill Lynch may monitor, review and retain e-communications (EC)
traveling through its networks/systems. The laws of the country of each
sender/recipient may impact the handling of EC, and EC may be archived,
supervised and produced in countries other than the country in which you are
located. This message cannot be guaranteed to be secure or error-free. This
message is subject to terms available at the following link:
http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you
consent to the foregoing.
--------------------------------------------------------
|
