Rsync eng - Revision history

Eocakovs: /* Via remote shell */

2017-05-08T07:55:56Z

Via remote shell

← Older revision		Revision as of 10:55, 8 May 2017
Line 190:		Line 190:
	I will not go trough full SSH setup, for that please see [http://troy.jdmz.net/rsync/index.html this] link.		I will not go trough full SSH setup, for that please see [http://troy.jdmz.net/rsync/index.html this] link.

	Additionally here are two great articles that will explain ~~SHH~~ more in depth:		Additionally here are two great articles that will explain SSH more in depth:
	[https://wiki.itcollege.ee/index.php/SSH_for_beginners] SSH for beginners by Etienne Barrier.		[https://wiki.itcollege.ee/index.php/SSH_for_beginners] SSH for beginners by Etienne Barrier.
	[https://wiki.itcollege.ee/index.php/SSH_Encryption] SSH Encryption by Frank Korving.		[https://wiki.itcollege.ee/index.php/SSH_Encryption] SSH Encryption by Frank Korving.

Eocakovs: /* Via remote shell */

2017-05-08T07:55:33Z

Via remote shell

← Older revision		Revision as of 10:55, 8 May 2017
Line 191:		Line 191:

	Additionally here are two great articles that will explain SHH more in depth:		Additionally here are two great articles that will explain SHH more in depth:
	1. [https://wiki.itcollege.ee/index.php/SSH_for_beginners] SSH for beginners by Etienne Barrier.		[https://wiki.itcollege.ee/index.php/SSH_for_beginners] SSH for beginners by Etienne Barrier.
	2. [https://wiki.itcollege.ee/index.php/SSH_Encryption] SSH Encryption by Frank Korving.		[https://wiki.itcollege.ee/index.php/SSH_Encryption] SSH Encryption by Frank Korving.

	:The basics go like this:		:The basics go like this:

Eocakovs: /* Via remote shell */

2017-05-08T07:54:48Z

Via remote shell

← Older revision		Revision as of 10:54, 8 May 2017
Line 188:		Line 188:
	;At this point you should have both Rsync and SSH on all machines involved in the data transfer.		;At this point you should have both Rsync and SSH on all machines involved in the data transfer.

	~~<pre>~~I will not go trough full SSH setup, for that please see [http://troy.jdmz.net/rsync/index.html this] link.		I will not go trough full SSH setup, for that please see [http://troy.jdmz.net/rsync/index.html this] link.

	Additionally here are two great articles that will explain SHH more in depth:		Additionally here are two great articles that will explain SHH more in depth:
	1. [https://wiki.itcollege.ee/index.php/SSH_for_beginners] SSH for beginners by Etienne Barrier.		1. [https://wiki.itcollege.ee/index.php/SSH_for_beginners] SSH for beginners by Etienne Barrier.
	2. [https://wiki.itcollege.ee/index.php/SSH_Encryption] SSH Encryption by Frank Korving~~</pre>~~		2. [https://wiki.itcollege.ee/index.php/SSH_Encryption] SSH Encryption by Frank Korving.

	:The basics go like this:		:The basics go like this:

Eocakovs: /* Via remote shell */

2017-05-08T07:53:36Z

Via remote shell

← Older revision		Revision as of 10:53, 8 May 2017
Line 189:		Line 189:

	<pre>I will not go trough full SSH setup, for that please see [http://troy.jdmz.net/rsync/index.html this] link.		<pre>I will not go trough full SSH setup, for that please see [http://troy.jdmz.net/rsync/index.html this] link.

	Additionally here are two great articles that will explain SHH more in depth:		Additionally here are two great articles that will explain SHH more in depth:
	1. [https://wiki.itcollege.ee/index.php/SSH_for_beginners] SSH for beginners by Etienne Barrier.		1. [https://wiki.itcollege.ee/index.php/SSH_for_beginners] SSH for beginners by Etienne Barrier.

Eocakovs: /* Via remote shell */

2017-05-08T07:53:13Z

Via remote shell

← Older revision		Revision as of 10:53, 8 May 2017
Line 187:		Line 187:

	;At this point you should have both Rsync and SSH on all machines involved in the data transfer.		;At this point you should have both Rsync and SSH on all machines involved in the data transfer.
	:I will not go trough full SSH setup, for that please see [http://troy.jdmz.net/rsync/index.html this] link.
			<pre>I will not go trough full SSH setup, for that please see [http://troy.jdmz.net/rsync/index.html this] link.
			Additionally here are two great articles that will explain SHH more in depth:
			1. [https://wiki.itcollege.ee/index.php/SSH_for_beginners] SSH for beginners by Etienne Barrier.
			2. [https://wiki.itcollege.ee/index.php/SSH_Encryption] SSH Encryption by Frank Korving</pre>

	:The basics go like this:		:The basics go like this:
Line 196:		Line 200:
	:*Generate keys on both machines. Leave the passphrase empty if you would like to use this authentication method for automated scripts.		:*Generate keys on both machines. Leave the passphrase empty if you would like to use this authentication method for automated scripts.
	:<pre>ssh-keygen -t rsa -b 4096 -a 1000 -f ~/.ssh/key_file</pre>		:<pre>ssh-keygen -t rsa -b 4096 -a 1000 -f ~/.ssh/key_file</pre>
			:This will generate an RSA private key <code>~/.ssh/key_file</code> and public key <code>~/.ssh/key_file.pub</code>.

	:* Copy public key from client to server		:* Copy public key from client to server
	:<pre>ssh-copy-id -i ~/.ssh/key_file user@IP-address</pre>		:<pre>ssh-copy-id -i ~/.ssh/key_file user@IP-address</pre>

Eocakovs: /* Tips and tricks */

2017-05-08T07:46:20Z

Tips and tricks

← Older revision		Revision as of 10:46, 8 May 2017
Line 342:		Line 342:
	:Depending witch option you chose you would write something like this in to script file:		:Depending witch option you chose you would write something like this in to script file:
	<source lang="bash">#!/bin/bash		<source lang="bash">#!/bin/bash
	rsync -avz -e 'ssh -i /path/to/~~pemfile.pem~~' user@10.0.2.20:/path/to/source /path/to/destination</source>		rsync -avz -e 'ssh -i /path/to/private_key' user@10.0.2.20:/path/to/source /path/to/destination</source>
	:And something like this in to Makefile:		:And something like this in to Makefile:
	<source lang="make">backup:		<source lang="make">backup:
	rsync -avz -e 'ssh -i /path/to/~~pemfile.pem~~' user@10.0.2.20:/path/to/source /path/to/destination</source>		rsync -avz -e 'ssh -i /path/to/private_key' user@10.0.2.20:/path/to/source /path/to/destination</source>
	:Then you would edit your Crontab like so:		:Then you would edit your Crontab like so:
	:<pre>crontab -e</pre>		:<pre>crontab -e</pre>

Eocakovs: /* Remote source or destination */

2017-05-08T07:44:10Z

Remote source or destination

← Older revision		Revision as of 10:44, 8 May 2017
Line 276:		Line 276:

	<pre>rsync -tavz *.c username@10.0.2.20::module_name</pre>		<pre>rsync -tavz *.c username@10.0.2.20::module_name</pre>

			As you can see in daemon mode we specify remote destination ip followed by <code>::</code> and the module we want to use, as per installation instructions module contains all the configuration options. And note that <code>username</code> is a user specified in <code>/path/to/rsyncd.scrt</code>.

	* Remote shell		* Remote shell
Line 282:		Line 284:

	<code>/path/to/private_key</code> will usually be <code>~/.ssh/id_rsa</code> if you generated a key pair using <code>ssh-keygen -f ~/.ssh/id_rsa -t rsa -b 4096</code>		<code>/path/to/private_key</code> will usually be <code>~/.ssh/id_rsa</code> if you generated a key pair using <code>ssh-keygen -f ~/.ssh/id_rsa -t rsa -b 4096</code>

	As you can see in daemon mode we specify remote destination ip followed by <code>::</code> and the module we want to use, as per installation instructions module contains all the configuration options. And note that <code>username</code> is a user specified in <code>/path/to/rsyncd.scrt</code>.

	In remote shell mode we specify remote shell via -e option and SSH <code>user</code> followed by <code>@</code> and ip of the destination followed by <code>:</code> and destination path.		In remote shell mode we specify remote shell via -e option and SSH <code>user</code> followed by <code>@</code> and ip of the destination followed by <code>:</code> and destination path.

Eocakovs: /* Remote source or destination */

2017-05-08T07:43:40Z

Remote source or destination

← Older revision		Revision as of 10:43, 8 May 2017
Line 281:		Line 281:
	<pre>rsync -tavz -e 'ssh -i /path/to/private_key' *.c user@10.0.2.20:src/</pre>		<pre>rsync -tavz -e 'ssh -i /path/to/private_key' *.c user@10.0.2.20:src/</pre>

	<code>/path/to/private_key</code> will usually be ~/.ssh/id_rsa if you generated a key pair using <code>ssh-keygen -f ~/.ssh/id_rsa -t rsa -b 4096</code>		<code>/path/to/private_key</code> will usually be <code>~/.ssh/id_rsa</code> if you generated a key pair using <code>ssh-keygen -f ~/.ssh/id_rsa -t rsa -b 4096</code>

	As you can see in daemon mode we specify remote destination ip followed by <code>::</code> and the module we want to use, as per installation instructions module contains all the configuration options. And note that <code>username</code> is a user specified in <code>/path/to/rsyncd.scrt</code>.		As you can see in daemon mode we specify remote destination ip followed by <code>::</code> and the module we want to use, as per installation instructions module contains all the configuration options. And note that <code>username</code> is a user specified in <code>/path/to/rsyncd.scrt</code>.

Eocakovs: /* Remote source or destination */

2017-05-08T07:42:36Z

Remote source or destination

← Older revision		Revision as of 10:42, 8 May 2017
Line 279:		Line 279:
	* Remote shell		* Remote shell

	<pre>rsync -tavz -e 'ssh -i /path/to/private_key~~.pem~~' *.c user@10.0.2.20:src/</pre>		<pre>rsync -tavz -e 'ssh -i /path/to/private_key' *.c user@10.0.2.20:src/</pre>

			<code>/path/to/private_key</code> will usually be ~/.ssh/id_rsa if you generated a key pair using <code>ssh-keygen -f ~/.ssh/id_rsa -t rsa -b 4096</code>

	As you can see in daemon mode we specify remote destination ip followed by <code>::</code> and the module we want to use, as per installation instructions module contains all the configuration options. And note that <code>username</code> is a user specified in <code>/path/to/rsyncd.scrt</code>.		As you can see in daemon mode we specify remote destination ip followed by <code>::</code> and the module we want to use, as per installation instructions module contains all the configuration options. And note that <code>username</code> is a user specified in <code>/path/to/rsyncd.scrt</code>.
Line 287:		Line 289:
	A bit more complex sample using ssh from remote source to local destination.		A bit more complex sample using ssh from remote source to local destination.

	<pre>rsync -avz -e 'ssh -i /path/to/~~pemfile.pem~~' user@10.0.2.20:/file{1,2} :/file3 user@172.16.1.10:/file4 /path/to/destination</pre>		<pre>rsync -avz -e 'ssh -i /path/to/private_key' user@10.0.2.20:/file{1,2} :/file3 user@172.16.1.10:/file4 /path/to/destination</pre>
	This would transfer files - file1, file2, file3 from <code>10.0.2.20</code> and file4 from <code>172.16.1.10</code> to /path/to/destination on local machine. It shows the versatility of Rsync, you can specify several individual files on remote host - <code>:/file1 :/file2</code> or you can specify a pattern <code>/file{1,2}</code>. Also you can specify several remote hosts if the ssh key you provided will match public key on remote machines.		This would transfer files - file1, file2, file3 from <code>10.0.2.20</code> and file4 from <code>172.16.1.10</code> to /path/to/destination on local machine. It shows the versatility of Rsync, you can specify several individual files on remote host - <code>:/file1 :/file2</code> or you can specify a pattern <code>/file{1,2}</code>. Also you can specify several remote hosts if the ssh key you provided will match public key on remote machines.

Line 295:		Line 297:
	Directory copy works the same as in local-only mode only difference is that you have to specify remote host:		Directory copy works the same as in local-only mode only difference is that you have to specify remote host:

	<pre>rsync -avz -e 'ssh -i /path/to/~~pemfile.pem~~' user@10.0.2.20:/path/to/source /path/to/destination</pre>		<pre>rsync -avz -e 'ssh -i /path/to/private_key' user@10.0.2.20:/path/to/source /path/to/destination</pre>

	or		or

Eocakovs: /* Via remote shell */

2017-05-08T06:32:24Z

Via remote shell

← Older revision		Revision as of 09:32, 8 May 2017
Line 195:		Line 195:
	:<pre>sudo service ssh start</pre>		:<pre>sudo service ssh start</pre>
	:*Generate keys on both machines. Leave the passphrase empty if you would like to use this authentication method for automated scripts.		:*Generate keys on both machines. Leave the passphrase empty if you would like to use this authentication method for automated scripts.
	:<pre>ssh-keygen -t rsa -b 4096 -f ~/.ssh/key_file</pre>		:<pre>ssh-keygen -t rsa -b 4096 -a 1000 -f ~/.ssh/key_file</pre>
	:* Copy public key from client to server		:* Copy public key from client to server
	:<pre>ssh-copy-id -i ~/.ssh/key_file user@IP-address</pre>		:<pre>ssh-copy-id -i ~/.ssh/key_file user@IP-address</pre>

			:Please remeber that file permissions for ~/.ssh directory and its subfiles needs to be strict, to make sure of that run the following commands:
			:<pre>chmod 700 ~/.ssh/</pre>
			:<pre>chmod 600 ~/.ssh/*</pre>

	When Rsync is used via SSH you can still use Rsync in daemon mode to use preconfigure modules, see subsection Daemon mode of [[Rsync_eng#Setup\|Setup]]. In that case only the usage syntax will change as specified in [[Rsync_eng#Usage\|Usage]] section.		When Rsync is used via SSH you can still use Rsync in daemon mode to use preconfigure modules, see subsection Daemon mode of [[Rsync_eng#Setup\|Setup]]. In that case only the usage syntax will change as specified in [[Rsync_eng#Usage\|Usage]] section.