Comments on: Easy Rsync Remote Backups Using SSH Keys

By: Using Rsync as a Backup Solution

Using Rsync as a Backup Solution — Wed, 14 Dec 2011 05:58:35 +0000

[...] solution is to setup password-less login with an SSH key. This will encrypt the sign in, but it does mean that a third party that gains access to your [...]

By: Backup Important Server Files with Rsync

Backup Important Server Files with Rsync — Thu, 16 Jun 2011 17:12:40 +0000

[...] order to have the process fully automated without having to manually login, you will need to setup SSH keys on your server and remote backup [...]

By: Vinay

Vinay — Tue, 23 Nov 2010 14:16:54 +0000

just to add to my last query I am expecting to be prompted for password and that is also not coming.
tried using rsync on both the machines locally and that is working.

By: Vinay

Vinay — Tue, 23 Nov 2010 14:15:11 +0000

I want to do this remote rsync just one off to create a one time back up for a few days
(need to preserve premissions and timings etc so using rsync)

soo no ssh keys

while specifying the remote directory i am giving as below

I am trying the below commnad

/software/rsync/usr/local/bin/rsync -rlptgov –rsync-path=/software/rsync/usr/local/bin/rsync –delete myUser@123.123.123.123 :/t1 t2

Intending to copy from remote directory t1 to directory t2
I am getting the below response
receiving incremental file list
rsync: change_dir#3 “123.123.123.123″ failed: No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(707) [sender=3.0.4]
rsync: connection unexpectedly closed (9 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(632) [receiver=3.0.4]

If you can kindly guide ?

By: John

John — Thu, 12 Nov 2009 18:04:46 +0000

you need to limit what command is executed when sync without password, prefix the key with command=”/path/to/validating/script”.

As an example, your secured authorized_keys file might look like:

command=”/home/user/validate-rsync.sh” ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAyNChQxw/+Da….= user@remotehost.com

Finally, put something like the following in your validate-rsync.sh file:

#!/bin/sh
case “$SSH_ORIGINAL_COMMAND” in
*\&*)
echo “Rejected”
;;
*\;*)
echo “Rejected”
;;
rsync\ –server*)
$SSH_ORIGINAL_COMMAND
;;
*)
echo “Rejected”
;;
esac

Make it executable by typing: chmod +x ~/validate-rsync.sh.

This will check to see if the ssh session is being used to execute an rsync backup.

If it is being used for anything else, the session will be rejected and closed.

Nice tutorial bro…