>>> "when the dba's remove a data base" If your DBAs have gone ahead and deleted a database from the SQL Server end, TSM/TDP will never get a chance to inactivate the object and it will hang around forever as an 'active' object on the TSM Server.
Take a look here to see how to deactivate a backup from the TDP GUI so that it can participate in expiration processing. http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmfd. doc/dpsql55498.htm#dps_tsk_gui_inactivatedbs HTH, ______________ David Mc London, UK -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Schaub, Steve Sent: 09 November 2010 19:01 To: [email protected] Subject: [ADSM-L] SQL mgmtclass rules Tsm server 5.4.3.2 Tsm client 5.5.1.0 Tdp client 5.5.3.0 My mgmt classes for SQL tdp backups are: Verexist=nolimit Verdelete=nolimit Retextra=30 Retonly=90 I had thought that these settings would roll off any and all database backups more than 90 days old, specifically when the dba's remove a data base. However, it looks to me like I have a bunch of old backups hanging around forever, so maybe I misunderstood how to accomplish that. Can someone confirm whether this is the case, and if I have it wrong, what should the settings be so deleted databases will eventually roll off, and if I make the change, will the current moldy backups disappear? Thanks, -Steve Schaub ----------------------------------------------------- Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.864 / Virus Database: 271.1.1/3203 - Release Date: 10/28/10 18:34:00
