Since Exchange 2007 deployed, I’ve been asked many times what should be considered when designing a stretch Cluster Continuous Replication (CCR) server configuration. A stretch CCR is typically where you have 1 node in 1 physical datacenter and the other CCR node in a separate physical datacenter, typically connected over a private WAN link. This blog provides some of those considerations.
Consider a stretch CCR environment that spans 2 different data centers.
Consider the following potential issues when using stretched CCR nodes across 2 datacenters -&- same AD Site:
Maintenance & Monitoring
Those considerations listed above are the common ones that I run into. You may find other considerations for this type of design as it applies to your environment. At this point, you might be asking, “OK, so what should I consider as a replacement option?” For most scenarios, the requirements are typically:
With that in mind, here is a common solution:
This solution puts the CCR nodes in the primary datacenter and uses SCR to replicate the data to the secondary datacenter.
SCR can provide the remote datacenter failover capability that most are looking for. That might be a better solution than trying to geo-cluster a CCR server.