• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 467
  • Last Modified:

Exchange 2007 SCR Scenario

I have a 2008 Server that is a DC, DNS, and running Exchange 2007 SP1.  This Exchange 2007 server is running all of the exchange roles, and it is the only Exchange server in the environment.  I am trying to setup a DR plan because I am in South Florida and Hurricane season is approaching.  I will be acquiring a colocation facility and connecting to that facility via VPN.  I would like to setup replication between my production Exchange server and a server I put at the colo.  I have been reading a bit about SCR and was wondering if that solution would work in my scenario.  And if so, how would it work in a DR situation?
  • 2
1 Solution
Stephen CroftTechnical ArchitectCommented:
Are you going to put a server in colo and add it to your domain? If so, CCR is the way to go and will replicate logs (and therefore DB) over the vpn as long as it is consistant.

If you are not putting the server in colo into your domain, and just want to flatfile replicate, thats a little trickier. Depending on how much cash you can throw at it, my money would be on vmware SCR, which will replicate an entire VMware (ESX) scenario over a VPN link. This means all your DC's, DB's (SQL for example), and Data will get replicated too, and in the event of a failure, vmware will automatically switch and power on the remote scenario, giving you full access within a short time.

will cost a lot (servers + SAN + Licences etc) but it is, in my opinion, the best way to do it without sprawling your AD over a VPN link.
SCR would be fine. I am doing something very similar. It isn't a live failover, but that shouldn't be a problem. You will need a domain controller at the other end, as well as the Exchange server, therefore requiring two additional Windows licenses and an Exchange 2007 standard license.

As for how it works, that is all documented on Technet.

BSModlinAuthor Commented:
My grand plan is to Virtualize (hyper-v) my current production Exchange server.  Then put a vitual server (hyper-v) with a virtual machine running as a DC and have Exchange 2007 on it.  Then use SCR to replicate.  Is this viable?  If so, in a DR situation would I point my MX record to the colo?  Then when I get my production server back up how would I replicate back?
Don't try and combine Exchange and the domain controller on the same machine  -whether physical or virtual.
When Exchange is installed on a DC it affects the entire Exchange org. Exchange will only use that domain controller, which will include all other Exchange servers you have, so in this scenario there will be a performance impact.

As long as you have the same AV and antispam protection for the other server, there is nothing to stop you from having MX records pointing to both servers. During regular times email will come in and be delivered in the usual way, via either server. In the event of a loss of the connection, then email will simply queue on the second server until you intervene.

If you don't want to have MX records pointing to the second server at all, except in the case of a problem, then you may want to look at the dynamic DNS method to get the change made quickly.

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

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!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now