glennda Posted August 9, 2012 Posted August 9, 2012 Not sure if its my google skills failing me. Just trying to draw together a plan to replace 3 2007 Exchange servers with 3 2010 Exchange servers with DAG. Currently 3 x 2007 Sp1 boxes (to be upgraded to SP3 Prior to any move) 1 located with customer 2 at seperate Datacenters. Changes are replicated VIA Double Take. What we are looking to do is move to Exchange 2010 with all servers in a DAG group - all this is fine and dandy in my planning. The only part I can't seem to find out is the WAN requirements of DAG groups. Anybody able to find any documentation/information.
sukh Posted August 9, 2012 Posted August 9, 2012 As long as latency is less than 500ms between the members then you're supported. I would create multiple DAG's if you have active/active deployment. 1
glennda Posted August 9, 2012 Author Posted August 9, 2012 As long as latency is less than 500ms between the members then you're supported. I would create multiple DAG's if you have active/active deployment. Thanks Sukh - so as long as the latency is less the 500ms it doesn't matter on the speed of the connection? I'm planning three servers two in one Datacenter (offshore) and 1 in a secondary (connected via VPN in another country). They will not be Active/Active. This company handles financial data hence the need for multiple DC in various countries etc
Domino Posted August 9, 2012 Posted August 9, 2012 Should be fine, it's what we do between London and Boston. I'd suggest a new vlan for the DAG network though 1
glennda Posted August 9, 2012 Author Posted August 9, 2012 Awesome - all i could find was the info about the latency but nothing on bandwidth. Should be ok then Thanks!
sukh Posted August 9, 2012 Posted August 9, 2012 The bandwidth should be good enough for a good user experience. If deploying cache mode then you may want to rolloit/stagger cache mode if bandwdith isnt good. Aswell as have multiple OAB generation servers.
glennda Posted August 9, 2012 Author Posted August 9, 2012 (edited) The bandwidth should be good enough for a good user experience. If deploying cache mode then you may want to rolloit/stagger cache mode if bandwdith isnt good. Aswell as have multiple OAB generation servers. Bandwidth to the main server is fine - its the bandwidth between the DCs which is/could be the issue as it shares it with all the other servers. I think though we should be ok. Edited August 9, 2012 by glennda
sukh Posted August 9, 2012 Posted August 9, 2012 cant remember on top of my head but there is gc/dc to exch ration, its on technet. Also I thouht you were concerned aboit the WAN bandwidth?
glennda Posted August 9, 2012 Author Posted August 9, 2012 cant remember on top of my head but there is gc/dc to exch ration, its on technet. Also I thouht you were concerned aboit the WAN bandwidth? the thing I was worried about was the link between the two datacenters. The end users will only ever talk to the second datacenter if the primary datacenter has a catastrophic failure (with two separate copies of everything in separate parts of datacenter) and dr is envoked and the dr site is brought online in which case a slight performance hit is accepted.
sukh Posted August 9, 2012 Posted August 9, 2012 In that case you should be ok. I assume where ever the users are physically located they have a good connection to the primary dc. Otherwise that would be your concern.
sukh Posted August 9, 2012 Posted August 9, 2012 something to help you with calculating bandwidth if you wish to go into depth. Office Exchange Client Network Bandwidth Calculator
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now