Hi Robert

I don't know if this is  relevant under 2010 but under exchange 2007 VSS
backups to TSM automatically ran a consistency check using a program
with 'ese' in the name as the shapshot to TSM portion of the process
ran, and this check was single-threaded.

Perhaps there is something similar happening under 2010.  Sorry its so
fuzzy but my memories of this are a year old now.

Regards

Steven Harris
TSM Admin
Paraparaumu, New Zealand





Robert Ouzen wrote:

Hi to all



Did anyone as tips to improve performance with  TDP for exchange 2010,  my 
backup is lanfree my old fashion EXCHSRV01_DB took  03:28 for 413 GB , the 
Exchange 2010 with VSS feature EXCHSRVB_DB took 02:01 for 184 GB.



The backup is thru DE duplication Data Domain on VTL.





Nodename

Activity

Data amount

Elapse time

Affected

Failed

Media wait

EXCHSRV01_DB                               Old Fashion

BACKUP

413.1 GB

0 03:28:30

54

0

110















EXCHSRVB_DB (EXCHSRVB)       New Fashion

BACKUP

184.7 GB

0 02:01:04

138

0

31



My TDP opt file looks like:



NODename          exchsrvb_db

CLUSTERnode       no

COMPRESSIon       Off

PASSWORDAccess    Generate

COMMMethod        TCPip

TCPPort           1500

TCPServeraddress  132.74.XX.XXX

TCPWindowsize     63

TCPBuffSize       32

DISKBUFFSIZE      32



INCLUDE "exchsrvB\...\full" MGEXCHANGE

INCLUDE "exchsrvB\...\incr" MGEXCHANGE



Tsm server version: 5.5.2.0

Tsm client version: 6.2.1.0

TDP for exchange 2010:   6.1.2.0

O.S: Winows 2008 64bit



T.I.A Regards

Robert Ouzen






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


No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.829 / Virus Database: 271.1.1/2947 - Release Date: 06/19/10 
06:35:00