Exchange 2007 CCR
Have a customer with current Exchange CCR implmented:
-Both nodes are on the 10.x.x.x vlan
-2 HUB/CAS servers load balanced on 10.x.x.x vlan (one of these servers curently act as the Windows 2008 Failover Cluster FSW)
-All Exchange servers using Windows 2008 SP1 and Exchange 2007 SP1
Customer has a Disaster Recovery site on a different VLAN 192.168.x.x
Customer would like to split the CCR and have the following configuration:
-Active node would reside in 10.x.x.x vlan
-Passive node would reside in the 192.168.x.x vlan
-FSW HUB server on the 10.x.x.x vlan
-DR HUB/CAS server on the 192.168.x.x vlan
-All Exchange servers will be Windows 2008 SP1/Exchange 2007 SP1
I have an idea of my approach but I wish to ask the following questions to the community for clarification of the processes to take:
1. What are the best practices for such a split on a pre-exisitng CCR solution
2. Has anyone ever performed such a feat and what are any gotchas that should be watched for, prepared for, etc
Thanks all
Rich
-Both nodes are on the 10.x.x.x vlan
-2 HUB/CAS servers load balanced on 10.x.x.x vlan (one of these servers curently act as the Windows 2008 Failover Cluster FSW)
-All Exchange servers using Windows 2008 SP1 and Exchange 2007 SP1
Customer has a Disaster Recovery site on a different VLAN 192.168.x.x
Customer would like to split the CCR and have the following configuration:
-Active node would reside in 10.x.x.x vlan
-Passive node would reside in the 192.168.x.x vlan
-FSW HUB server on the 10.x.x.x vlan
-DR HUB/CAS server on the 192.168.x.x vlan
-All Exchange servers will be Windows 2008 SP1/Exchange 2007 SP1
I have an idea of my approach but I wish to ask the following questions to the community for clarification of the processes to take:
1. What are the best practices for such a split on a pre-exisitng CCR solution
2. Has anyone ever performed such a feat and what are any gotchas that should be watched for, prepared for, etc
Thanks all
Rich
cmccall
Make sure you have a fat data pipe between the two. You will probably want to increase the heartbeat timeout period. If you can't get network latency between the sites down to less that 50 ms, I wouldn't try it. You are better to put an SCR target in the 192.168.x.x site. You also want to make sure that your FSW is in the same site as your preferred node. Some backup solutions have trouble backing up when the cluster is in the DR site. You might need to take this into consideration as well.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.