Duplicacy VS borgmatic

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

- for important files, a separate box where I have borgmatic [1] in deduplication mode installed; this is updated once in a while

Just curious: Do you have any reason to believe that such a data corruption bug is likely in ZFS? It seems like saying that ext4 could have a bug and you should also store stuff on NTFS, just in case (which I think does not make sense..).

[1]: https://github.com/borgmatic-collective/borgmatic

Not really dumb. I do use them too but with Borgbackup on the top (since they support it natively).

I found Borgmatic ( https://torsion.org/borgmatic/ ) to be the best way to run my backups. It takes care of everything from pruning to verifying the checksum etc... and it integrates with some monitoring (like cronitor).

So Borgmatic + rsync.net is the best combo

For backups I use Borg myself. If you need a GUI, you can use Vorta or Pika. With borgmatic, there is also a wrapper that extends the range of functions of Borg.

Furthermore, Borgmatic is a wrapper for Borg that extends or improves the range of functions.

For those of you not familiar, borgmatic is a very convenient tool which runs as a wrapper around borg.

I recommend Borg and Borgmatic. Automated, easy to setup, capable of notifying you if anything happens, deduplication and compression makes backups smaller, etc.

To add to this, Borg backup can be a little daunting to configure. There is a wrapper script called Borgmatic that distills it down to a single yaml config file. There are also some cloud hosts like BorgBase and rsync.net with native Borg support.