Hi

I'm getting the same messages in my logfile, .

Date 15/05/2020 08:58:26

Log SQL Server (Current - 15/05/2020 08:39:00)

Source spid290s

Message

UpdateHadronTruncationLsn(14) (force=0): Primary: 0:0:0 Secondary: 13707:432:1 Partial Quorum : 0:0:0 Aggregation: 13707:432:1 Persistent:...

Hi thanks for that, we are running on Windows Server 2012R2, with SQL Server 2016 STD SP2.

Also why did windows need to failover as it was the witness that went down and I still had 2 servers.

that's correct,  Though once fileshare became available I rebooted NSKLHR-GWDB01 to bring everything in sync and for databases to be accessible, I'm trying to understand why when the fileshare failed,...

On the screen shot the current host server is the primary. in this case NSKLHR-GWDB02

Within the nodes you have

nsklhr-gwdb01  1 vote

nsklhr-gwdb02  1 vote

When we lost the filewitness the current host...

Both nodes have 1 vote

Hi I have attached, ignore the offline witness, moved it away from the DC.

Hi,

I can see the primary server fall over to the secondary but the SQL Server AG on the secondary has not fallen over to become the primary.

Update to this,

I'm not using shared storage disks.

I have 2 nodes configured in failover cluster manager (Windows server 2012 R2), and file share on another server.

with a number of BAG on SQL Server 2016 SP2.

Clive