Check out duplicacy https://twitter.com/ArtemR/status/1159392251992145920

https://github.com/gilbertchen/duplicacy

I moved away from Duplicacy to restic when restic finally implemented compression.

Duplicacy is slower and also only free for personal use.

really tough for me to decide to use restic or kopia. instead i use a way worse solution because i'm afraid i'll mess something up

I use restic for everything Linux or windows except for Mac’s. There I use kopia. It just works. There is not much to mess up really. Just keep your password safe and be sure to test your backups.

I back up TBs with restic, never had issues. When I need a file, I mount the remote repository. The mount is fast with S3.

The rclone backend means I can backup anywhere.

Like with all contingency systems it's necessary to do a "fire drill" exercise from time to time. Pretend that you lost your data and attempt to recover a few files from backups. Pretend that your house burned down and you can't use any item from home. This will give you confidence that your system is working.

The main disadvantage with pure Restic is that you usually have to end up writing your own shell scripts for some configuration management because Restic itself has none of that.

Fortunately there is https://github.com/creativeprojects/resticprofile to solve that problem.

Resticprofile is fantastic, makes it much easier to set up

The restic team refuses to have unencrypted backups just "because security".

I hate such an approach when someone assumes that whatever happens their opinion is the best one in the world and everyone else is wrong.

I do not want to encrypt my backups because I know what I am doing and I have very, very good reasons for that.

Restic could allow a --do-not-encrypt switch and backup by default.

The arrogance of the devs is astonishing and this si why I will not use Restic and i regret it very much because this is a very good backup solution.

Try Borg.

Mind sharing the reasons?

Backup locally or on a NAS, don't worry about losing the keys and all of your backups.

I'm using duplicity because none of these can sync to a rsync server that I run on my NAS.

You listed the main reasons, thanks.

As for remote backups - I use ssh with Borg and it works fine. If this is a NAS you can probably enable ssh (if it is not enabled already).

BTW for my remote backups I do encrypt them but this is a choice the author of Borg left open.

There are other issues with Borg such the use of local timestamps (naive date format, no timezone) instead of a full ISO8601 string, and the lack of capacity to ask whether a backup is completed (which is a nightmare for monitoring) because the registry is locked during a backup and you cannot query it.

I use both.

Restic for various machines to hourly backup on a local server. Rclone to sync those backups to S3 daily.

Keeps the read/write ops lower, restores faster, and limits to a single machine with S3 access.

Also, consider making backups append-only as an extra precaution: https://ruderich.org/simon/notes/append-only-backups-with-re...