If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
Implementing DAG in two site configuration
OK so we currently have 2 active sites (A&B) with an Exchange 2010 SP1 server at each site, with users accessing both and are looking to implement DAG's. We also have a 3rd site (C) that is used for hosting our spam appliances and intranet servers. All sites are connected via a WAN, in the same AD domain and each site is in it's own AD Site.
My main concern with implementing DAG's in this configuration is what happens if I lose WAN connectivity?
I've read that SP1 now supports this type of configuration and helps prevent the potential 'split-brain' situation through the use of DAC (Datacenter Activation Coordination)
I have questions though.
Where should I place my primary FSW?
Should I configure an Alternate FileShareWitness server?
Example: Could I have Site A + FSW and Site B + AltFSW? What would happen if I lost WAN connectivity?
In the future we plan to implement a 4th site with an Exchange server.
My main concern with implementing DAG's in this configuration is what happens if I lose WAN connectivity?
I've read that SP1 now supports this type of configuration and helps prevent the potential 'split-brain' situation through the use of DAC (Datacenter Activation Coordination)
I have questions though.
Where should I place my primary FSW?
Should I configure an Alternate FileShareWitness server?
Example: Could I have Site A + FSW and Site B + AltFSW? What would happen if I lost WAN connectivity?
In the future we plan to implement a 4th site with an Exchange server.
Asked:
4-
3
1 Solution
>> >> My main concern with implementing DAG's in this configuration is what happens if I lose WAN connectivity?
>>the site with no file share witness will go down due to loss of quorum
What would happen if I had an alternate file share witness at the other site?
>>the site with no file share witness will go down due to loss of quorum
What would happen if I had an alternate file share witness at the other site?
the concept of the alternate share witness is totally different, it is used only one you do a datacenter failover it is not for these scenarios
So if WAN connectivity is lost all the users at the site with no FSW will not be able to access email even thought they have a functioning email server in the same location as them? Seems kind of limited?
>> So if WAN connectivity is lost all the users at the site with no FSW will not be able to access email even thought they have a functioning email server in the same location as them?
exactly
>> Seems kind of limited?
DAG cross site was designed to be in a DR site as active/passive model and not as active/active. It could be better I know, hopefully exchange 2013 :)
exactly
>> Seems kind of limited?
DAG cross site was designed to be in a DR site as active/passive model and not as active/active. It could be better I know, hopefully exchange 2013 :)
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.
One of a set of tools we're offering as a way of saying thank you for being a part of the community.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
the site with no file share witness will go down due to loss of quorum
>> I've read that SP1 now supports this type of configuration and helps prevent the potential 'split-brain' situation through the use of DAC (Datacenter Activation Coordination)
it does but wan connectivity issues are still not supported