redis VS docker-db-backup

services: - type: web name: myapp-web env: ruby region: frankfurt # or oregon plan: starter numInstances: 1 buildCommand: ./bin/render-build.sh startCommand: REDIS_URL="redis://${REDIS_HOST}" bundle exec puma -C config/puma.rb domains: - example.com # replace with your domain name envVars: - key: DATABASE_URL fromDatabase: name: myapp-db property: connectionString - key: REDIS_HOST fromService: name: myapp-redis type: pserv property: hostport - key: RAILS_MASTER_KEY sync: false - type: worker name: myapp-sidekiq env: ruby region: frankfurt # or oregon plan: starter buildCommand: bundle install && bundle exec rake assets:precompile startCommand: REDIS_URL="redis://${REDIS_HOST}" bundle exec sidekiq -e production envVars: - key: DATABASE_URL fromDatabase: name: myapp-db property: connectionString - key: REDIS_HOST fromService: name: myapp-redis type: pserv property: hostport - key: RAILS_MASTER_KEY sync: false - type: pserv name: myapp-redis env: docker region: frankfurt # or oregon repo: https://github.com/render-examples/redis.git numInstances: 1 disk: name: myapp-redis-data mountPath: /var/lib/redis sizeGB: 1 databases: - name: myapp-db plan: starter region: frankfurt # or oregon

I have several dozen containers and I want to establish a good backup policy. Currently, all containers that store data do so by bind mounts to directories on a BTRFS volume. The files are backed up directly from the host. For MySQL/PostgreSQL containers I've been using the fantastic utility tiredofit/db-backup, which does a hot dump of all the data.

this one (https://github.com/tiredofit/docker-db-backup) can be a solution, but it export only to S3 or compatible storage. ( i use Minio)

Then went with https://github.com/prodrigestivill/docker-postgres-backup-local for remote productive Postgres backups, https://github.com/foorschtbar/pyd2b2 for local self-hosted docker database backups and might check out https://github.com/tiredofit/docker-db-backup because it looks promising.

Take a look at tiredofit/db-backup. I run three containers, one for MariaDB, one for Postgres, and one for InfluxDB (also supports other DB types). It uses the database's native backup mechanism to create a database backup that your backup SW of choice can then pick up each day. Then set your backup SW to ignore the database files each night to eliminate the errors in your backups due to locks, open files, files changed during backup, etc.

Cron works just fine but if you’re lazy like me and don’t want to create your scripts yourself, there are prebuilt docker images like https://github.com/tiredofit/docker-db-backup that dumps, compress, encrypts and uploads your backups.

I like do deploy one of these with every database. https://github.com/tiredofit/docker-db-backup Super easy to set up and works with all sorts of databases.

I run a tiredofit/db-backup for each of my databases to backup the database on a nightly basis. I have a shared volume that I share between this container and my database container. I mount it in /backups in both containers for consistency. I retain 8 copies of the backups, just in case I don't catch something in time, and need to go back and restore to a previous date. This volume is kept on a separate drive from the actual database data (which I keep in /mnt/user/appdata (SSD backed cache pool).

I built an image a while back that allows you to take scheduled backups of your databases that you could allow your backup software of choice archive and do its thing.

I have MariaDB in a docker container, recently found out about db-backup and set it up to backup MariaDB and now also Postgresql and Redis, though it requires a separate instance for each backup.