Thanks David, it would be great to get that functionality introduced.
The backup problem isn't really anything to do with SQL (we're taking a backup of the VM only excluding SQL), it's due to the server being stunned by VMWare. The SQL AG sees the I/O being paused because of the stun and tries to failover the AG. At the same time, the secondary node is being stunned and SQL decides the whole cluster is dead and kills itself.
The solution is either to put a gap between the stuns and let the AG failover, or even better, do a controlled failover from one node to the other. Both would require me splitting the backup in two because of the freeze/thaw parameter limitations unfortunately.
The backup problem isn't really anything to do with SQL (we're taking a backup of the VM only excluding SQL), it's due to the server being stunned by VMWare. The SQL AG sees the I/O being paused because of the stun and tries to failover the AG. At the same time, the secondary node is being stunned and SQL decides the whole cluster is dead and kills itself.
The solution is either to put a gap between the stuns and let the AG failover, or even better, do a controlled failover from one node to the other. Both would require me splitting the backup in two because of the freeze/thaw parameter limitations unfortunately.
Statistics: Posted by ratkinsonuk — Apr 28, 2025 3:29 pm
