diff --git a/content/posts/backup-strategy-2021.md b/content/posts/backup-strategy-2021.md index 302da44..de2aa8c 100644 --- a/content/posts/backup-strategy-2021.md +++ b/content/posts/backup-strategy-2021.md @@ -60,7 +60,7 @@ So, my data now lives outside my server, should something happen to it (or I run Recently, I moved my off-site backup mechanism from [Duplicati](https://www.duplicati.com/) to [restic](https://restic.net/). I had been using Duplicati for a couple of years, and it's served me well, _ish_. Duplicati can be quite temperamental, complaining about backup files, corrupting itself, and various other things. Not to mention the fact it's not especially fast, and doesn't have great compression support (just ZIP in 2021?!). Restic on the other hand is the _hot new thing_. It's much simpler, much more lightweight, and yet has some powerful features. Restic doesn't support compression ([yet](https://github.com/restic/restic/issues/21)), but it's fancy [content-defined chunking](https://restic.net/blog/2015-09-12/restic-foundation1-cdc/) is almost as effective (compared to zip, at least). -

The Changelog 434: Restic has your backup – Listen on Changelog.com

+

The Changelog 434: Restic has your backup – Listen on Changelog.com

Rather than using an existing orchestration tool like [autorestic](https://github.com/cupcakearmy/autorestic/) or [resticprofile](https://github.com/creativeprojects/resticprofile), I wrote [my own](https://github.com/RealOrangeOne/infrastructure/blob/master/ansible/roles/restic/files/backrest.sh) (yes, that's really what I named it). The others never did quite what I want, and I wanted something which "just worked", and had a tight integration with [healthchecks.io](https://healthchecks.io/). Using my [Ansible repo](https://github.com/RealOrangeOne/infrastructure/tree/master/ansible/roles/restic), it gets installed on all my servers, and scheduled with cron.