Zerobyte Backup of Running Containers / Open Files

[Ascar699]

@nicotsx Thank you for Zerobyte! I could not make it work through SFTP until I read the troubleshooting page. Now everything is working and looks great.
My main question before fully adopting Zerobyte as the backup tool of choice - how do we make safe backups of docker containers which are running or files which are open (app binaries, databases etc.). I don't know how to ensure data consistency and integrity. Perhaps you are thinking about adding a facility to send pre-run and post-run commands to the targets to stop and start containers or applications to the hosts?

I naturally counseled AI and I hear from Gemini the following:

Restic creates deduplicated point-in-time backups that it calls "snapshots," but on Linux, it does 
not natively use underlying filesystem snapshot technology (like ZFS or Btrfs) to freeze data. Because it reads live files 
sequentially, directly backing up a running Docker container's SQLite database with Restic can result in corrupted 
backups if writes occur during the read process.

Restic Snapshot Mechanics
Restic uses an algorithm called Content-Defined Chunking (CDC) to split files into variable-sized blobs, 
which are then deduplicated and encrypted before being saved as a "snapshot" in the repository. 
When running on Windows, Restic natively integrates with the Volume Shadow Copy Service (VSS) to read 
locked files safely. However, on Linux environments typical for Docker, Restic reads directly from the live 
filesystem without freezing it, meaning file modifications during the backup run can lead to 
inconsistent database states.

So whatever insight you can share will be appreciated.