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.