Project Summary
rdiff-backup backs up one directory to another, possible over a network. The target directory ends up a copy of the source directory, but extra reverse diffs are stored in a special subdirectory of that target directory, so you can still recover files lost some time ago. The idea is to combine the best features of a mirror and an incremental backup. rdiff-backup also preserves subdirectories, hard links, dev files, permissions, uid/gid ownership (if it is running as root), modification times, acls, eas, resource forks, etc. Finally, rdiff-backup can operate in a bandwidth efficient manner over a pipe, like rsync. Thus you can use rdiff-backup and ssh to securely back a hard drive up to a remote location, and only the differences will be transmitted.
In a Nutshell, rdiff-backup...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a small development team
with decreasing Y-O-Y commits -
...
took an estimated 14 years of effort (COCOMO model)
starting with its first commit in March, 2002
ending with its most recent commit 2 months ago
Quick Reference
GNU General Public License v2.0 or later
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
use of OSS increased in 65% of companies in 2016
-
...
anyone with an Open Hub account can update a project's tags
-
...
55% of companies leverage OSS for production infrastructure
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
30 Day SummaryDec 25 2025 — Jan 24 2026
|
12 Month SummaryJan 24 2025 — Jan 24 2026
|
