- Over 1500 lines of changelog since 0.10.2
- Now rdiff-backup writes metadata (uid, gid, mtime, etc.) to a
compressed text file in the rdiff-backup-data directory
- No longer seems compelled to send symlinks every time
Provided in PR 18577 by David.S at idiom dot com, some modifications
by me to use buildlink2 files, and to specify the correct version of
python required.
Rdiff-backup backs up one directory to another, possibly 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), and modification times. 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.
