We have Microsoft Exchange server running on local data center and we want to create EC2 replica and synchronize local and cloud instances, just in case local server goes down, to switch the traffic to EC2.

I' ve already searched through the AWS for service that does this, but I didn't find anything, so I'm Asking You if there is any AWS service that I can use for this problem, or it has to be done manually?



It looks like you're talking about sending a snapshot of your local exchange server to AWS?

That's not likely to work terribly well, Exchange's system works around transactional databases that need to keep their integrity in order to function properly, and snapshotting is likely to mess with that. Also, I suspect you'd lose email while stuff was "in flight".

To make this work reliably, you'd want a "local" DC in your AWS virtual server farm, or the AWS service Tim suggests, and it would still be a bodge. You'd be better off working with the High Availabilty options built into Exchange itself, such as Database Availability Groups (DAG). Microsoft have some good documentation on how this might work here.

Keep in mind that you're also going to need to think about updating DNS to deliver email to the right server in your scenario (you can't have multiple MX records existing in your scenario or you'll lose email when a temporary 'blip' in your main system's availability causes messages to go the second MX entry). This isn't an "instant switch over" option if something goes down in the middle of the night, and also DNS TTL will be a factor.

If you really need your Exchange email to be highly available and you're obviously not against using cloud services to achieve that, I would suggest the best option of all would be to use Office 365 and Azure Active Directory. I've got several thousand mailboxes in O365 and I just don't worry about Exchange availability any more because Microsoft do a great job.

|improve this answer|||||
  • thank You very much for the answer, me and my team will consider Your suggestions. In the mean time, I' d like to provide You with more details about our local infrastructure. We curently have 2 instances of Echange server on local cluster and transactions are completed after writing is finished on both of these instances, so we want to have one more instance running on isolated location(AWS) in STANDBY mode, just in case local cluster goes down, to switch to that cloud instance. – Miodrag Lazarevic Aug 12 '18 at 9:39
  • Ah, that changes things somewhat. I got the impression you had a single server from the original post. Going with what you have and my thoughts, might be worth creating a lagged DAG in AWS? – Rob Moir Aug 12 '18 at 11:16
  • Thank You very much Rob, I will consider DAG for solution and if I had some problem with the implementatiion, would You mind if I ask You? – Miodrag Lazarevic Aug 12 '18 at 11:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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