Database Backup Fidelity: Why Crash-Consistent Is Not a Database Backup

App-consistent database backup is the difference between a recoverable database and a recovery event that fails under pressure. Backup policies are designed by architects. They are discovered by engineers during recovery. Most enterprise environments have backup schedules running, retention policies configured, and dashboards showing green. What most have never validated is the consistency level those backups are actually capturing. That question gets answered — usually under pressure — when a DBA attempts to restore a production database and discovers the backup represents a storage snapshot taken mid-transaction. The Two Models At the storage layer, every backup is a point-in-time copy. The difference between crash-consistent and app-consistent database backup is what state the database engine is in when that copy is taken. Crash-consistent captures whatever was on disk at the moment the snapshot fired — no coordination with the database engine, no quiesce. Open transactions are mid-