One Comment

  1. […] VMware snapshots playing havoc with availability groups – Mark Read. Share with your social network DBA’s, have you ever woken up one morning and found your SQL 2012, 2014 or 2016 Availability Group had mysteriously failed over during the wee hours? Of course there can be several legitimate reasons why it failed over (Windows Cluster or Quorum issue, O/S resources, SQL Server/node rebooted, SQL Services restarted, lost network connectivity, storage went offline, etc), but then there are those weird and seemingly unexplainable events that get you scratching your head after a look in all the obvious places for a smoking-gun. […]

Leave a Reply