[JeremyNT]

I'm curious if there is any reason to use Borg these days.

I had the impression that in the beginning Borg started as a fork of Restic to add missing features, but Restic was the more mature project.

Is there still anything Borg has that Restic lacks?

[lutoma]

Borg is a fork of Attic, not restic. Restic is also written in Go while Attic/Borg is in Python.

For me the reason to use Borg over Restic has always been that it was _much_ faster due to using a server-side daemon that could filter/compress things. The downside being you can’t use something like S3 as storage (but services like Borgbase or Hetzner Storage Boxes support Borg).

That’s probably changed with the server backend, but with the same downside.

[KingOfCoders]

We used borg with the very nice people at rsync.net in two startups.

[remram]

My number one problem with Restic is the memory usage. On some of my workloads, Restic consumes dozens of gigabytes of memory during backup.

I am very much in the market for a replacement (looking at Rustic for example).

[nadir_ishiguro]

That's very interesting. Never had noticed anything like that. What kind of workloads are you seeing this with?