Reseeding an Exchange CCR Node

  • Article

[For content updates, see Newly published content for Microsoft System Center Data Protection Manager.]

Cluster Continuous Replication (CCR) is a high-availability feature of Microsoft Exchange Server 2007 that combines the asynchronous log shipping and replay technology built into Exchange 2007 with the failover and management features provided by the Microsoft Windows Cluster service. When the active node stops working, the passive node in the cluster takes over as the active node. The administrator now must reseed a new computer and add it to the cluster as the passive node. The passive VSS writer then copies the databases and logs from the active node. Depending on the size of the data, this process can affect the performance of the active node.

Alternately, you can reseed the passive node using the last available recovery point from DPM. Using DPM to reseed the passive node gives you two advantages:

  • No effect on performance of active node.

  • No initial replica of new computer is required since it was built using the recovery point that DPM has.

Manually Reseeding an Exchange CCR Node

  1. Run the cmdlet suspend-storagegroupcopy on the Exchange cluster.

  2. Rename the .log, .chk, .edb files on the passive node.

  3. Using the Recovery Wizard, recover the last successful backup for the cluster from DPM to an alternate location.

    Warning

    Select Apply security settings of the destination computer.

  4. Move the database, .log and .chk files to their respective folders.

  5. Run the cmdlet resume-storagegroupcopy.