8 ms·

Duplicity is your best bet for incremental backups using B2. I use this for my personal server and it works brilliantly.

gingerlime 6y ago
I thought so too for a long while. Until I was trying to restore something (just to test things), and wasn’t able to... it might have been specific to our GPG or an older version or something... but I decided to switch to restic and am much happier now. Restic has a single binary that takes care of everything. It feels more modern and seems to work really well. Never had any issue restoring from it. Just one data point. Stick to whatever works for you. But important to test not only your backups, but also restores!
- sebmellen 6y ago
  Interesting, I will check Restic out, I’ve heard other good things about it. Duplicity is a bit of a pain to set up and Restic’s single binary model is more straightforward (Go is a miracle). Thanks for the recommendation! GPG is a bit quirky but I do regularly check my backups and restores (if once every few months counts as regular).
- nix23 6y ago
  +1 for Restic It's brilliant, works like a charm on freebsd windows and a rpi with linux since over 2 years.
- remram 6y ago
  I've been using Duplicati forever. The fact that it's C# is a bit of a pain (some distros don't have recent Mono), but running it in Docker is easy enough. Being able to check the status of backups and restore files from a web UI is a huge plus, so is the ability to run the same app on all platforms. I've found duplicity to be a little simplistic and brittle. Purging old backups is also difficult, you basically have to make a full backup (i.e. non-incremental) before you can do that, which increases bandwidth and storage cost. Restic looks great feature-wise, but still feels like the low-level component you'd use to build a backup system, not a backup system in itself. It's also pre-1.0.
geocrasher 6y ago
I'm using rclone, it works very well for the purpose too.
- nucleardog 6y ago
  Ditto. Moved to rclone after having a bunch of random small issues with Duplicity that on their own weren't major but made me lose faith in something that's going to be largely operating unsupervised except for a monthly check-in.
uncledave 6y ago
I’d stay away from duplicity. I’ve had serious problems with it and large inode counts where it’ll bang the CPU at 100% and never complete. Have moved to using rdiff-backup over SSH.

gingerlime 6y ago

I thought so too for a long while. Until I was trying to restore something (just to test things), and wasn’t able to... it might have been specific to our GPG or an older version or something... but I decided to switch to restic and am much happier now. Restic has a single binary that takes care of everything. It feels more modern and seems to work really well. Never had any issue restoring from it. Just one data point. Stick to whatever works for you. But important to test not only your backups, but also restores!

sebmellen 6y ago
Interesting, I will check Restic out, I’ve heard other good things about it. Duplicity is a bit of a pain to set up and Restic’s single binary model is more straightforward (Go is a miracle). Thanks for the recommendation! GPG is a bit quirky but I do regularly check my backups and restores (if once every few months counts as regular).
nix23 6y ago
+1 for Restic It's brilliant, works like a charm on freebsd windows and a rpi with linux since over 2 years.
remram 6y ago
I've been using Duplicati forever. The fact that it's C# is a bit of a pain (some distros don't have recent Mono), but running it in Docker is easy enough. Being able to check the status of backups and restore files from a web UI is a huge plus, so is the ability to run the same app on all platforms. I've found duplicity to be a little simplistic and brittle. Purging old backups is also difficult, you basically have to make a full backup (i.e. non-incremental) before you can do that, which increases bandwidth and storage cost. Restic looks great feature-wise, but still feels like the low-level component you'd use to build a backup system, not a backup system in itself. It's also pre-1.0.

geocrasher 6y ago

I'm using rclone, it works very well for the purpose too.

nucleardog 6y ago
Ditto. Moved to rclone after having a bunch of random small issues with Duplicity that on their own weren't major but made me lose faith in something that's going to be largely operating unsupervised except for a monthly check-in.

uncledave 6y ago

I’d stay away from duplicity. I’ve had serious problems with it and large inode counts where it’ll bang the CPU at 100% and never complete. Have moved to using rdiff-backup over SSH.