Backing up active container databases can lead to corrupted files. Currently, Duplicati lacks a built-in method to handle this safely. For beginners like me, it is quite difficult to find a “recommended way” online, and setting up manual scripts feels like a significant barrier to entry.
I would love to see a native, “set and forget” implementation for containerized database backups. Since containers are standard in almost every HomeLab setup, a built-in solution would allow users to secure their data reliably without needing custom scripting.
I have explored two ways to handle this, but I would appreciate the community’s expertise on which fits Duplicati best:
-
Stop/Start Script: I wrote a script that stops containers before the backup and restarts them after: LennardPlay/duplicati-docker-scripts. (Feedback or improvements are very welcome!)
-
Live Export: Performing a safe database export while the container is running, similar to this project: container-db-backup.
Which method would be the most robust for a native integration? As a beginner, having this as a standard feature would make Duplicati the perfect tool for securing modern HomeLab environments.