AlwaysOn 2012 Failover has problem: fails

Question

Hi all,
this is my first post ever, so I apoligize if I'm not doing well.
We installed SQL Server 2012. All good!
We configured AlwaysOn High Availability Group. Some problems but all good!
We are testing and we are having some problems. If we shutdown node A all resources go to node B and all still working. When we just stop the SQLServer service the role doesn't failover. What we noticed is that the listener and the IP don't go the node B.
If I force manualli the role to move to node B all work fine.
What could be the problem?
For me is the WFCI that doesn't feel correctly the fail of the service and don't move the IP to node B: I investigated in the dependencies but I couldn't figure out how to set them.

Answer 1

Hi Fabio,
According to your description, you have configured the AlwaysOn High Availability Group with node A and node B, then you tried to test the failover, at first time when you shutdown node A it failed over successfully, but after that when you stopped the SQL
Server service it did not failover, right?
As far as I know, the cause of this issue may be that you've reached the WSFC failure threshold during your test of the failover.
The WSFC failure threshold is defined as the maximum number of failures supported for the availability group during a given time period. The default time period is six hours, and the default value for the maximum number of failures during this period is
n-1, where n is the number of WSFC nodes.
If an availability group exceeds its WSFC failure threshold, the WSFC cluster will not attempt an automatic failover for the availability group. Furthermore, the WSFC resource group of the availability group remains in a failed state until either the cluster
administrator manually brings the failed resource group online or the database administrator performs a manual failover of the availability group.
For more information about Flexible Failover Policy for Automatic Failover of an Availability Group (SQL Server), please refer to the following article:
http://msdn.microsoft.com/en-us/library/hh710061.aspx
As you have only two nodes in this case, so it only be able to automatically fail over once during six hours. In order to change the failure-threshold values for a given availability group, we can use the WSFC Failover Manager Console. For more details about
these steps, please refer to the following article:
http://blogs.msdn.com/b/sqlserverfaq/archive/2012/03/15/inf-alwayson-the-secondary-database-doesn-t-come-automatically-when-the-primary-instance-of-sql-server-goes-down.aspx
If you have any question, please feel free to let me know.
Regards,
Jerry Li