I am wanting to add a 3rd 2010 Exchange server to my already existing environment, but I want to place this new server at a remote site as a DR system incase the primary site goes offline.
Currently, my remote offices are all connected to the Texas data center via VPN tunnels. I have EX-01 and EX-02 at the primary site, each have the client, hub, and mailbox roles installed.
The Mailbox DBs are DAG'd together, EX-01 as the active server & EX-02 as the passive. I do not have the CAS array load balanced at this time but would like to add this capability in the future.
Here is my Plan:
I'll add a secondary site in North Carolina and connect the primary site (Texas) to the secondary using VPN tunnels.
I'll stand up EX-02 at this site and add this server to the existing DAG and CAS array.
This server will hold passive copies of the Mailbox DB from EX-01
After this server is fully configured, I'd like to hardware load balance (HLB) the CAS array.
My current scenario:
A natural disaster hits the Texas data center knocking it offline. My users will be without email access (meaning I have no DR).
Scenario with EX-03.
A Natural disaster hits the Texas data center knocking it offline. I'd update the external mx record to point to EX-03 at the data center in North Carolina. I'd also update the CAS array internal DNS entry to point to EX-03 for remote offices.