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