Rajesh,

A DIFFERENTIAL backup is a separate versioned object on the TSM Server.
It is only logically tied to the FULL database backup.
When the DIFFERENTIAL backup is inactivated after
a FULL backup, it falls into the "Versions Data Deleted" category.
That means, the VERDELETED and RETONLY management class
settings are in effect. That is why you need to set the
VERDELETED setting to nolimit as well.

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 10/26/2010
01:35:11 PM:

>> From: "Lakshminarayanan, Rajesh" <Rajesh.Lakshminarayanan AT DFS DOT COM>
>> To: ADSM-L AT vm.marist DOT edu
>> Date: 10/26/2010 01:35 PM
>> Subject: Re: Backup strategy for SQL server.
>> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>>
>> Hi,
>>
>>     I am little bit confused with David's answer.  It would be great if
>> some one brief's me what is wrong with my setting.
>>
>>      Version Data deleted will take effect only when the database is
>> deleted from the server and more over the "version data exists" option
>> is set to no-limit. Over here I didn't delete the database.   When full
>> tdp backup is executed after the weekly differential backup, diff
copies
>> get inactivated and it is not available for restore.  Based on my
>> setting the inactive copies should be available for 30 days.
>>
>> My copygroup setting is
>>
>> Versions Data Exists: no -limit
>> Versions Data Deleted: 1
>> Retain Extra Versions: 30
>> Retain Only Version: 30
>>
>> Does tdp backup has different interpretation for the above setting?
>>
>>
>> Regards,
>>
>> Rajesh