I have seen this before when mailbox migrations
from Exchange 2007 or Exchange 2003 are occurring
and creating large amounts of transaction log files.
The problem is that Microsoft requires the
integrity check and back up of all of these log
files before log truncation can occur. The integrity check
and back up of all those files can take a long time.

I recommend that you turn on circular logging
until mailbox migrations are complete.

Thanks,

Del

----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 04/13/2011
07:41:05 AM:

>> From: Sachin Chaudhari <schn999 AT YAHOO DOT COM>
>> To: ADSM-L AT vm.marist DOT edu
>> Date: 04/13/2011 07:42 AM
>> Subject: Exchange 2010 with TDP
>> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>>
>> One of my customer is facing major performance issue on MS-Exchnage
>> 2010 database backup.
>> Env Details
>> BA : V6.2.2
>> TDP-exch : v6.1.3
>> sta : v5.5.4
>> TSM Server : 5.5.4
>>
>> Database size : 500 GB
>> Transactional logs : say 100-150 GB (each has 1 MB in size)
>>
>> When we execute the backup via tdp (Copy backup) 500 GB data gets
>> transfered on tape in approx 4 hrs but the takes more time at the
>> time of transactional logs backup (i.e incremental bkp).
>> For about 150 GB of transactional log it was taking approx 25 hrs.
>>
>> Customer has three exchange nodes with multiple databases running
>> on same(Active-Passive combination), I had tested the backup from
>> multiple database passive DB copy, but results are same.
>>
>> Does anyone faced this kind of challanges? Pl share some inputs..
>>
>> Thanks,
>> Sachin