←back to thread

Restic: Backups done right

(restic.net)
231 points fanf2 | 1 comments | 13 Oct 24 17:42 UTC | HN request time: 0.205s | 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 #
layer8 ◴[13 Oct 24 22:07 UTC] No.41832118[source]▶
Duplicity is solid, I’ve been using it since over a decade, and it’s a standard package on Debian-based distributions. Never had any hiccups (and I run regular backup validations).

These threads about backup tools come up regularly, and I always wonder if I’m missing something important about the other tools.

replies(1): >>41833344 #
1. Delk ◴[14 Oct 24 01:28 UTC] No.41833344[source]▶
I used Duplicity (via the Gnome Déjà Dup GUI) for years, but Borg turned out to be a lot faster at making the backups, at least for my laptop home dir backups. Like an order of magnitude faster. I don't think I ever tried to hand-configure Duplicity, though.