Back In Time: a Qt frontend for rsync-based incremental backups with hard links
GitHub RepoImpressions711
View on GitHub
@githubprojectsPost Author

Back In Time: A Qt-Powered rsync Backup Tool with Hard Links

If you’ve ever tried to set up incremental backups using rsync, you know it works—but the command-line flags and manual script maintenance get old fast. You want something reliable that doesn’t reinvent the wheel, just wraps it in a clean interface. That’s where Back In Time comes in.

It’s a Qt frontend for rsync that turns your existing rsync knowledge into a usable, snapshot-based backup system—without locking you into a proprietary format or cloud service. Hard links keep disk usage sane, and the GUI means you don’t have to remember all those --link-dest flags.

What It Does

Back In Time creates incremental backups of your files using rsync. Each backup is a full-looking directory tree, but unchanged files are just hard links to previous snapshots. So you get the convenience of having every backup look complete, but you only store the actual changes.

It’s basically a friendlier interface for a pattern many devs already hack together with cron and rsync scripts. You choose source directories, a destination (local or remote via SSH), and a schedule. The tool handles the rest—taking snapshots, pruning old ones, and letting you browse or restore files from any point in time.

Why It’s Cool

A few things that stand out:

  • Hard link magic. Because it uses rsync’s --link-dest under the hood, each backup is space efficient. You can have daily snapshots for months, and unless files change daily, it barely uses more space than the original data.
  • Qt GUI. It runs on Linux (and BSDs) and gives you a clear tree view of snapshots. You don’t have to guess which directory contains a file from last Tuesday—just browse the snapshot.
  • SSH remote destinations. You can back up to another machine over SSH without needing any special daemon. The remote side just needs rsync and SSH access.
  • No lock-in. Your backups are plain files and directories. If you decide to switch tools, you can copy the snapshot folders manually—no special restore tool required.
  • Retention profiles. You can keep hourly snapshots for a week, daily for a month, weekly for a year—all configurable. Old snapshots get automatically cleaned up.

How to Try It

Installation is straightforward on most Linux distros:

# Debian / Ubuntu
sudo apt install backintime-qt

# Fedora
sudo dnf install backintime

# Arch / Manjaro
yay -S backintime

For other systems, check the official install docs.

Once installed, launch backintime-qt from your application menu. The wizard walks you through choosing your source folders, snapshot location (local path or SSH), and schedule. After that, you can take a manual snapshot or let cron handle it (the tool sets up the cron job for you).

Final Thoughts

Back In Time is one of those tools that does exactly what you expect, without surprise vendor lock-in or obscure config formats. If you’re a developer who already uses rsync for personal backups but wishes it had a proper UI and automatic pruning, this is worth the five minutes to install.

It’s not flashy—it’s just solid. And sometimes that’s exactly what you want from a backup tool.


Follow us at @githubprojects

Back to Projects
Last updated: June 6, 2026 at 10:22 AM