Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4532

SQL server 2017 always on: Manually fail over from primary node to secondary node--- never successed

$
0
0

Here is error message when I do from wizard or T-sql(ALTER AVAILABILITY GROUP group1 FORCE_FAILOVER_ALLOW_DATA_LOSS;)

Failed to bring availability group 'group1' online.  The operation timed out. If this is a Windows Server Failover Clustering (WSFC) availability group, verify that the local WSFC node is online. Then verify that the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again.

I checked Failover cluster manager and all online and green I checked Cluster events: no error log showup.

Any idea what happened? It failed again and again yesterday: "Server name" under "cluster core resources" offline yesterday.

Today, everything back online. Then I tried to manually fail over. Still failure and get those messages.

I try to reboot primary node: failover didn't happen. After primary restarted, I checked: everything is green(good) and no failover happened. 

Any help?Thanks




Viewing all articles
Browse latest Browse all 4532

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>