Duplicity VS rdedup

http://duplicity.nongnu.org/ at least can use PGP public keys. I've used it for a long time and not seen any particular reason to change.

There are backup tools with built-in encryption like borg backup or duplicity, these should be fine. If you already have a backup process and it's missing encryption then you should be able to use e.g. age or gpg.

For my family photos (critical, irreplaceable, on plex), I use duplicity which can make use of Amazon Glacier and Deep Archive for really cheap storage (0.00099 /gb /month no joke) with incremental versioning and client side encryption. Long restore time, but perfect for disaster recovery on data that doesn't change much. Want to set up the same for music (which rarely but sometimes changes, e.g. Correcting tags).

And google docs / apple cloud etc. aren't proper backups. They can cancel your account, be inaccessible, or hacked even. There's software like duplicity that can upload encrypted backups to multiple services, which are handy. But in any case, if you're doing cloud backups, do do redundant local backups too. My setup is I've a USB stick tacked onto a Raspberry Pi computer, and use something called borg to do daily backups over SSH.

I have had good success using [Duplicity](http://duplicity.nongnu.org/) via [Duply](https://www.duply.net/) for a few years now. The main point for me is that duplicity directly backs up to many cloud-storage endpoints. I'm using google drive specifically, but it supports a ton of options.

I'm not really doing much about it anymore, but I have somewhat similar project: https://github.com/dpc/rdedup

I'm the author of https://github.com/dpc/rdedup . Threads is your answer. Make a large threadpool, process IO in it, use channels to submit work and responses if need.

rdedup (rust) - https://github.com/dpc/rdedup