Duplicacy VS Duplicati

I have been having great luck with incremental backups with the very similar named Duplicacy https://duplicacy.com/

Pro: No need for a special index database. The chunks are placed in the file system. This explains it in greater detail. Seems to place great emphasis on reliability, which is important for me. Versioning is also supported.

Having all your data in one place isn't wise though, so I am planning on storing encrypted backups on Dropbox and Backblaze B2 using Duplicity so that I am following the 3-2-1 backup rule.

I tried a bunch of different ways but ultimately settled on Duplicacy [0].

It runs inside a Docker container and backs up both my data as well as configurations like my docker compose file and smb.conf.

Off site storage was Backblaze B2, but I moved to Hetzner. Likely will move back just because B2 is cheaper and a bit faster for my region.

Another layer of backup I do is use Duplicacy to backup to a portable hard drive occasionally that I keep off site.

[0] https://duplicacy.com/

Duplicacy

I use Kopia and works well. Have also used this https://duplicacy.com

Petabaytlarca veri emanet edilen şu kodun %85'i C# https://github.com/duplicati/duplicati

For my parents' computer, I'm using the canary version (which should be the alpha version I think?) of Duplicati since years.

It hasn't had a release in a little while but work is still occurring. https://github.com/duplicati/duplicati/actions.

Hey have a read at : https://github.com/duplicati/duplicati/issues/4041

I just came across this while looking through their issues to see if anyone else had reported the firefox issue i'm running into. I'm starting to have serious reservations.

I like duplicacy because of the way it keeps the chunks in the file system, without a special database. This makes it scale up really well no matter how many backups you have (you can even have multiple computers saved). It's kind of beyond weird how you select what you want to backup with the symlinks (using the command line version), looks more like what one would make for himself in a weekend (not that I'm complaining about free software!) but it's been without bugs for me and extremely efficient. In contrast duplicati has a perfect interface, it's well maintained and everything but bogs down in any large backup, has stories about people recovering for weeks for a very few local TBs and I've experienced for myself this, granted in the python that is checking the sha256 checksums of the backups but it makes it slower many times (possibly hundreds of times), nobody checked from 2013 to 2021 (or did it on tiny datasets like 1GB or was content to wait for weeks even on something small-ish)?