I have a working Exchange 2010 setup here. I have 2 sites, connected via a dedicated 30Mbps WAN connection.
I have 1 mailbox server in each site, both mailbox servers participate in 1 DAG.
Site 1 holds my Witness server.
The DAG works as expected, when everything is online. When I have a break in my WAN connection, is where I get problems.
When the WAN goes down....
Site 1, with the witness server, acts as expected. The local DB stays online, and the replicated DB mounts....as it should.
Site 2, without the witness serveris where i have the issue. The replicated DB from site one goes into a 'services down' state, as expected. HOWEVER, the primary DB on the server, goes into a "FAILED" state, and stops service for that DB.
I assume this is because both the mailbox server in the DAG, and the witness server are unavailable?
Well I can only have 1 witness server, so it has to be somewhere. Wherever it is, the other site loses it's DB's, during an outage. This really stinks.
What can I do about it?
I have thought of creating 2 DAG's, and each site having a local witness server. The only issue is that each Mailbox server can only be in 1 DAG, so I'd have to have another server at each site, just for this purpose. Licensing alone, plus resource utilization makes this a clunky solution.
I also found this online, it talks about "alternate" witness server;
Set-DatabaseAvailabilityGroup -Identity DAG1 -AlternateWitnessDirectory C:\DAGFileShareWitnesses\DAG1.contoso.com -AlternateWitnessServer EXHUB3
However, I put this into my config, and I get the same results. Not sure if this command is supposed to do what I want it to do, but by the terminology it would seem so, but maybe not.
What can I do about this? having my local DB go into a FAILED state just because the WAN is out, is a terrible setup.