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.

Who is Participating?
Will SzymkowskiConnect With a Mentor Senior Solution ArchitectCommented:
The answer to your first question is yes. The second question is also yes as you can have multiple witness servers. You can have a secondary witness for your DAG.

You can do this from the ECP or EMS.

EMS: Set-DatabaseAvailabilityGroup (using the -AlternateWitnessServer switch)

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.

All Courses

From novice to tech pro — start learning today.