gitkurwa VS borgmatic

> as far as OSS names of Polish go, kopia is pretty tame

Well indeed.

There's a project on GitHub with 1.7k stars called GitKurwa[1].

Now that's proper untame Polish. ;-)

[1] https://github.com/jakubnabrdalik/gitkurwa

Polecam klasykę na poprawę humoru : https://github.com/jakubnabrdalik/gitkurwa/blob/master/configNSFW_PL

Zawsze jest gitKurwa

- 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.