How to fully replicate MS Exchange at Second Site

Here is our  setup:

1) 2 Locations connected by VPN (Cisco)
2) Both locations have all 2008 R2 Standard servers
3) Exchange 2010 SP3 at Primary location

Basically, we want to setup Exchange at the second site as well. We have two objectives:
1) Full replication so that if one goes down, the other can pick up the load
2) The clients at the second location treat the second exchange server as their primary server.

Just looking for a good hw-to link and some advice. Thanks!
JesusFreak42Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MIRSYSCommented:
This is not something that's done in 5 minutes. Find more info here:


http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html

Depending on the size of the company you could be better of just using virtualisation and then replicating the exchange VM to the remote site.
0
JesusFreak42Author Commented:
The problem is that the second location may be sold off in a year or two, so they want the impossible, i.e. a place that is both separate and integrated. :). In any case, they've already purchased the second machine for the second location.
0
Simon Butler (Sembee)ConsultantCommented:
It isn't really possible to do what you want reliably with two servers.

First you would need to change the host OS to either Windows 2008 R2 Enterprise, or Windows 2012. Then deploy a DAG. However Active/Active doesn't work well over separate sites, because you cannot maintain both sites if the link drops. Therefore you would need to have four servers total, two DAGs. Active/Passive (with the passive in the other location).

The processes to do so are all documented on TechNet.

Simon.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

MIRSYSCommented:
Well then you sure don't want to start deploying DAG and whatnot.
If they bought the machine then look into deploying a vmware vsphere essentials with a veeam license (will not cost much) and then you can virtualise the exchange on site 1 and replicate it to site 2

In case of problems you boot the exchange in site 2.

This will be a lot less hassle and headache.
0
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
There is an issue with MIRSYS' suggestion as you are relying on backups and in case of a failure on server in main site, powering the server in offsite will not be synchronized and you may need to do a dial-tone recovery whereas with a DAG, you may be out of sync by 15 minutes or so.  DAG would be the way to go and it also provides redundancy.
0
JesusFreak42Author Commented:
Hmmm.. OK. Two more questions:

1) Is it expensive to upgrade from standard to enterprise? I believe DAG's are the way to go.
2) Could I have basically each location be a "backup" for the other site? In other words, site 1 is active for site 1, but backs up site 2, and site 2 is active for site 2, and backups site 1.
0
Simon Butler (Sembee)ConsultantCommented:
The strategy I outlined above with four servers would do the backup for each site.
Buy a machine with enough horsepower to run both servers on the same physical server, then you only need two licences for Enterprise edition of Windows 2008 R2 - as you can have up to four virtual machines per physical server.
Although even with Windows 2012 you can have two VM per physical machine, which will probably be a cheaper way to go.

Upgrading your existing server to enterprise edition is NOT supported, so you would need to have new hardware for this task.

Simon.
0
JesusFreak42Author Commented:
Just a quick question on upgrading existing servers.... what is the link below referring to:

http://blogs.technet.com/b/server_core/archive/2009/10/14/upgrading-windows-server-2008-r2-without-media.aspx
0
JesusFreak42Author Commented:
Ok. So how does this plan sound
1.The server at Site 2 has not been setup yet. We can update this one to Enterprise.
2.Install Exchange at Site 2
3.Export the exchange server from Site 1 to Site 2.
4.Uninstall Exchange from Site 1
5.Upgrade Exchange server at site 1 to Enterprise.
6.Reinstall Exchange at Site 1
7.Go with the following scenario - "Two Exchange servers with CAS, HT and Mailbox and deploy hardware Load Balancer."'

My last question is whether the Cisco Small Business Routers we have will be able to function as as hardware load balancers.
0
Simon Butler (Sembee)ConsultantCommented:
Unless you have a lot of bandwidth between the two sites I wouldn't do as suggested.
If you have a server for site 2, then bring it site 1 so you can run both servers next to each other. That will allow you to have two servers local while you move everything around.
Furthermore it will make seeding easier, as you can seed the databases local and then move the server (with the copy) once complete. The only data that then has to go over the site connection will be what has changed while the server has been moved.

The small business routers will not be load balancers. You may not even need them if you are able to accept some downtime while DNS changes are made.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JesusFreak42Author Commented:
How much downtime are we talking about?
0
Simon Butler (Sembee)ConsultantCommented:
The only downtime will be at the end of the move mailbox process - so about a minute or two per mailbox.
When you come to move the servers there will be no downtime because the active server is still active.

Simon.
0
JesusFreak42Author Commented:
Simon,
    Thanks for walking me through some of this. We successfully setup both, but one of them is passive right now. When the second location opens up, we will be making a database for each location and making the database active at its home location. Then, if one of them dies, we can just activate the database at the location still functioning.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.