The problem below goes further than just TDP for SQL. It looks like everyone needs that brute force command to expire a backup, particularly to cleanup a mistake, or to change a single database backup to have a long retention after the fact. I am going to try to put together a Share requirement for this. I am thinking of a system administrator's commmand only because policies and management classes are done by them. Of course the level of authority required would be similar to other storage policy commands.
What we need is: (1) a way to rebind a new management class for a backup object (with masking type where options like the update volume command) and a flag set on the objects to say they are no longer eligible for rebind (REBIND with where options and specific specifications). (2) a way to turn the rebind eligibility back on. This also solves the problem with objects that are no longer active. I will discuss at Share in San Francisco. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -----Original Message----- From: Del Hoobler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 8:16 AM To: [EMAIL PROTECTED] Subject: Re: how can I delete backups from TDP SQL 2.2? > I used to be able to delete backup sets in TDP for SQL 1.x > I do not want to delete all my inactive sets because I want to keep > one backup from the 1st of each month. Has anyone else come up with a > solution to this? Don, TDP for SQL 2.2 introduced full TSM policy management. Many customers asked for this because TDP for SQL 1.1 did not have it. If you cannot achieve your desired goals through TSM policy management settings, one way you you could do what you are asking is to use a different TSM NODENAME once a month, with different policy settings. Thanks, Del ---------------------------------------------------- Del Hoobler IBM Corporation [EMAIL PROTECTED] - Live your life as an exclamation, not an explanation. - Strive for excellence, not perfection.
