April 8, 2016 at 5:48 am
All, I am wondering if I can get some help. I have AG configured between 2 servers AG1 which is primary and AG2 which is secondary. Now time to time, it fails over randomly. This week it failed over twice but last week it didn't fail over at all. 2 weeks ago, it had failed over twice as well. I have checked the SQL Server log file and so far this is what I have found. "windows server failover clustering (wsfc) node has lost quorum". I don't know where else to look for possible cause.
April 8, 2016 at 6:20 am
It's worth looking at the cluster event log on the server for any errors. Also there should be a diagnostic extended event file in there. The file itself is under ../MSSQL/Log/<SERVERNAME_INSTANCE_SQLDIAG*.XEL
I had this problem myself last night and was due to the primary losing connection with the secondary and causing the cluster service on the secondary to stop
April 8, 2016 at 6:22 am
April 8, 2016 at 1:49 pm
Chitown (4/8/2016)
All, I am wondering if I can get some help. I have AG configured between 2 servers AG1 which is primary and AG2 which is secondary. Now time to time, it fails over randomly. This week it failed over twice but last week it didn't fail over at all. 2 weeks ago, it had failed over twice as well. I have checked the SQL Server log file and so far this is what I have found. "windows server failover clustering (wsfc) node has lost quorum". I don't know where else to look for possible cause.
Are the servers same site?
What quorum model have you chosen for your windows server failover cluster?
Have you run a cluster validation report?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply