How to Restore CCR Functionality After a Failure or Divergence
Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Applies to: Exchange Server 2007, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3
This topic explains how to restore cluster continuous replication (CCR) functionality after the passive copy has been reported as diverged.
Failures can occur and then be manually or automatically recovered without causing a divergence. A divergence is reported in the event log after CCR has seen significant traffic since the last outage. This can be several megabytes of storage group changes. If a divergence is not reported, the administrator should assume that any issues were automatically recovered by CCR.
Before You Begin
To perform this procedure, the account you use must be delegated the following:
- Exchange Server Administrator role and local Administrators group for the target server
For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.
Procedure
To restore CCR functionality after a divergence using the Exchange Management Shell
Determine which node is currently the passive node. You can do this by running the following cmdlet in the Exchange Management Shell:
Get-ClusteredMailboxServerStatus -Identity:<Server>Follow the steps to seed the passive node that are in the topic How to Seed a Cluster Continuous Replication Copy.