CCR/SCR design query

Posted on 2010-03-28
Medium Priority
Last Modified: 2012-05-09

I had a theortical query on CCR/SCR in Exchange 2007 that I was hoping someone could help me with.

Let's say I have a Main Office site in London, UK. The DR site is in Swindon, UK. There is a good WAN link between the two sites.

From what I understand, a good DR strategy for Exchange 2007 would be:

- Have a CCR/SCC cluster located in London with Hub Transport and CAS servers.
- Have an SCR target located in Swindon, also with Hub Transport and CAS servers.

However, how about this idea:

Have just one CCR cluster, but with one node in London and one node in Swindon (with HT/CAS in both locations).

Would this work? I can't see any reason why not and it would actually cut down on hardware expenditure? The amount of data replicated is still the same isn't it?

Secondly, is there actually any need to have a CAS server in the DR site?

Thirdly, wouldn't the CCR only method work better considering we'd need to upgrade to 2010 at some point, and 2010 does not support SCR/SCC?
Question by:kam_uk
LVL 74

Accepted Solution

Glen Knight earned 668 total points
ID: 28900529
Ok what you really need is an SCR (Standby Continuous Replication) cluster.
This is designed for DR.  Have a read of: http://technet.microsoft.com/en-us/library/bb676502(EXCHG.80).aspx

what ever you do now will not he replicated for Exchange 2010 as we now have the Database Availability Group (DAG) I have written an article on it here:  http://www.experts-exchange.com/articles/Software/Server_Software/Email_Servers/Exchange/High-Availability-Exchange-2010.html

and since there is no in-place upgrade to Exchange 2010 you would need to build a new cluster and migrate to it.
LVL 37

Assisted Solution

by:Jamie McKillop
Jamie McKillop earned 668 total points
ID: 28903925

You can setup your CCR cluster so that one node 1 is in one site and node 2 is in another site but there are some pitfalls. You would need to have both sites in a single AD site. You would need/want a CAS server in each site for DR. The reason you would want a CCR node at each site is in case one whole site goes down. It does you no good to have the mailbox server up but no CAS server available. You would also need a Hub transport server in each site for the same reason.

Here is a good explanation of some of the problems you would encounter with a multi-site design - http://msmvps.com/blogs/clusterhelp/archive/2008/02/19/ccr-and-multi-site-environments.aspx

LVL 58

Assisted Solution

tigermatt earned 664 total points
ID: 28906715

You're correct. Exchange 2010 doesn't support CCR/SCR, which were complicated to say the least. 2010 simplifies the database model greatly into the Database Availability Group/Mailbox Copy structure, as demazter already indicated.

There are a number of considerations you need to take into account with cross-site CCR. There are placement issues for the File Share Witness (if you only have two nodes and an FSW and your FSW site burns down, the backup site won't have quorum so the cluster will not start automatically). Similarly, you won't get true "failover" (within a matter of minutes) because the DNS change for the cluster must be replicated. You must also extend the Active Directory site to the backup data centre, since CCR nodes cannot be deployed across AD sites.

That said, what you MIGHT want to consider is a mix of CCR and SCR, or simply opting for Exchange 2010 DAG. You can deploy a mix of CCR and SCR, with intra-site CCR backed up by SCR to another site for off-site backup purposes.

Note also that SCR requires manual admin intervention to fail it over, whereas CCR provides typical clustering capabilities with automated failover in the event of an outage.

I would seriously suggest you consider Exchange 2010 DAG. The deployment model has been vastly improved. You can also save on licensing and hardware by deploying roles other than the Mailbox role on the DAG Mailbox Server (you are restricted to only the Mailbox role on a CCR/SCR host).


Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

There are literally thousands of Exchange recovery applications out there. So how do you end up picking one that’s ideal for your business & purpose? By carefully scouting the product’s features, the benefits it offers you, & reading ample reviews f…
Migrating Exchange data from one Exchange Server to another server is complicated. Though Exchange administrators can try manual methods to migrate their data from one version of Exchange to another, these manual methods are not that reliable. That…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
To export Lotus Notes to Outlook PST or Exchange and Domino Server files to Exchange Server or PST files with ease, go for Kernel for Lotus Notes to Outlook conversion tool. Through the video, you can watch the conversion process. A common user with…

587 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question