[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 727
  • Last Modified:

Exchange 2010 DAG, Windows Failover Clustering

I am troubleshooting a strange issue with our Exchange 2010 DAG in that it appears to lose the quorum at random times only to light right back up.  After doing a little more digging, I found that the 3 Cluster Core Resources all have different policies?  I have been pulling my hair out to find something that tells me whether this is correct.  Logically it would seem to me that they should match exactly.  I have attached 3 pictures of the 3 different resources and their settings.  The first is the actual "DAG" resource, the 2nd is the "DAG IP" resource and the third is the "FSW" resource

Should they all be different?  Should they match?  What's considered "best practice" for Windows Failover Clustering with Exchange 2010.  2 Nodes and a File Share Witness

If they should be different, can anyone help me understand why?  Additionally, if they should be different, are these the optimal settings?

Any help would be appreciated!  

Thank you!
  • 2
1 Solution
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Look DAG works with MNS "file share witness" also acting like a DAG .... so lets say i have One node in SiteA which is currently Active, now i have Passive node in SiteB with MNS being there as well. Now if the Connetivity fails between both the sites .... SiteB has the majority and Custer would fail to SiteB.

However if i have failed to userstand your query or you have some other query please do let us know.

- Rancy
JeremyricciAuthor Commented:
Hi Rancy,

This is actually a single site.  Our Exchange environment is fairly simple.  2 Hub/Cas servers 2 Mbox servers.  All on VMWare hosts.  So Hub/Cas1 and Mbox1 on one host, hub/cas2 and mbox2 on 2nd host.  

So there are 3 "nodes" in the failover cluster, Mbox1, Mbox2 and our FSW.  My question was more related to the policies of the individual cluster resources (like time for restarts and pending timeout) which are all set to different values.  

If you see the attached pictures, you'll see what I'm talking about.
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Hub/Cas1 and Mbox1 on one host, hub/cas2 and mbox2 on 2nd host - I like this :)
So its more of a failure point in case something happens to either Host :)

I guess these settings very much depend on your environment ...... it looks fine and not necessarily they all have to be the same as the functioning is not the same as well. Also if Active copy host goes down everything will automatically be failed-over to another node.

- Rancy

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now