Zolton,

For legacy-style DP/SQL backups, you can break this up by
using the STRIPES option. Each stripe will use a different
session with the TSM Server. For example:

    tdpsqlc backup db1 full /STRIPES=4

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 09/06/2011
01:12:56 PM:

>> From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
>> To: ADSM-L AT vm.marist DOT edu
>> Date: 09/06/2011 01:17 PM
>> Subject: Re: LARGE MS-SQL TDP backup keeps failing
>> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>>
>> I don't think there is a firewall.
>>
>> Well, it got further (700GB) before being killed by the TSM server.
>>
>> 9/6/2011 12:05:04 PM ANR0524W Transaction failed for session 59224 for
>> node ACIPENSER.VCU.EDU (TDP MSSQL Win32) - data transfer interrupted.
>> 9/6/2011 12:05:05 PM ANR0487W Session 59224 for node ACIPENSER.VCU.EDU
>> (TDP MSSQL Win32) terminated - preempted by another operation.
>>
>> At this rate, I don't think it is possible to back it up, especially if
it
>> is making this 1-4TB transaction.
>>
>> I again have to ask the question - can you tell the SQL TDP to break-up
>> the backup into multiple transactions, like you can with the Oracle
TDP?
>>
>>