tarsnap VS rdedup

Tarsnap for configs and critical stuff (password database, emails).

Someone does :)

https://tarsnap.com

> Tarsnap uses a prepaid model based on actual usage:

> Storage: 250 picodollars / byte-month of encoded data

Colin Percival's tarsnap

In past threads, people have mentioned enjoying my Tarsnap (https://github.com/Tarsnap/tarsnap) code. I personally think that the spiped (https://github.com/Tarsnap/spiped) code is even better.

I prefer Vorta myself ( https://github.com/borgbase/vorta ) as it also has incremental and encrypted backups, as well as being a fraction of the price, but tarsnap seems to still be in very-slow development: https://github.com/Tarsnap/tarsnap , so I'd say from a quick look it's still trustworthy.

Each server also upload their configs and « important » data (my mails and git repos) to tarsnap 3. Tarsnap storage is not as cheap as B2, so I try not to upload too much data there, but it's reliable and easy to use. It was also my first backup solution, and barely cost me 10$ a year so I keep it as a secondary backup.

Not foolish! The Tarsnap client code is open source, but the license file prohibits anyone from using the code: https://github.com/Tarsnap/tarsnap/blob/master/COPYING

> Redistribution and use in source and binary forms, without modification,

Yes. For the curious,

https://github.com/Tarsnap/tarsnap/graphs/contributors

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