3 ms·
What kind of backup solution are you expecting? Every selfhosted app runs in docker, where the backup solution is back up the folders you mounted and the docke
by hamdingers 1y ago
What kind of backup solution are you expecting?
Every selfhosted app runs in docker, where the backup solution is back up the folders you mounted and the docker-compose.yml. To restore, put the folders back and run docker compose up again. I don't need every app to implement its own thing, that would be a waste of developer time.
- tracker1 1y ago+1 for the above... all my apps are under /app/appname/(compose and data)... my backup is an rsync script that runs regularly... when I've migrated, I'll compose down, then rsync then rsync to the new server, then compose up... update dns, etc. It's been a pretty smooth process. No, it's not a multi-region k8s cluster with auto everything.. but you can go a long way with docker-compose files that are well worth it.
- turtlebits 1y agoThat doesn't work for databases unless you stop the container. You'll likely end up with a corrupt backup.
- esseph 1y agoStreaming replication to a read-only DB off-site. Shut that one down and back it up from time to time. Then copy that to a third site with rsync/etc
- hamdingers 1y agoThen stop the container. A self hosted app can have a few minutes of downtime at 3am while the backup script runs.
- mamcx 1y ago? Any decent RDBMS can be backup live without issues. You only need to stop for restore (well without going with complex tricks)
- turtlebits 1y agoYes, but not by "simply" snapshotting the volume/disk as the previous poster suggested.