… and what I’ve learned about backups and self-hosting my files.
I’m switching from Backblaze B2 to Scaleway’s Object Storage.
I used to use B2 as a backup destination for my restic backups from various servers. The service is fine, but what drives me away is missing €-billing (and credit cards as the only payment method) and a somewhat slow performance (at least it feels like that). Scaleway asks for twice the price (0,01€ per GB per month) but the first 75GB are free.
restic is my tool of choice to do backups. I’m just eagerly waiting for this a(a)wsome PR to get merged and a new version released! I’m backing up my Nextcloud (currently ~50 GB), but I never pruned the backup and now the backup is taking up more than 160 GB. That’s still just peanuts with Backblaze B2 as online storage, but I like to have things clean and tidy and a prune is overdue.
I got the question how to solve the problem that when backing up the storage of a dockerized Postgres database (using Resticker) it could be that the backup is corrupt because the database is still running.
This is an addition to my post of how to backup Docker volumes using resticker.
I had exactly the same problem. I wanted to backup a Postgres database running in a Docker container without having to stop the database or have a corrupt backup.
One of the most visited pages on my blog is about how to automatically backup Docker volumes. In that post I use the Docker image blacklabelops/volumerize. Unfortunately that image is deprecated since March 2019 and not longer maintained.
Under the hood the volumerize image is using the GNU program duplicity, which is an awesome software, but also has its downsides. Especially the model of full backups and incremental backups comes from a time where backups where mainly made to tapes (just append new files all the time).