|Original author(s)||Andrew Tridgell, Paul Mackerras|
|Initial release||June 19, 1996|
|Stable release||3.0.9 (September 23, 2011[±])|
|Type||Data transfer, Differential backup|
rsync is a utility software and network protocol for Unix-like systems (with ports to Windows) that synchronizes files and directories from one location to another while minimizing data transfer by using delta encoding when appropriate. Quoting the official website: "rsync is a file transfer program for Unix systems. rsync uses the 'rsync algorithm' which provides a very fast method for bringing remote files into sync." An important feature of rsync not found in most similar programs/protocols is that the mirroring takes place with only one transmission in each direction.[why?] rsync can copy or display directory contents and copy files, optionally using compression and recursion.
In daemon mode, rsync listens on the default TCP port of 873, serving files in the native rsync protocol or via a remote shell such as RSH or SSH. In the latter case, the rsync client executable must be installed on the remote machine as well as on the local machine.
Andrew Tridgell and Paul Mackerras wrote the original rsync. Tridgell discusses the design, implementation and performance of rsync in chapters 3 through 5 of his Australian National University Ph.D. thesis.
rsync was originally written as a replacement for rcp and scp. As such, it has a similar syntax to its parent programs. Like its predecessors, it still requires a source and a destination to be specified, either of which may be remote, but not both. Because of the flexibility, speed and scriptability of rsync, it has become a standard Linux utility and is included in all popular Linux distributions. It has also been ported to Windows (via Cygwin, Grsync or SFU) and Mac OS.
rsync [OPTION] … SRC [SRC] … [USER@]HOST:DEST rsync [OPTION] … [USER@]HOST:SRC [DEST]
...where SRC is the file or directory (or a list of multiple files and directories) to copy from, and DEST is the file or directory to copy to. Square brackets indicate optional parameters.
One of the earliest applications of rsync was to implement mirroring or backup for multiple Unix clients to a central Unix server using rsync/ssh and standard Unix accounts. It can also be used in desktop settings, for example to efficiently synchronize files with a backup copy on an external hard drive. With a scheduling utility such as cron, one can schedule automated encrypted rsync-based mirroring between multiple hosts and a central server.
A command line to mirror FreeBSD might look like:
% rsync -avz --delete ftp4.de.FreeBSD.org::FreeBSD/ /pub/FreeBSD/
The Apache HTTP Server supports only rsync for updating mirrors.
rsync -avz --delete --safe-links rsync.apache.org::apache-dist /path/to/mirror
The preferred (and simplest) way to mirror the PuTTY website to the current directory is to use rsync.
rsync -auH rsync://rsync.chiark.greenend.org.uk/ftp/users/sgtatham/putty-website-mirror/ .
#date=`date "+%Y-%m-%dT%H:%M:%S"` date=`date "+%FT%T"` rsync -aP --link-dest=$HOME/Backups/current /path/to/important_files $HOME/Backups/back-$date ln -nfs $HOME/Backups/back-$date $HOME/Backups/current
Determining which files to send 
By default rsync uses a quick method of determining which files differ between the sending and receiving systems, by checking the modification time and size of each file. This method uses very little CPU time, but it can occasionally miss files that have changed.
rsync can be forced to use a more comprehensive check by adding the
--checksum flag, which causes rsync to do a full checksum on every file. This ensures that rsync does not miss any changed files, but it is much slower and uses a lot of CPU time.
Determining which parts of a file have changed 
The rsync utility uses an algorithm invented by the Australian computer programmer Andrew Tridgell for efficiently transmitting a structure (such as a file) across a communications link when the receiving computer already has a similar, but not identical, version of the same structure.
The recipient splits its copy of the file into fixed-size non-overlapping chunks and computes two checksums for each chunk: the MD5 hash, and a weaker 'rolling checksum'. (Prior to version 30 of the protocol, released with rsync version 3.0.0, it used MD4 hashes rather than MD5.) It sends these checksums to the sender.
The sender computes the rolling checksum for every chunk of size S in its own version of the file, even overlapping chunks. This can be calculated efficiently because of a special property of the rolling checksum: if the rolling checksum of bytes n through n+S-1 is R, the rolling checksum of bytes n+1 through n+S can be computed from R, byte n, and byte n+S without having to examine the intervening bytes. Thus, if one had already calculated the rolling checksum of bytes 1...25, one could calculate the rolling checksum of bytes 2...26 solely from the previous checksum (R), byte 1 (n), and byte 26 (n+S).
The sender then compares its rolling checksums with the set sent by the recipient to determine if any matches exist. If they do, it verifies the match by computing the hash for the matching block and by comparing it with the hash for that block sent by the recipient.
The sender then sends the recipient those parts of its file that did not match the recipient's blocks, along with information on where to merge these blocks into the recipient's version. This makes the copies identical. However, there is a small probability that differences between chunks in the sender and recipient are not detected, and thus remains uncorrected. This requires a simultaneous hash collision in MD5 and the rolling checksum. It is possible to generate MD5 collisions, and the rolling checksum is not cryptographically strong, but the chance for this to occur by accident is nevertheless extremely remote. With 128 bits from MD5 plus 32 bits from the rolling checksum, and assuming maximum entropy in these bits, the probability of a hash collision with this combined checksum is 2−(128+32) = 2−160. The actual probability is a few times higher, since good checksums approach maximum output entropy but very rarely achieve it.
If the sender's and recipient's versions of the file have many sections in common, the utility needs to transfer relatively little data to synchronize the files. Note that if usual data compression algorithms are used, files that are similar when uncompressed may be very different when compressed, and thus the entire file will need to be transferred – local changes in uncompressed files yield global changes in compressed files. This is particularly an issue with mirroring of archive files, such as disk images and compressed tarballs, where often individual files change. Some compression programs, such as gzip, provide a special "rsyncable" mode which allows these files to be efficiently rsynced, by ensuring that local changes in the uncompressed file yields only local changes in the compressed file.
While the rsync algorithm forms the heart of the rsync application that essentially optimizes transfers between two computers over TCP/IP, the rsync application supports other key features that aid significantly in data transfers or backup. They include compression and decompression of data block by block using zlib at sending and receiving ends, and support for protocols such as ssh that enables encrypted transmission of compressed and efficient differential data using rsync algorithm. Instead of ssh, stunnel can also be used to create an encrypted tunnel to secure the data transmitted.
rsync is capable of limiting the bandwidth consumed during a transfer.
A utility called rdiff uses the rsync algorithm to generate delta files with the difference from file A to file B (like the utility diff, but in a different delta format). The delta file can then be applied to file A, turning it into file B (similar to the patch utility).
Unlike diff, the process of creating a delta file has two steps: first a signature file is created from file A, and then this (relatively small) signature and file B are used to create the delta file. Also unlike diff, rdiff works well with binary files.
- Using rdiff, a utility called rdiff-backup has been created, capable of maintaining a backup mirror of a file or directory either locally or remotely over the network, on another server. rdiff-backup stores incremental rdiff deltas with the backup, with which it is possible to recreate any backup point.
- Duplicity is a variation on rdiff-backup that allows for backups without cooperation from the storage server, as with simple storage services like Amazon S3. It works by generating the hashes for each block in advance, encrypting them, and storing them on the server, then retrieving them when doing an incremental backup. The rest of the data is also stored encrypted for security purposes.
- rsyncrypto is a utility to encrypt files in an rsync-friendly fashion. The rsyncrypto algorithm ensures that two almost identical files, when encrypted with rsyncrypto and the same key, will produce almost identical encrypted files. This allows for the low-overhead data transfer achieved by rsync while providing encryption for secure transfer and storage of sensitive data in a remote location.
An alternative to manually scripting rsync is the Free Software (FLOSS) GUI program BackupPC, which performs automatic scheduled backups to rsync servers.
As of Mac OS X 10.5 and later, there is a special -E or—extended-attributes switch which allows retaining much of the HFS file metadata when syncing between two machines supporting this feature. This is achieved by transmitting the proprietary Resource Fork along with the Data Fork.
Solutions using rsync 
|BackupAssist||No||No||Yes||Direct mirror or with history, VSS|
|Back In Time||Yes||No||No|
|Cwrsync||No||No||Yes||Rsync for Windows (based on Cygwin)|
|CarbonCopyCloner||No||Yes||No||Local whole disk backup|
|gadmin-rsync||Yes||No||No||Part of Gadmintools|
|Grsync||Yes||Yes||Yes Grsync for Windows||Graphical Interface for rsync on Linux Systems|
|DeltaCopy||No||No||Yes||Open Source, Free - WebSite - Download|
|Yintersync||No||No||Yes||VSS Shadow Copies, Email Reports, Scheduler, NTFS Permissions, Centralised.|
|Syncrify||Yes||Yes||Yes||Free for personal use, uses rsync protocol over HTTP(S), AES encryption, GUI, 2-way synchronization, written in Java|
|tym||Yes||No||No||time machine - Time rsYnc Machine (tym) - bash script - free|
|Duplicati||Yes||Yes||Yes||VSS, LVM snapshots, Scheduler|
|FolderWatch||No||Yes||No||Supports real-time and on-demand syncing|
|DropSync||No||Yes||No||SFTP Browser that uses rsync for transfers|
|Get Backup||No||Yes||No||Partial sync, comparison between sync, scheduler, disk cloning|
|Unison||Yes||Yes||Yes||Two-way file synchronizer using Rsync algorithm|
|rsnapshot||Yes||Yes||Yes||Snapshot-generating backup-tool using Rsync and hard links www.rsnapshot.org|
See also 
- Tridgell, Andrew (19 June 1996). "<email@example.com>#1/1 First release of rsync - rcp replacement". comp.os.linux.announce. Web link. Retrieved 2007-07-19.
- "NEWS for rsync 3.0.9 (23 Sep 2011)". 2011-09-23. Retrieved 2011-09-23.
- rsync features, Retrieved 29 Jul. 2012.
- Lossless compression handbook
- Web content caching and distribution: proceedings of the 8th International Workshop
- In-Place Rsync: File Synchronization for Mobile and Wireless Devices, David Rasch and Randal Burns, Department of Computer Science ,Johns Hopkins University
- Dempsey, Bert J.; Weiss, Debra (April 30, 1999). "Towards an Efficient, Scalable Replication Mechanism for the I2-DSI Project". Technical Report TR-1999-01. CiteSeerX: 10.1.1.95.5042.
- Andrew Tridgell: Efﬁcient Algorithms for Sorting and Synchronization, February 1999. Retrieved 29 Sept. 2009.
- Davison, Wayne (1 March 2008). "Rsync 3.0.0 released". rsync-announce mailing list. http://lists.samba.org/archive/rsync-announce/2008/000057.html.
- See the README file
- How to Mirror FreeBSD (With rsync)
- How to become a mirror for the Apache Software Foundation
- PuTTY Web Site Mirrors: Mirroring guidelines
- Rsync setup to run like Time Machine
- NEWS for rsync 3.0.0 (1 Mar 2008)