Comment by TheFreim

I spent too long looking into this and settled on restic. I'm satisfied with the performance for our large repo and datasets, though we'll probably supplement it with filesystem-based backups at some point.

Borg has the issue that it is in limbo, i.e. all the new features (including object storage support) are in Borg2, but there's no clear date when that will be stable. I also did not like that it was written in Python, because backups are not always IO blocked (we have some very large directories, etc.).

I really liked borgmatic on Borg, but we found resticprofile which is pretty much the same thing (it is underdiscussed). After some testing I think it is important to set GOGC and read-concurrency parameters, as a tip. All the GUIs are very ugly, but we're fine a CLI.

If rustic matures enough and is worth a switch we might consider it.

restic

Single binary, well supported, dedup, compression, excellent snapshots, can mount a backup to restore a single file easily etc etc.

It's made my backups go from being a chore to being a joy.

Restic is nice. Backrest if you like a webUI.

I still use borg for local backups but use restic for all my offsite backups. Off-hand I don’t think redtic lacks any feature borg has (although there’s probably at least one) after they added compression a few years ago.

Kopia