Back In Time VS ZBackup

it is often asked by beginners how and where starting to contribute. As member of the maintenance team of Back In Time (Backup software using rsync in the back, written with Python and Qt) I would like to introduce one of our "good first issues" (#1578).

I'm member of the upstream maintenance team of Back In Time a rsync-based backup software. No one gets payed. No company behind hit. Even the maintainers and developers are volunteers.

Back In Time is a round about 15 years old backup software using rsync in the back. I'm part of the 3rd generation maintenance team there. A lot of work in investigating and fixing issues, understanding, documenting and refactoring old code.

This request is related to an Open Source project named Back In Time. Everyone there works voluntarily and unpaid.

In my own project we do it more transparent. We close if there is a good reason for it. We don't close just because no one is working on something. If there are no resources to work in it now but it seems important we keep it open until it is fixed. We do use milestones and priority labels to give the users an idea about our plans.

I'm member of the maintenance team of Back In Time a rsync-based backup software.

Most of the strings are form two past developers (the founder and the past maintainer). Since last summer we took over the project and try to clean things up. Some of the source strings just got a review from a linguist and he also mentioned about that exclamation marks. But he kind of stopped at some point because it was to much. ;)

Currently the translation is locked because of maintenance issues and an open PR offering review of original English strings.

Great and thanks. Feel free to ask further questions in the Issues section of our project or the bit-dev.python.org mailing list. Of course you can contact me directly here.

I'm interested in that topic because I'm member of the maintenance team of Back In Time, the software discussed in that video. The version in video is 0.9, today Back In Time reached 1.3.3. Also interesting is that I'm the third generation of maintainers to that project. I'm not sure but 0.9 there was the fist maintainer and founder involved only.

I've been doing semi-regular backups with mintbackup, but it's gotten to the point where my backups are filling up the drive even when I gzip them individually. Because these backups contain a bunch of the same files over and over again, I looked for a way to de-duplicate the backups and I landed on zbackup. It looks like it does what I want and my tests are promising, but I wanted to know if there were any caveats or if there are any better solutions out there.

[I] app-backup/zbackup [1] Available versions: (~)1.4.4-r2 **9999 {tartool} Installed versions: 1.4.4-r2(09:57:06 02/07/21)(tartool) Homepage: https://github.com/zbackup/zbackup Description: A versatile deduplicating backup tool

I use zbackup which is quite similar in concept to Borg (doesn't offer mountable images tho) with cron jobs such as the bash script below which backs up all the root folders except for selected things like /dev

I use zbackup ("globally-deduplicating backup tool, based on the ideas found in rsync") from a cron job which saves more space than just using links (ie it can recognise moved files, renamed files, and files that are only partially edited).