Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have heard there is a limit to the distance which you can get Continuous Cluster Replication to work properly. Anyone have any insight on this? If so, What is the latency threshold where the CCR capability begins to break down?

Assuming ideal conditions, what is the largest distance I could separate my clusters geographically?

share|improve this question
up vote 1 down vote accepted

Some NetApp documents talk about this subject. Then indicate that Exchange 2007 requires disk latency below 20ms which usually translates to about 100 miles

Distance to the disaster recovery site. Remember that Microsoft Geographically Dispersed Clusters require network latency below 500ms, and Exchange 2007 requires a disk latency below 20ms, which typically restricts distances less than 100 miles between systems in the cluster. If the DR site is more than 100 miles away, then a solution other than or in addition to CCR is required.

share|improve this answer
That is precisely what I needed to know! Thank you.... – user13846 Jul 24 '09 at 13:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.