←back to thread

Restic: Backups done right

(restic.net)
231 points fanf2 | 1 comments | 13 Oct 24 17:42 UTC | HN request time: 0s | source
Show context
kayson ◴[13 Oct 24 18:57 UTC] No.41830564[source]▶
Other popular choices include borg, duplicity, and duplicati.

After evaluating these and others mentioned in the comments, I ended up using borg with borgmatic to define homelab backups with yaml files that are version controlled in gitea and deployed using ansible.

I also use duplicity to back up my sister in laws storefront website to backblaze. I've been quite happy with both.

https://borgbackup.readthedocs.io/en/stable/

http://duplicity.gitlab.io/

https://docs.duplicati.com/en/latest/

replies(8): >>41830658 #>>41830915 #>>41831061 #>>41831170 #>>41831332 #>>41831517 #>>41832118 #>>41834010 #
sph ◴[13 Oct 24 20:32 UTC] No.41831332[source]▶
I chose restic because borg was slow, buggy and an unwieldy pile of Python, not the best language for deployment on heterogeneous Linux systems.

Restic on the other hand is slow, but never crashed on me and is distributed as a single binary.

The only thing I dislike about restic is that it does not have a simple config file where you define your backup settings. Instead I had to write my own backup.sh that I deploy everywhere on my personal and production machines. Paired with rsync.net for storage and healthchecks.io for notifications.

replies(5): >>41831821 #>>41831842 #>>41832187 #>>41832825 #>>41836933 #
1. 3eb7988a1663 ◴[13 Oct 24 22:18 UTC] No.41832187[source]▶
I write Python day to day, but even I use Restic for the single binary. I take a lot of comfort in being able to keep the backup executable adjacent to the backup blobs. While I believe Borg now has a distributable binary, Go has it in its blood to make easy deployment without tricks.