rsync-time-backup VS borgmatic

Hi Hacker News,

I'm excited to share my recent project, where I took on the challenge of porting a popular but untested 600+ line Bash script to Python. The outcome is [`rsync-time-machine.py`](https://github.com/basnijholt/rsync-time-machine.py), a Python implementation of the [`rsync-time-backup`](https://github.com/laurent22/rsync-time-backup) script. It provides Time Machine-style backups using rsync and creates incremental backups of files and directories to the destination of your choice.

The tool is designed to work on Linux, macOS, and Windows (via WSL or Cygwin). Its advantage over Time Machine is its flexibility - it can backup from/to any filesystem and works on any platform. You can also backup to a Truecrypt drive without any issues.

Unlike the original Bash script, `rsync-time-machine.py` is fully tested. It has no external dependencies (only requires Python ≥3.7), and it is fully compatible with [`rsync-time-backup`](https://github.com/laurent22/rsync-time-backup). It offers pretty terminal output and is fully typed.

Key features include:

* Each backup is in its own folder named after the current timestamp.

I'm excited to share my recent project, where I took on the challenge of porting a popular but untested 600+ line Bash script to Python. The outcome is rsync-time-machine.py, a Python implementation of the rsync-time-backup script. It provides Time Machine-style backups using rsync and creates incremental backups of files and directories to the destination of your choice.

Here's a script that someone made that simplifies the setup. I haven't used this script, but it looks pretty good: https://github.com/laurent22/rsync-time-backup

https://github.com/laurent22/rsync-time-backup or https://torsion.org/borgmatic/ could come in handy.

If you are interested, you can check it out here: https://github.com/laurent22/rsync-time-backup

I do most of my backups using some version of this script to (efficiently) keep a long backup history: https://github.com/laurent22/rsync-time-backup

Here is a scripted version. Honestly, I’d rather roll my own but it’s still helpful: https://github.com/laurent22/rsync-time-backup

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