Rsync - Revision history

Christoph: /* External links */

2015-07-11T21:34:39Z

‎External links

Christoph: /* Rsync exit values */

2015-07-11T20:03:55Z

‎Rsync exit values

Christoph at 19:47, 11 July 2015

2015-07-11T19:47:47Z

Christoph at 19:43, 11 July 2015

2015-07-11T19:43:36Z

Christoph: /* Examples */

2014-05-13T11:16:57Z

‎Examples

Christoph: /* Examples */

2014-01-12T02:07:00Z

‎Examples

Christoph: /* Examples */

2014-01-09T22:44:40Z

‎Examples

Christoph: /* Examples */

2013-11-17T00:13:55Z

‎Examples

Christoph: /* Examples */

2013-11-08T16:27:30Z

‎Examples

Christoph: /* External links */

2012-05-30T23:20:37Z

‎External links

@@ Line 246: / Line 246: @@
 *[http://www.mikerubel.org/computers/rsync_snapshots/ Easy Automated Snapshot-Style Backups with Linux and Rsync]
 *[http://rsync.samba.org/tech_report/node2.html rsync algorithm]
-*[http://archive.macosxlabs.org/rsyncx/rsyncx.html RsyncX] - Frontend for rsync under Mac OS X
+*[https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Automated_Backup OpenSSH/Cookbook/Automated Backup] on Wikibooks
 *[[wikipedia:rsync]]

@@ Line 212: / Line 212: @@
      Timeout waiting for daemon connection
 </pre>
 ==Variations==

@@ Line 1: / Line 1: @@
-'''rsync''' is a [[:Category:Linux Command Line Tools|command line tool]] which [[File synchronization|synchronizes]] files and directories from one location to another while minimizing data transfer using delta encoding when appropriate. An important feature of <tt>rsync</tt> not found in most similar programs/protocols is that the mirroring takes place with only one transmission in each direction.
+'''rsync''' is a [[:Category:Linux Command Line Tools|command line tool]] which synchronizes files and directories from one location to another while minimizing data transfer using delta encoding when appropriate. An important feature of <tt>rsync</tt> not found in most similar programs/protocols is that the mirroring takes place with only one transmission in each direction.
 <tt>rsync</tt> can copy or display directory contents and copy files, optionally using compression and recursion.
-<tt>rsync</tt> has the default [[Transmission Control Protocol|TCP]] port of 873.
+<tt>rsync</tt> has the default TCP port of 873.
 ==The rsync algorithm==
@@ Line 27: / Line 27: @@
 * Copy files to/from computers in your local area network
-Consider a case where you have two computers plugged into your home router. To copy files/directories between the two, first find out their local IPv4 addresses (e.g., configured to use eth0) using <code>`[[ifconfig]]`</code> or <code>`ip a`</code>. The following command will copy files between the two machines (make sure your [[firewall]] rules allow connections via [[iptables|port 22]] for [[SSH]]):
+Consider a case where you have two computers plugged into your home router. To copy files/directories between the two, first find out their local IPv4 addresses (e.g., configured to use eth0) using <code>`[[ifconfig]]`</code> or <code>`ip a`</code>. The following command will copy files between the two machines (make sure your firewall rules allow connections via [[iptables|port 22]] for [[SSH]]):
   $ rsync -e 'ssh -p 22' -avl --stats --progress /home/bob/source bob@192.168.0.2:/home/bob/destination
@@ Line 153: / Line 153: @@
 </pre>
-Note in particular the initial rsync of the ChangeLog to determine if anything has changed. This could be omitted but it would mean that the rsyncd on vger would have to build a complete listing of the cvs area at each run. As most of the time nothing will have changed I wanted to save the time on vger by only doing a full rsync if the ChangeLog has changed. This helped quite a lot because vger is low on memory and generally quite heavily loaded, so doing a listing on such a large tree every hour would have been excessive.
+Note in particular the initial rsync of the ChangeLog to determine if anything has changed. This could be omitted but it would mean that the rsyncd on vger would have to build a complete listing of the cvs area at each run. As most of the time nothing will have changed, I wanted to save the time on vger by only doing a full rsync if the ChangeLog has changed. This helped quite a lot because vger is low on memory and generally quite heavily loaded, so doing a listing on such a large tree every hour would have been excessive.
 ===Automated backup at home===
@@ Line 239: / Line 239: @@
 *[http://www.mikerubel.org/computers/rsync_snapshots/ Easy Automated Snapshot-Style Backups with Linux and Rsync]
 *[http://rsync.samba.org/tech_report/node2.html rsync algorithm]
-*[http://archive.macosxlabs.org/rsyncx/rsyncx.html RsyncX] - Frontend for rsync under [[Mac OS X]]
+*[http://archive.macosxlabs.org/rsyncx/rsyncx.html RsyncX] - Frontend for rsync under Mac OS X
 *[[wikipedia:rsync]]

← Older revision		Revision as of 19:43, 11 July 2015
Line 184:		Line 184:

	note that that is backquotes enclosed by quotes (some browsers don't show that correctly).		note that that is backquotes enclosed by quotes (some browsers don't show that correctly).
		+
		+	==Rsync exit values==
		+	Note: Obtained via the man page. Capture exit value with <code>`$?`</code>.
		+
		+	<pre>
		+	0 Success
		+	1 Syntax or usage error
		+	2 Protocol incompatibility
		+	3 Errors selecting input/output files, dirs
		+	4 Requested action not supported: an attempt was made to manipulate 64-bit
		+	files on a platform that cannot support them; or an option was specified
		+	that is supported by the client and not by the server.
		+	5 Error starting client-server protocol
		+	6 Daemon unable to append to log-file
		+	10 Error in socket I/O
		+	11 Error in file I/O
		+	12 Error in rsync protocol data stream
		+	13 Errors with program diagnostics
		+	14 Error in IPC code
		+	20 Received SIGUSR1 or SIGINT
		+	21 Some error returned by waitpid()
		+	22 Error allocating core memory buffers
		+	23 Partial transfer due to error
		+	24 Partial transfer due to vanished source files
		+	25 The --max-delete limit stopped deletions
		+	30 Timeout in data send/receive
		+	35 Timeout waiting for daemon connection
		+	</pre>

	==Variations==		==Variations==

@@ Line 34: / Line 34: @@
   $ rsync -e 'ssh -p 22' -avl --stats --progress /home/source/foo-{1..3}.jpg bob@192.168.0.2:/home/destination
 <!--<pre style="overflow: auto;">-->
 ==rsyncd.conf==

@@ Line 21: / Line 21: @@
 ===Examples===
 Let us say you wish to <tt>rsync</tt> your home directory (e.g. <code>/home/bob</code>) with a backup directory/disk (e.g. <code>/backup</code>). The following command will accomplish this:
-  rsync -avz --delete /home/bob/ /backup/
+  $ rsync -avz --delete /home/bob/ /backup/
 where <code>a</code> means archive, <code>v</code> means do it verbosely, <code>z</code> means compress the data, and <code>delete</code> means to delete the backup file '''if''' the original file (i.e. in <code>/home/bob</code>) has been deleted since the last <tt>rsync</tt>.
@@ Line 27: / Line 27: @@
 * Copy files to/from computers in your local area network
-Let's say you have two computers plugged into your home router. To copy files/directories between the two, first find out their local IPv4 addresses (e.g., configured to use eth0) using <code>`[[ifconfig]]`</code>. The following command will copy files between the two machines (make sure your [[firewall]] rules allow connections via [[iptables|port 22]] for [[SSH]]):
+Consider a case where you have two computers plugged into your home router. To copy files/directories between the two, first find out their local IPv4 addresses (e.g., configured to use eth0) using <code>`[[ifconfig]]`</code> or <code>`ip a`</code>. The following command will copy files between the two machines (make sure your [[firewall]] rules allow connections via [[iptables|port 22]] for [[SSH]]):
-  rsync -e 'ssh -p 22' -avl --stats --progress /home/bob/source bob@192.168.0.2:/home/bob/destination
+  $ rsync -e 'ssh -p 22' -avl --stats --progress /home/bob/source bob@192.168.0.2:/home/bob/destination
 ==rsyncd.conf==

@@ Line 20: / Line 20: @@
 ==Usage==
 ===Examples===
-Let's say you wish to <tt>rsync</tt> your home directory (e.g. <code>/home/bob</code>) with a backup directory/disk (e.g. <code>/backup</code>). The following command will accomplish this:
+Let us say you wish to <tt>rsync</tt> your home directory (e.g. <code>/home/bob</code>) with a backup directory/disk (e.g. <code>/backup</code>). The following command will accomplish this:
   rsync -avz --delete /home/bob/ /backup/
-where <code>a</code> means archive, <code>v</code> mean do it verbosely, <code>z</code> mean compress the data, and <code>delete</code> means to delete the backup file '''if''' the original file (i.e. in <code>/home/bob</code>) has been deleted since the last <tt>rsync</tt>.
+where <code>a</code> means archive, <code>v</code> means do it verbosely, <code>z</code> means compress the data, and <code>delete</code> means to delete the backup file '''if''' the original file (i.e. in <code>/home/bob</code>) has been deleted since the last <tt>rsync</tt>.
 The same can be done where the backup disk is on a remote machine via [[ssh]]. See [http://www.howtoforge.com/rsync_incremental_snapshot_backups here] for more information.

← Older revision		Revision as of 16:27, 8 November 2013
Line 25:		Line 25:

	The same can be done where the backup disk is on a remote machine via [[ssh]]. See [http://www.howtoforge.com/rsync_incremental_snapshot_backups here] for more information.		The same can be done where the backup disk is on a remote machine via [[ssh]]. See [http://www.howtoforge.com/rsync_incremental_snapshot_backups here] for more information.
		+
		+	* Copy files to/from computers in your local area network
		+	Let's say you have two computers plugged into your home router. To copy files/directories between the two, first find out their local IPv4 addresses (e.g., configured to use eth0) using <code>`[[ifconfig]]`</code>. The following command will copy files between the two machines (make sure your [[firewall]] rules allow connections via [[iptables\|port 22]] for [[SSH]]):
		+	rsync -e 'ssh -p 22' -avl --stats --progress /home/bob/source bob@192.168.0.2:/home/bob/destination

	==rsyncd.conf==		==rsyncd.conf==