We recently ran into an issue with our Exchange 2007 servers using CCR not properly failing over to the standby cluster node. Our suspicions for this failure point to the existence of Distributed Transaction Coordinator as a cluster resource. A bit of background: Exchange 2007 was setup on the server first along with the failover clustering. After Exchange was setup, we installed our backup software (Acronis) which requires DTC. We suspect the installation of DTC for Acronis put DTC in the cluster resource list. DTC, as a cluster resource has failed, but works fine for the backup software. My question is: since DTC is not needed in a CCR environment, can it be safely removed from the cluster group, or is Exchange relying on it just because it’s there? We are having and issue with Exchange’s Share Witness, but want to either fix or remove DTC before the witness issue is addressed. DTC’s only dependencies are Name and Witness.

“Exchange 2007 removes the requirement for the clustered MSDTC resource. Clustered mailbox servers in a CCR environment do not use and do not need the MSDTC resource installed in the failover cluster” ----------Refer to <Planning for Cluster Continuous Replication>James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

So, to be on the safe side and take baby steps with this: if I removed the two dependencies from DTC, things should remain up? Once I breathe a sigh of relief after that, I could then safely remove the DTC resource from the cluster and be in the clear. I am trying to take this in baby steps. We have had a rough time with this setup and solving this problem will be a big step in the right direction for us. Thank you for your help!

Since exchange doesn’t use DTC, I think the removal action is purely related to windows clustering part. Just make sure there’s nothing else require this resourceJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com