Back to all scenarios
Scenario #371
Storage
Kubernetes v1.26, Velero with CSI VolumeSnapshot
Volume Snapshot Restore Misses Application Consistency
Snapshot restore completed successfully, but restored app data was corrupt.
Find this helpful?
What Happened
A volume snapshot was taken while the database was mid-write. Restore completed, but database wouldn't start due to file inconsistencies.
Diagnosis Steps
- 1Restored volume had missing WAL files.
- 2Database logs showed corruption errors.
- 3Snapshot logs showed no pre-freeze hook execution.
Root Cause
No coordination between snapshot and application quiescence.
Fix/Workaround
• Integrated pre-freeze and post-thaw hooks via Velero Restic.
• Enabled application-aware backups.Lessons Learned
Volume snapshot ≠ app-consistent backup.
How to Avoid
- 1Use app-specific backup tools or hooks.
- 2Never snapshot during heavy write activity.