borgmatic VS ansible-role-borgbackup

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

Heavy Ansible user here, so I use this Ansible role to set up Borgmatic and then send the encrypted Backup to BorgBase.com. Works reliable for a few dozen bare metal- and virtual servers and doesn't cause much load during the backup run.

If you use Ansible, try our Ansible role. It supports EPEL8 and 9. If you don't use Ansible, you can still copy the build dependencies from the `var` folder.

Our Ansible role to quickly set up backups on new servers already supports RHEL9 and Arch Linux.

The Log4J debacle just before Christmas got me thinking about our own Borg ecosystem. At BorgBase.com we already maintain a few projects, like Vorta and an Ansible role to set up Borg & Borgmatic on new servers.

We even maintain an Ansible role to set it up in a repeatable way: https://github.com/borgbase/ansible-role-borgbackup

Ansible role to setup Borg+Borgmatic on most server systems