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

AlwaysOn SQL 2014 Windows failover Cluster issues

Hi Experts, We have upgraded SQL Server 2014 Alwayson and we are getting issues on cluster sudden failures. the cluster fail-over happening suddenly and getting resolved automatically after sometime. please see the below cluster event error messages and guide me how can I resolve those issues.

1.      Cluster node 'ABC' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
 
2.      File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\xyz20p\srv23pQuorum$'. Please ensure that file share '\\xyz20p\srv23pQuorum$' exists and is accessible by the cluster.
 
3.      Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed. Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
 

Thanks,
Sreenivasa
0
tschary
Asked:
tschary
  • 4
  • 3
  • 2
1 Solution
 
lcohanDatabase AnalystCommented:
I assume you have left the default heartbeat and if the share where the quorum sits is "unavailable" for any reason for more than the heartbeat interval your cluster will automatically fail-over so you have 2 options - 1 good and 2 not so good but on some slower networks/connections to SAN you may have no choice:

1. make sure the share where quorum sits is 100% up no matter what
2. increase the heartbeat interval from default to a value that suits your connections.
https://blogs.msdn.microsoft.com/clustering/2012/11/21/tuning-failover-cluster-network-thresholds/
1
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Are you using a network share as Quorum?
1
 
tscharyAuthor Commented:
Hi Vitor, Yes. we are using network share as quorum. please help me and provide any more solutions.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Vitor MontalvãoMSSQL Senior EngineerCommented:
I never used a network share for Quorum and can't help you much with this.
Just know that if the share is down then the Quorum won't be available. You should check first for the availability of the share.
Also know that the network share shouldn't reside in any of the cluster nodes. Hopefully is not your case.
0
 
tscharyAuthor Commented:
Hi Vitor, Network share not reside in any cluster node. It is a separate server. Please let me know What are the best practices for quorum in this case.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
I usually use a SAN storage. I know that also works with a network share but besides the two validations I wrote above I don't have any expertise working with these kind of quorum.
0
 
lcohanDatabase AnalystCommented:
Did you had a look at the recommendations at the link I posted just because you have a "share" that looks like is not that reliable for whatever reason?

In particular did you read about:
<<
Relaxed Monitoring – Provides more forgiving failure detection which provides greater tolerance of brief transient network issues.  These longer time-outs will result in cluster recovery from hard failures taking more time and increasing downtime.
>>
I believe you should try that first and increase as suggested "with moderation" the SameSubnetThreshold to 15 or 20.
1
 
tscharyAuthor Commented:
Thanks lcohan. Sure I wil go through your recommendations and implement it. will get back to you soon.
0
 
tscharyAuthor Commented:
We have found another solution either net adapter issues and changed those  settings. Also heartbeat setting helped us.
0
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.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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