Thanks for the reply. I agree that it sounds like a configuration issue. We are 
trying to do this via command line so it can be scripted and therefore 
automated.  I do have a problem open with IBM and sent them some logs and lots 
of information but their first was response was to tell me that it wasn't 
configured correctly as they were looking at early entries in the logs I sent 
them instead of further down. Lesson learned, delete all of your logs before 
recreating problem as support won't look at timestamps and first error they see 
must be the problem. <sigh> The command line I am using looks like this:
C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup <datastore> incr 
/fromreplica /backupmethod=vss /backupdestination=tsm /tsmoptfile="c:\Program 
Files\Tivoli\TSM\TDPExchange\dsm.opt"
I was getting it to create a TSM session but the session would just be WAITING 
on the server for hours and never actually did anything. FWIW, the datastore I 
am testing with is tiny.
Now when I try running the backup on the inactive CCR replica I get:
Updating mailbox history on TSM Server...
Mailbox history has been updated successfully.
Querying Exchange Server to gather component information, please wait...
ACN5241E The Microsoft Exchange Information Store is currently not running.
but as I mentioned before, according to my exchange admins, that service should 
never be running on both sides of the CCR cluster.
I have changed the dsm.opt and tdpexc.cfg options so many times with every 
option can think of which is why I was hoping someone had a sanitized version 
of their dsm.opt and tdpexc.cfg that are working in their environment I could 
look at.




Hi John, This looks like a configuration issue to me. Exchange Server 2007 CCR 
and LCR replica copies can be backed up and restored by using the VSS method 
only. Microsoft does not allow Legacy backups of Exchange Server 2007 CCR and 
LCR replica copies. Also keep in mind, all VSS Restores of a CCR or LCR replica 
can be restored only into the running instance of a storage group (primary, 
recovery, or alternate). Microsoft does not support VSS Restores into a replica 
instance. If you want to back up from the replica copy when running in a CCR or 
LCR environment, specify the "FromReplica True" backup option in the Protect 
tab of the MMC GUI. You can also specify the /fromreplica parameter with the 
tdpexcc backup command on the command-line interface. Here is the important 
one... For CCR copies, you must run the backup while logged on to the secondary 
node of the cluster that currently contains the replica copy and you must use 
the "FROMREPLICA" option. Here are a few more things: 
http://www-01.ibm.com/support/knowledgecenter/SSTG2D_6.4.0/com.ibm.itsm.mail.exc.doc/c_dpfcm_bup_replica_exc.html?cp=SSTG2D_6.4.0&lang=en
 If you are not able to get this working, you should open a PMR so that the 
service team can help you get the configuration working. Del 
---------------------------------------------------- "ADSM: Dist Stor Manager" 
<ADSM-L AT VM.MARIST DOT EDU> wrote on 10/31/2014 08:40:00 AM: > From: "Dury, 
John C." <JDury AT DUQLIGHT DOT COM> > To: ADSM-L AT VM.MARIST DOT EDU > Date: 
10/31/2014 08:42 AM > Subject: Anyone else doing replica backups of exchange 
datastores? > Need some help please. > Sent by: "ADSM: Dist Stor Manager" 
<ADSM-L AT VM.MARIST DOT EDU> > > I have been trying to get this to work for 
days now and I don't seem > to be making any progress. I have tried all kinds 
of options in both > the dsm.opt and tdpexc.cfg files and I get various 
messages. The > documentation in the TDP for Exchange manual on doing replica > 
backups is not very detailed at all. > Our environment looks like this. > We 
have two windows 2008 exchange 2007 servers setup for CCR > replication to each 
other. I am trying to do replica backups on the > offline cluster member so it 
doesn't affect performance on the live > cluster member. > The TSM server is 
6.3.4.300 running on RHEL5 linux. > I thought I had it working but nothing was 
actually backed up. The > TSM session was established on the TSM server but no 
data was > actually sent. The sessions appeared to be hung and seemed to > 
eventually timeout. > The other message I was receiving on the offline exchange 
cluster member was > Updating mailbox history on TSM Server... > Mailbox 
history has been updated successfully. > > Querying Exchange Server to gather 
component information, please wait... > > ACN5241E The Microsoft Exchange 
Information Store is currently not running. > but from what I was told by our 
exchange experts is that that > service only runs on the active cluster member 
and not on the offline member. > Below are my sanitized dsm.opt and tdpexc.cfg 
> dsm.opt > NODename exchange > deduplication no > CLUSTERnode yes > 
COMPRESSIon Off > COMPRESSalways On > PASSWORDAccess Generate > 
resourceutilization 5 > COMMMethod TCPip > TCPPort 1500 > TCPServeraddress 
tsmserver > TCPWindowsize 128 > TCPBuffSize 64 > diskbuffsize 32 > SCHEDMODE 
Prompted > SCHEDLOGRetention 14,d > HTTPport 1581 > tdpexc.cfg > BUFFers 4 > 
BUFFERSIze 8192 > clusternode yes > compression off > compressalways on > 
LOGFile tdpexc.log > LOGPrune 60 > MOUNTWait Yes > TEMPLOGRestorepath 
P:\TempRestoreLoc > LASTPRUNEDate 10/31/2014 06:55:09 > BACKUPMETHod LEGACY > * 
BACKUPMETHod vss > RETRies 0 > LANGuage ENU > BACKUPDESTination TSM > 
LOCALDSMAgentnode exchangeofflineclustertsmnodename > REMOTEDSMAgentnode 
exchange > TEMPDBRestorepath P:\TempRestoreLoc > CLIENTACcessserver > > Could 
someone who actually has this working send me their sanitized > 
dsm.opt.tdpexc.cfg and the actual command used to do a replica backup from the 
> offline cluster member? >