bup vs Backup wrapper nono Backup-rsync-time-backup

A side-by-side comparison of two self-hosted backup & recovery options — licensing, setup difficulty, resource needs, and what each one replaces.

Not the right match-up?
FeaturebupBackup wrapper nono Backup-rsync-time-backup
CategoryBackup & RecoveryBackup & Recovery
LicenseLGPL-2.1MIT
LanguagePythonShell
Setup difficultyMediumEasy
Min. RAM128 MB32 MB
Deploymentbinarybinary
GitHub stars★ 7,337★ 3,608
First released20102014
ReplacesTime MachineTime Machine

Why pick each one

Choose bup if…

  • Released under the LGPL-2.1 license
  • Mature project with 7.3k GitHub stars
  • Written in Python
  • Tiny footprint — runs in 128 MB RAM
bup details

Choose Backup wrapper nono Backup-rsync-time-backup if…

  • Released under the MIT license
  • Easy to set up — beginner-friendly
  • Active community (3.6k GitHub stars)
  • Written in Shell
Backup wrapper nono Backup-rsync-time-backup details

Frequently asked questions

Is bup or Backup wrapper nono Backup-rsync-time-backup better?

Neither is universally better. bup has the larger community, while Backup wrapper nono Backup-rsync-time-backup is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.

Are bup and Backup wrapper nono Backup-rsync-time-backup free and open-source?

Yes. bup is licensed under LGPL-2.1 and Backup wrapper nono Backup-rsync-time-backup under MIT. Both can be self-hosted at no software cost.

Can I run bup and Backup wrapper nono Backup-rsync-time-backup with Docker?

bup: check the project docs for container support. Backup wrapper nono Backup-rsync-time-backup: check the project docs for container support.

Related comparisons