Forum Discussion
SQL Server Failover Cluster Resource/Group stop itself due lost connection to storage
afiqazmi31 RodVK If you're willing to accept higher timeouts before automatic failovers, it appears that you want to adjust the Health Check Timeout.
select name, health_check_timeout from sys.availability_groups
As described in this Learn article, sp_server_diagnostics returns results at 1/3 of the timeout threshold.
Configure a flexible automatic failover policy for an availability group - SQL Server Always On | Microsoft Learn
sp_server_diagnostics is what checks the io subsystem.
In other words, to increase the acceptable timeout, set health_check_timeout to a higher value (milliseconds).
ALTER AVAILABILITY GROUP <AG> SET (HEALTH_CHECK_TIMEOUT = 60000);
Hi SivertSolem thanks for the reply but we are using Failover cluster instance, and the rhs.exe is bugchecking after storage seems to disappear after a failover. Not using Always on Availability groups.
Aah, apologies. That should have been given by using iSCSI as quorum.
The health check timeout is still configurable, but in this case in the Failover Cluster Configuration.
PowershellImport-Module FailoverClusters $fci = "SQL Server (INST1)" Get-ClusterResource $fci | Set-ClusterParameter HealthCheckTimeout 60000T-SQL
ALTER SERVER CONFIGURATION SET FAILOVER CLUSTER PROPERTY HealthCheckTimeout = 60000;