I started out with borg. Basically had no problems with it. Then i moved to Restic. For the past few years i am using it, i never experienced any issue with it. Can only recommend Restic.

Borg (specifically Borg Matic) has been working very well for me. I run it on my main server and then on my Nas I have a Borg server docker container as the repository location.

I also have another repository location my on friends Nas. Super easy to setup multiple targets for the same data.

I will probably also setup a Borg base account for yet another backup.

What I liked a lot here was how easy it is to make automatic backups, retention policy and multiple backup locations .

Open source was a requirement so you can never get locked out of your data. Self hosted. Finally the ability to mount the backup as a volume / drive. So if I want a specific file, I mount that snapshot and just copy that one file over.

Highly recommend restic. Simple and flexible. Plus I've actually used it on two occasions to recover from dead boot drives.

Im using borgmatic, a wrapper around Borg that has some extra functionality.

Very happy with it, does exactly as advertised.

I've been using Kopia for all my backups for a couple years, both backing up my desktop and containers. It's been very reliable, and it has nice features like being able to mount a backup.

I setup a script to backup my lvm volumes with kopia. About to purchase some cloud storage to send it off site. Been running for a while de duplication working great. Encryption working as far as I can tell. The sync to other repo option was the main seller for me.

I use restic with a local external drive that is then synced to backblaze b2 via rclone.

I’m using Autorestic, a wrapper for Restic that lets you specify everything in a config file. It can fire hooks before/after backups so I’ve added it to my healthchecks instance to know if backups were completed successfully.

One caveat with Restic: it relies on hostnames to work optimally (for incremental backups) so if you’re using Autorestic in a container, set the host: option in the config file. My backups took a few hours each night until I fixed this - now they’re less than 30 minutes.

Was using borg, was a bit complicated and limited, now i use kopia.
Its supposed to support multiple machines into a single repository, so you can deduplicated e.g. synced data too, but i havent tested that yet.

I use a k8s Cron job to execute backups with Kopia. The manifest is here

For me it's restic with creatic wrapper, apprise for notifications and some bash / systemd scripts to make it all connected.

Everything is in a config file, just as god intended.

I use restic with resticprofiles (one config file), notifications via (self hosted) ntfy.sh and wasabi as backend. Been very happy, runs reliably and has all the features of a modern backup solution, especially like the option to mount backups as if it were a filesystem with snapshots as folders, makes finding that one file easy without having to recover)

restic without any doubt. I use it with S3 backend and SSH copy and it has an excellent performance (with copies of years).

Borg I was using it for a while (to compare) and I do not recommend it, it is not a bad product, but it has a lousy performance compared to restic.

Kopia I didn't know it, but from what I have read about it it seems to be very similar to restic but with some additions to make it pretty (like having ui).

Some people say that Kopia is faster in sending data to the repository (and other people say it's restic), I think that, unless you need ui, I would use restic.

I really like Kopia. I backup my containers with it, my workstations, and replicate to s3 nightly. It's great.