---
title: "Comment by Lakhyajit Changmai on \"Backups aren't simple\" | Hashnode"
description: "The consistency-group caveat in your post-discussion update is crucial for app-and-database backups: a file-level snapshot can be readable yet logically inconsi"
url: "https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c/comment/6af73fc63b7fa79a4a2fcc76"
---

[Discussion](https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c)

Comment [Backups aren't simple](https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c)

[Lakhyajit Changmai](https://hashnode.com/@lakhyajit)

[4h ago](https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c/comment/6af73fc63b7fa79a4a2fcc76)

The consistency-group caveat in your post-discussion update is crucial for app-and-database backups: a file-level snapshot can be readable yet logically inconsistent if the database and application state are captured at different points. I’d document the quiesce/snapshot/restore sequence and test it on a clean instance, using paused writes or a database-native consistent dump where appropriate. That turns “backup completed” into a reproducible recovery path.