You can’t dedup/compress restic repos at fs level due to the encryption.
Nice thing is you get those even with „dumb“ targets that can‘t do those for you.
You can’t dedup/compress restic repos at fs level due to the encryption.
Nice thing is you get those even with „dumb“ targets that can‘t do those for you.
Restic is my tool of choice for deduplicated encrypted verifiable compressed incremental backups.
Some woods are meant for the oven.
Deep Rock galactic. I played it very early, didn’t feel it and refunded it. A year or so later I stumbled upon it again and bought it again. I really like it now.
You can also feed database dumps directly into restic, like this:
mysqldump --defaults-file=/root/backup_scripts/.my.cnf --databases mydatabse | restic backup --stdin --stdin-filename mydatabase.sql
Daily backup using Restic to wasabi s3.
Restic already speaks s3 natively, no need to mount it or anything, just point it at a bucket and hand it an api key.
You can use an api key that’s only allowed to read and write, but not delete / modify, so you’ve got some protection from ransomware.
.tar.zst is my go-to nowadays. .txz if I need wide compatibllity.
I use wasabi s3, I back up to that using restic.
With restic you can pipe to stdin, so I use mysqldump and pipe it to restic:
mysqldump --defaults-file=/root/backup_scripts/.my.cnf --databases db-name | restic backup --stdin --stdin-filename db-name.sql
The .my.cnf looks like this:
[mysqldump] user=db-user password="databasepassword"