A crash-consistent snapshot is a block-level, point-in-time copy that preserves disk write order but does not flush database I/O coherently. It may leave SQL Server inconsistent when transactions are in flight. section 12.3 section 12.12
Mistake: treating a VM snapshot as a reliable database recovery strategy. The snapshot can appear valid until restoration, when buffered data and already-written data no longer describe one coherent database state. section 12.3
Bad-change rollback
A change plan restores a database-hosting VM after a failed deployment. If its storage protection is crash-consistent, the rollback may restore a corrupted database rather than a usable recovery point. section 12.3
Use these checks before relying on storage snapshots for SQL Server:
- Confirm that the provider supports application-consistent snapshots, not only crash-consistent snapshots. section 9.7
- Verify that Volume Shadow Copy Service (VSS) flushes pending I/O before the snapshot. section 9.7 section 12.3
- Keep validated database backups in the recovery strategy; use snapshots as a rapid-recovery complement rather than a replacement. section 12.12
