Question on File Share Witness and quorum

We have two Exchange 2010 SP3 nodes in a DAG and a FSW. The two MB nodes are in the same Site but the FSW is in another Site. For whatever reason, our FSW became unvailable which should have been OK because the other two nodes were still up and running and we should not have lost quorum but the Cluster service on one of the nodes stopped and the mounted DB's on that node failed over to the other node. Everything is back to normal and I am suspecting a possible NIC glitch with the node that lost quorum and not a FSW issue but just wanted to confirm that in this setup, if the FSW goes down, the Cluster should not be affected?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mahesh SharmaCommented:
Yes, If FSW goes down, clsuter should not be affected. Active DB's should still be mounted.
If your FSW is down, you will still be able to activate the other database copy since you still have the majority of the votes up. If you have a problem with the FSW it only takes seconds to configure a new primary one.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
shadowtuckAuthor Commented:
Thanks. I think the issue is with the MB node itself, not the FSW as I suspected. I checked the event log on the MB that was complaining and saw Event ID 1135 which I remember from another Cluster I managed was a heartbeat issue. I wound up calling Microsoft on that one and they had me increase the heartbeat thresholds to the values below:


This happened during a backup so I am suspecting the heartbeat timed out and the MB server thought quorum was lost and failed over its DB's to the other server. Was just trying to validate my configuration here so thanks.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.