rdiff-backup 1.2.8
相关合集：
相关热搜：
VCF通讯录编辑器用于编辑手机通讯录备份文件，设计是以索尼爱立信智能手机为蓝本，缺省的通讯录文件名称为 Contacts.vcf，通过手机的备份功能备份后位于扩展卡的“Others\Backup”目录下。将通讯录复制到执行目录或者用这个程序打开指定的文件之后，就可以在计算机上编辑了。编辑后的文件复制到手机上再恢复就可以使用新的通讯录。...
高速下载地址
联通下载地址
电信下载地址
移动及其他下载地址
(您的评论需要经过审核才能显示)
在我用过的系统工具软件里，这个rdiff-backup算不上是最稳定，最快的，但绝对是最特别的。
越更新越好用了，之前有些功能我都找不到，现在的rdiff-backup太令我惊喜了
既然这个rdiff-backup是国外软件，那我就会一直支持下去的
咨询一下这个rdiff-backup安装起来，普通电脑安装会卡么
哈哈！费劲千辛万苦终于让我找到这个rdiff-backup了
这个rdiff-backup好用不？求用过的朋友介绍下
找了好多家网站，终于在这里找到rdiff-backup了
rdiff-backup就是好用！呵呵，我喜欢这个系统工具
rdiff-backup1.2.8怎么找不到下载地址啊,求大神指教~
还在研究rdiff-backup中，很多功能不会用~~
热门关键词Support this project:
Hosted by:
rdiff-backup-web is a web front-end to , a command-line incremental backup application written by Ben Escoto.
The main web interface of rdiff-backup-web is written in php with a mysql backend. The backups are
actually run using a command line python script that can be set up as a cron job. The application was
originally written to do a specific task at the company I work for, but it turns out that it might be handy
to other people.
This is currently ALPHA quality software.
New Release: Version 0.5 is a big changes and improvements with a new backend script:
Process_backup script now written in Python as opposed to Perl. Did this as I am a far better Python programmer than Perl. Also allowed me to remove the dependancy on the PHP:Include CPAN module. This also allows the posibility to directally call functions from rdiff-backup that is also written in Python.
Created Local back up option
Added NFS support
Added Samba Support
Fixed SQL script Bug and some PHP UI bugs.
I didi do some work on the doco included with the package but i am going to review again and may re-release this package with some better doco.
New Developer: Hi all my name is Dale Stirling and i am maintaining the rdiff-backup-web project at the moment. I have found this app very valuable in some of the things that I am doing where I work and am hoping to share these and add to the project as time permits. Feel free to drop me a line and letr me know of any suggestions or feedback.Cheers,Dale
New Site: Over the next few weeks this site will be changing as i bring it inline with the same look and feel that I will be introducing to rdiff-backup-web in version 0.6. I hope you like the changes :)
New Release: Version 0.4 has several improvements over previous incarnations:
Now you can use SSH connections, if you follow Dean Gaudet's instructions for unattended rdiff-backup
Also, an unexpected bonus of adding the SSH backup type (well, unexpected to me, anyway) has been to allow local backups. Just set the "Path to Orig Files" to be /path
Files and directories are listed using a tree-style view, rather than a big list of files.
You can deactivate a backup with a single click, but it remains in the system to be reactivated with a similar, singular, click.
You can now back up to a different location than the default, simply by using a leading / in the backup location field (useful for backing up to a mounted USB drive, etc).
There is now one required perl module,
by , which can be downloaded and installed using
(instructions in the readme).
Oh, and unlike the previous release, this might actually work :-)
Update: Wait, scratch that last statement. It would work right if character 37 of line 88 of
backup.sql was a comma instead of a semi-colon. So the line that
reads&&&&administrator tinyint(4) default 0;in the CREATE TABLE users section should actually read&&&&administrator tinyint(4) default 0,cos otherwise it won't work. Damned if I know how that got in there! Thanks to Jacob Emcken for spotting it, and I'll make sure that it's fixed next update.
Files are released through the project's
The current version is 0.05, available . Download it, untar it using tar -zxvf rdiff-backup-web_0.05.tar.gz, then read the included README file for installation and use instructions.Please bear in mind that this is ALPHA QUALITY software, and should be approached with caution. Have a play, tell me what you think.
Screenshots
Thanks to:
created by
Buy nappies from David's wife:Access denied |
used Cloudflare to restrict access
Please enable cookies.
What happened?
The owner of this website () has banned your access based on your browser's signature (392d1f-ua98).rdiff-backup: Features
For many people hard disks provide the form of persistent storage
that is most readily available and cheapest per MB. I think that
rdiff-backup is often the best way to back one hard drive to
Easy to use: In most cases, the command
rdiff-backup dir1 dir2
will work out-of-the-box to backup dir1 to dir2.
rdiff-backup dir1 user@system::/dir2
will backup dir1 to dir2 on a different system (provided rdiff-backup is installed on both systems). rdiff-backup
also comes with a lot of .
Creates mirror: rdiff-backup makes the backup
directory into an almost exact copy of the source directory (the only
difference is one extra subdirectory on the backup side). If you
delete a file from the source directory you can simply copy it from
the backup directory, use "find" or "locate" to find the file, or use
any other familiar utility. Also, if the two directories are on
different disks, you can recover almost immediately if the disk
containing the source directory crashes, just by mounting the backup
directory where the source directory used to be.
Keeps increments: Normally, with a mirror, any
changes made to the source directory are immediately sent to the
backup directory, and old changes are lost. rdiff-backup saves those
changes in the form of reverse diffs, so you can recover the older
form of the file.
For instance, suppose last week you deleted half of some document,
thinking that what you had written was garbage. Yesterday, your
backup event ran, saving these changes. Today you realize that you
were on to something and want what you deleted back. If you just
mirrored, you would be out of luck, since the copy on your mirror
would be the newer one. With rdiff-backup, the newer version would
indeed be present, but in a special directory (rdiff-backup-data/)
there would be a file that recorded this change. Running rdiff-backup
on this file recovers the version from a week ago.
Preserves all information: Whether you restore
from the mirror directory or from an earlier incremental backup,
rdiff-backup will reproduce your files exactly as they were. Files
missing at the time of backup will also be missing after the restore.
Files hard linked when backed up will be hard linked after the
restore. rdiff-backup also preserves permissions, user and group
ownership, modification time, device files, fifos, and symlinks.
Sometimes it is impossible for the information to be replicated
exactly on the destination. For instance, ownership cannot usually be
replicated without root acces windows file
systems may not be case sensitive and have no ownership at all.
rdiff-backup records file metadata in a separate file so that all
information is preserved even if the destination file system is
missing features.
Space efficient: Suppose you have a large
database file that changes a little bit every day. A normal
incremental backup would keep saving copy after copy of this database,
wasting a lot of space. rdiff-backup uses librsync, which implements
the same efficient diffing algorithm that rsync uses. It works on
binary files as well as text, so only a fraction of the data in your
database would be saved in each incremental backup.
Bandwidth efficient: rdiff-backup depends on
librsync, and thus uses the same diffing algorithm as rsync (rsync and
rdiff-backup strictly speaking do not share any code however). As a
result, when when writing to a remote location, rdiff-backup will only
send diffs over and can use much less bandwidth than, say, ftp or
For instance, suppose you slightly alter large file A to make large
file A', and A is still on the remote system. When rdiff-backup is
run, it will only send over the diff A->A' (in order to "copy" A' to
the remote system). Neither A nor A' needs to be sent in its
Transparent data format: Except for recording
the hard link structure of old data sets, rdiff-backup doesn't
absolutely require any data files formatted specifically for rdiff-backup.
So if you want to stop using rdiff-backup in the future, you won't be
stuck with any undecipherable files in some strange format. As noted
above, the mirror directory will just be a copy of the source
directory as it was when rdiff-backup was last run. Earlier states of
your files are saved just by 1) keeping a copy of them, 2) in diff
form as produced by rdiff, or 3) as a gzipped version of 1 or
Filesystem feature autodetection: People use
rdiff-backup in many different environments. The filesystem they want
to back up may be on Linux, Windows, or Mac. It may or may not be
case sensitive, support characters like ":", have resource forks,
extended attributes, or access control lists. Moreover, the file
system they are backing up to may or may not support these features.
rdiff-backup tries to handle these situations automatically without
the need for switches like --acl --ea --no-ownership, etc. When run
it will run tests on both the source and destination filesystems to
see what features each supports like case sensitivity, changing
uid/gid ownership, resource forks, extended attributes, or access
control lists. To see the results of this testing, run rdiff-backup
with verbosity 4 or higher, as in -v4.
Mac OS X resource fork support: On Mac OS X
systems, rdiff-backup will backup the resource forks which store, for
instance, Finder information. Most unix backup programs would only
backup the data forks and discard the resource forks.
ACL and EA support: If rdiff-backup can find
and pyxattr
() modules, and if the file system supports these features, rdiff-backup will preserve Access
Control Lists and user-level Extended Attributes. ACLs are not supported,
however, on Mac OS X or Windows as those systems do not use standard
POSIX.1e access controls.
Keeps statistics: After each session
rdiff-backup writes summary statistics to a text file. You can
inspect these to see how large your repository is, how fast it is
growing, and how much space rdiff-backup is saving you, and more.
Here is an example session_statistics file:
StartTime .00 (Sun Aug 14 06:22:01 2005)
EndTime .64 (Sun Aug 14 06:37:34 2005)
ElapsedTime 933.64 (15 minutes 33.64 seconds)
SourceFiles 975715
SourceFileSize
MirrorFiles 975604
MirrorFileSize
NewFiles 119
NewFileSize .05 MB)
DeletedFiles 8
DeletedFileSize 6 KB)
ChangedFiles 2032
ChangedSourceSize
ChangedMirrorSize
IncrementFiles 2233
IncrementFileSize .82 MB)
TotalDestinationSizeChange .88 MB)
rdiff-backup also saves very detailed statistics in a
file_statistics. This file is also in (compressed) text
form, but is usually too voluminous to read manually.