+1 for Restic. What I ended up doing was writing a script which implements a file I called `backupctl` on my home server which specifies a set of directories under the home directories to backup. This wound up being a good solution to the problem of "try and save these files from loss due to annoyance" - i.e. a house fire isn't catastrophic, and "irreplaceable" (previous memories) which I want to head off to Restic.
For things like family photos this works really well since if we copy them all over the place across devices, restic will still deduplicate them down to just 1 record when it gets uploaded to Backblaze.
I've had a good experience with [crestic](https://github.com/nils-werner/crestic), even though it seems a lot smaller and simpler than autorestic.
But I really like how the same backup can be configured for different backends. Autorestic's seemed more complicated in comparison.
There’s also resticprofile which takes care of scheduling (with launchd on macOS) and maintenance tasks for restic. I especially enjoy that resticprofile can create a prom file for the backup status that I can just scoop up to my monitoring.
I've been using Autorestic but it has some issue, it keeps modifying the yml file on its own with an invalid config option, which causes the backups to fail.
Not a good thing for something that's supposed to run in the background and keep things backed up.
XorNot|3 years ago
For things like family photos this works really well since if we copy them all over the place across devices, restic will still deduplicate them down to just 1 record when it gets uploaded to Backblaze.
alexktz|3 years ago
https://autorestic.vercel.app/
fdw|3 years ago
hjuutilainen|3 years ago
https://creativeprojects.github.io/resticprofile/
Saris|3 years ago
Not a good thing for something that's supposed to run in the background and keep things backed up.
jacooper|3 years ago
wolfhumble|3 years ago
b0afc375b5|3 years ago
jacooper|3 years ago