You state Data Protection for SQL is the "tdp" you are referring to.
Data Protection for SQL backups are automatically managed.
You do not need to manually manage them.
If you run a full backup, it will expire all previous full, log,
and differential backups. At that point, according to your
settings, RETEXTRA and RETONLY settings will then manage
the lifetime of those backups.

Are all of the backups "FULL" backups?
Is it possible that you are running some "out of band" backups,
thus creating more than one backup per day on some days?
Are any of the backups > 30 days?

If you cannot figure this one out, open a PMR with IBM support.
They can take a close look at your environment and find out
what is going on.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 04/06/2011
03:59:36 PM:

>> From: js1000 <tsm-forum AT BACKUPCENTRAL DOT COM>
>> To: ADSM-L AT vm.marist DOT edu
>> Date: 04/06/2011 04:08 PM
>> Subject: TDp and retention settings question
>> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>>
>> The posting doesn't specify which TDP, which would help understanding.
>>
>> TDP for sql with a variety of different versions depending on which
server
>>
>> Which means that to TSM they are all active backups and TSM will
>> therefore not expire them. They have to be expired/deleted from the TDP
>> side, e.g. rman for oracle.
>>
>> is that the case? tdp manages the inactivating of the prior full on
>> the TSM side? so this can be related to be akin to similar to a
>> file backup where once the file is deleted (or marked inactive by
>> TDP) the backup falls under the 30 day expiration window.