Change IP address of Exchange 2010 - Disaster Recovery
-
Wednesday, May 12, 2010 3:38 PM
How does Exchange 2010 + DAG respond to IP address changes?
I would like to DR exchange 2010 using VMware SRM and EMC RecoverPoint. Would have 2 HT, 3 CAS and 3 MB with DAG locally. Would replicate all virtual machines and Exchange 2010 DB/Log to DR site. Would use SRM to bring all virtual machines online and change IP addresses to DR site IP Space. Is this change in IP possible/supported in 2010?
Thoughts:
1.) Would have to add the DR site subnets into the DAG MAPI (non-replication) network.
2.) Would DAG recognize existing interface (NIC) with new IP address?
Thank you!
Josh
All Replies
-
Wednesday, May 12, 2010 4:35 PM
Clients don't connect to the Dag IP address in any way.
The mailbox servers in the DR site will most likely have their IP addresses on a different subnet. But that's nothing you need to worry about. Clients connect to the store using the RpcClientAccessServer field on the MailboxDatabase object. So as long as that's resolvable, you're fine.
-
Thursday, May 13, 2010 10:56 AM
You need to stretch the LAN accross brother. What you are trying to do as what i understand is to switch all servers IP on the fly to bring them up onto DR upon disaster.BUT you will not have one problem doing that, you will have bundle of issues and that is not the right approach.
how to stretch VLAN,
http://www.cisco.com/en/US/docs/solutions/Verticals/mstdcmsftex.html
Also btw DAG is what not user is connected to. Users get connected to CAS server in all cases in Exchagne 2010.
- Proposed As Answer by Shahid Roofi Thursday, May 13, 2010 10:56 AM
- Marked As Answer by Josh W_ Thursday, May 13, 2010 1:09 PM
-
Thursday, May 13, 2010 1:10 PM
Thank, Shahid. We talked this over yesterday and there are too many hidden issues. It's a square peg in a round hole. We are going to give Replication Enabler for Exchange from EMC a shot.
thanks!
Josh
-
Monday, November 01, 2010 2:11 AM
Josh,
what's the Replication Enabler you speak of? Is this specifically for Exchange 2010?
We've got pretty much the same issue, using Exchange 2007 with Recoverpoint using SRM to recover from one site to another. Stretching VLANs at this stage isn't an option.

