django-dbbackup VS borgmatic

And finally backups, this part is really important. When I was a beginner, I used to make silly mistakes which would lead me having to reset the entire database and rebuild. With backups you can simply restore back to a working point in time whenever something goes wrong. The django-dbbackup package can do this for you, however, you may run into a few issues which can be fixed. Or you could simply use PostgreSQL database dumps.

I spent the entire day today trying to implement a backup system for my personal Django/Wagtail project using django-dbbackup, however, I ended up making zero progress.

I have a Django/Wagtail project and I'm trying to set up django-dbbackup to backup both my database as well as my media files.

I've just stumbled upon the django-dbbackup package, seems perfect as it backs up the database and media to the cloud. As backups are linked to the deployment using hostnames, it even seamlessly handles restores. I might give that a go using Ofelia to run the backup management command at regular intervals.

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