I haven't actually used TSM very much (my organization has an employee that 
just works with TSM), but I was wondering what solutions there were for 
implementing something similar to a grandfather/father/son rotation scheme for 
keeping files that my organization backs up.

I've asked our TSM person for suggestions, but she's telling me that our only 
option is to save 5 or 7 copies of a file.  We don't have agents or the like 
for SQL servers, so currently we do a dump every night that gets backed up by 
TSM.  For many of my systems, this means we only have a backup of 5 or 7 days.

Currently my only option is to append the date onto the dump which forces TSM 
to keep it as a seperate file each day.  Is there any way to just keep 
different dates of the same file without me having to go back to my 75 SQL 
servers and change the job so that the date is on the end of each filename?  
Thanks in advance for the help.

+----------------------------------------------------------------------
|This was sent by matt.self AT msj DOT org via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------