ekm51
asked on
Exchange 2013 cu2 DAG implementation
We're planning a Exchange 2013 Cu2 DAG and had a few questions:
1) I've read if the DAG cannot maintain quorum databases will dismount. ie - In a 2 node DAG if you have 1 node down and you lose connection to the witness server you're pretty much screwed. Does this change in a 3 or 4 node DAG?
2) Is there anyway of clustering the witness server? Without redundancy on the witness server it seems like we still have a single point of failure for the entire environment.
We're planning on running a Exchange 2013 CU2 std 3 node DAG on 2008 Server R2 enterprise. It will be a 4 node DAG once our second datacenter is complete.
Thanks!
1) I've read if the DAG cannot maintain quorum databases will dismount. ie - In a 2 node DAG if you have 1 node down and you lose connection to the witness server you're pretty much screwed. Does this change in a 3 or 4 node DAG?
2) Is there anyway of clustering the witness server? Without redundancy on the witness server it seems like we still have a single point of failure for the entire environment.
We're planning on running a Exchange 2013 CU2 std 3 node DAG on 2008 Server R2 enterprise. It will be a 4 node DAG once our second datacenter is complete.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.