Eric, we use TDP for Exchange 5.5.x on our Exchange 2007 servers. We have about 
450GB spread over 10 databases that we perform a full backup on every night. 
During the day, we perform a standard TSM 5.5.x client backup of our logs every 
hour. The nightly fulls take about seven hours. My Exchange database is hosted 
on several LUNS over a 4Gb SAN.

Since our data fits into a backup window where users are not impacted by the 
full backup I did not implement TDP for Exchange on the passive node of our CCR 
cluster. TDP for Exchange does support that configuration if you need to take 
the backup load off your primary server.

Ray

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Eric Vaughn
Sent: Thursday, August 19, 2010 9:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Backing up Exchange 2007 with TSM

Hello,
Can anyone give me insight as to what products TSM has in conjunction with 
backing up Exchange 2007 with TSM? We have migrated off of groupwise and now 
have implemented Exchange. My concern with using the windows Baclient that we 
normally use with TSM will not back up exchange they way I would like. Since 
TSM would be backing up exchanges .edb files and transaction logs my concern is 
that the initial 700 gb backup will potentially grow out of control, even if I 
stager days. Does ibm offer a product that reads just the incremental changes 
of the database files as to limit the massive amount of space rather than 
backing up each .edb file each night, since tsm will see it as a new file and 
not a change (since TSM does incremental changes)? Or does anyone have any 
guidance as to what they have implemented? I also don't believe that a snapshot 
would be a solution either. Any help would be much appreciated.

Eric Vaughn
System Administrator
Stevenson University
44-334-2301

________________________________
Stevenson University 1525 Greenspring Valley Road, Stevenson MD 21153-0641 
1-877-468-6852


CONFIDENTIALITY NOTICE:  This email and any attachments are for the
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return email and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.