Mac80
asked on
Single Exchange 2010 DR scenario
Hi,
I have single Exchange Server 2010 running all the roles in one single server. (Cas,Hub,Edge, mailbox).
I want to have DR solution at DR site.
We can replicate the VM to DR site but how we will trigger the DR for exchange ?
We dont want to increase too many exchange nodes as each instance cost us money.
What would be the step for manual failover in above case ?
regards
Kamal
I have single Exchange Server 2010 running all the roles in one single server. (Cas,Hub,Edge, mailbox).
I want to have DR solution at DR site.
We can replicate the VM to DR site but how we will trigger the DR for exchange ?
We dont want to increase too many exchange nodes as each instance cost us money.
What would be the step for manual failover in above case ?
regards
Kamal
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Simon.
I need to know what changes are required when Primary server goes down.
Where to update the DNS, mx record..what else ?
I don't have CAS array. Max I can do is have Two exchange servers with all the roles on them at Primary side and one Server with all the roles at DR.
In that case, I have atleast some HA at Primary. Can I create a CAS in those two servers having all other roles ?
I need to know what changes are required when Primary server goes down.
Where to update the DNS, mx record..what else ?
I don't have CAS array. Max I can do is have Two exchange servers with all the roles on them at Primary side and one Server with all the roles at DR.
In that case, I have atleast some HA at Primary. Can I create a CAS in those two servers having all other roles ?
CAS array can be created with one or more server. It is just a DNS entry and a command in Exchange. Takes less than two minutes to create. However it will require the clients to repair their profile to be fully deployed.
If you have two servers in a DAG, then you can have the MX record point to both servers.
All other DNS records can be moved to the other server in the event of a problem, but due to caching it can take 24 hours or more before they are fully effective.
Simon.
If you have two servers in a DAG, then you can have the MX record point to both servers.
All other DNS records can be moved to the other server in the event of a problem, but due to caching it can take 24 hours or more before they are fully effective.
Simon.
Does it require DAG setup or it can be done using VM based replication ?
Use a DAG, which will replicate the data to the other server in real time.
It will also allow you to patch your live server while maintaining mail flow.
The two servers need to be on the same OS - that means wither Windows 2008R2 Enterprise or Windows 2012 Standard. Their storage layout also needs to be the same.
In the event of a server loss, you would simply rebuild the server, then install Exchange using the recovery switch, then reseed the database. While you are doing that users would continue to use the other server.
The biggest headache with retrofitting a DAG is that you need to have a CAS array to allow you to control where the clients point. While you can configure those at any point, the clients will not pick it up automatically.
Simon.