Arriving at a workable generic backup solution #30

New Issue

decentral1se · 2020-10-25T19:50:32Z

decentral1se commented

2020-10-25 19:50:32 +00:00

Current stab was https://git.autonomic.zone/coop-cloud/backup-bot.

Upsides:

Borgbackup, Borgbase, Borgmatic - pretty cutting edge radness
Kinda seems to work

Downsides:

It requires its own compose configs inside the repository
You need to remember to deploy it each time

Something more flexible and disconnected directly from the app repository would be ideal. There has been some research going on, so here comes the links:

Current stab was https://git.autonomic.zone/coop-cloud/backup-bot. Upsides: - Borgbackup, Borgbase, Borgmatic - pretty cutting edge radness - Kinda seems to work Downsides: - It requires its own compose configs inside the repository - You need to remember to deploy it each time Something more flexible and disconnected directly from the app repository would be ideal. There has been some research going on, so here comes the links: - https://github.com/futurice/docker-volume-backup - https://github.com/loomchild/volume-backup - https://github.com/blacklabelops/volumerize - https://janikvonrotz.ch/2020/08/18/backup-docker-volumes-with-this-script/ - https://github.com/ricardobranco777/docker-volumes.sh

decentral1se commented

2020-10-25 19:51:48 +00:00

backup-bot example working configs:

https://git.autonomic.zone/coop-cloud/wordpress/src/branch/master/backup.d

backup-bot example working configs: > https://git.autonomic.zone/coop-cloud/wordpress/src/branch/master/backup.d

3wordchant commented

2020-10-26 14:30:14 +00:00

Use-cases

Make & download an ad-hoc .tar.gz backup of all an app's volumes, like Yunohost / Cloudron
- Include stack config? I think it's available from docker inspect
- To not be super-frustrating I think the backups should be generated on the server and then downloadable in a separate command (like Yunhohost). We should keep the location of this configurable if possible; we don't currently hard-code any other paths except the Docker socket. So we might want commands to list and prune remote backups
Regular off-site automatic backups
- This is the case that's handled really well by backupbot currently

Features

Run custom pre- and post-backup commands (for DB backups)
Easy integration into stack definition (env vars, optional compose file if we really need to)
Easy per-app config (env vars)

### Use-cases - Make & download an ad-hoc .tar.gz backup of all an app's volumes, like Yunohost / Cloudron - Include stack config? I think it's available from `docker inspect` - To not be super-frustrating I think the backups should be generated on the server and then downloadable in a separate command (like Yunhohost). We should keep the location of this configurable if possible; we don't currently hard-code any other paths except the Docker socket. So we might want commands to list and prune remote backups - Regular off-site automatic backups - This is the case that's handled really well by `backupbot` currently ### Features - Run custom pre- and post-backup commands (for DB backups) - Easy integration into stack definition (env vars, optional compose file if we really need to) - Easy per-app config (env vars)

decentral1se added this to the Public mini-launch milestone 2020-10-27 08:04:48 +00:00

decentral1se added the

design

label 2020-10-27 08:09:14 +00:00

decentral1se added this to the (deleted) project 2020-12-27 11:48:53 +00:00

decentral1se commented

2021-01-01 21:42:08 +00:00