diff options
author | Paul Wisehart <wise@lupulin.net> | 2010-05-11 15:18:44 +0200 |
---|---|---|
committer | Robby Workman <rworkman@slackbuilds.org> | 2010-05-11 15:18:44 +0200 |
commit | 728f17945e7363d9d693f76753598f355c91167e (patch) | |
tree | 467518079f4c2a51280982f834f005215047bd0d /system/rdiff-backup/README | |
parent | 3a93d214a76c222e7287774b16a1a86dfa29f787 (diff) | |
download | slackbuilds-728f17945e7363d9d693f76753598f355c91167e.tar.gz |
system/rdiff-backup: Initial import
Diffstat (limited to 'system/rdiff-backup/README')
-rw-r--r-- | system/rdiff-backup/README | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/system/rdiff-backup/README b/system/rdiff-backup/README new file mode 100644 index 0000000000..0e78f2aadb --- /dev/null +++ b/system/rdiff-backup/README @@ -0,0 +1,16 @@ +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, modification times, +extended attributes, acls, and resource forks. Also, 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. Finally, rdiff-backup is easy to use and settings +have sensical defaults. + +Dependencies: librsync (from slackbuilds.org) + |