Why do VSS Snapshots cause Availability Groups to fail over? Why do VSS snapshots cause Availability Groups to fail over?
Back in 2018, Ken Kellman and Erik Darling wrote that by freezing I/O on databases, VSS snapshots can cause Availability Groups to fail over.  https://www.brentozar.com/archive/2018/01/perils-vss-snaps/
According to Erik, &quot;the redo threads go buck wild on the other end.&quot;
OK.  I've got buck wild redo threads.  What does that mean?
I'm seeing one of my Availability Groups fail over on nearly a daily basis.  This usually happens right around the time our Avamar server backups run.  Is there anything that can, or should, be done to tame these buck wild redo threads of mine, and prevent this daily failover?
The failover policies are configurable - so you can adjust the thresholds
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-flexible-automatic-failover-policy?view=sql-server-ver15
of course to do this you need to know which policy triggers the failover in the first place
https://techcommunity.microsoft.com/t5/sql-server-support/diagnose-unexpected-failover-or-availability-group-in-resolving/ba-p/318474