I’ve been combing the forums and looking for a way to rsync between 2 Drobos (one 2nd Gen on a Droboshare and on DroboFS) without a computer as a mediator. I was given to understand that this is possible, but I don’t know how to make it happen.
I have successfully installed rsync on both the Droboshare and the DroboFS with the following respective rsyncd.conf files:
As it happens, I was finally able to get things working by first going to the droboshare via ssh and invoking the rsync command using the full path, as you suggested.
Just so the next poor slob doesn’t run into the same consuming frustration that I did, I’ll include the steps below. These worked for me and YMMV, but please understand that the IP addresses and network names in my examples apply only to my local network setup. You will need to gather your own IPs and switch them out.
(This assumes you have DroboApps Admin installed on your device http://Your.Drobo’s.IP.Address:8080)
1.) Click the “Install DroboApps” link
2.) Install Dropbear SSH AND rsync
4.) Edit the \Droboshare\Drobo\DroboApps\rsync\rsyncd.conf to include "Read Only = false’ like so:
5.) Restart the Droboshare again, so the settings take effect
6.) Once the device reboots and the service is running, ssh to your Droboshare or DroboFS, as appropriate (I used Terminal on a MacBook)
Remember that the default user/pass for Dropbear is either root/root or root/giveit2me. If the IP address of my Droboshare were 192.168.0.144:
7.) Once you authenticate with your password, you just need to give the full path to the rsync command, the switches you wish to apply, followed by the source you want to copy and then the destination you want to copy to.
–This copies the contents of the Drobo share point (Drobo) to the base directory of the Drobo FS (/Public):
-a, --archive archive mode; equals -rlptgoD (no -H,-A,-X)
-r, --recursive recurse into directories
-l, --links copy symlinks as symlinks
-p, --perms preserve permissions
-t, --times preserve modification times
-g, --group preserve group
-o, --owner preserve owner (super-user only)
-D same as --devices --specials
--devices preserve device files (super-user only)
--specials preserve special files
-v, --verbose increase verbosity
-i, --itemize-changes output a change-summary for all updates
-P same as --partial --progress
--partial keep partially transferred files
--progress show progress during transfer
In other words, -aviP will produce quite a lot of output, which is nice to figure out what is happening. Otherwise, it’ll try to continue transfer from where it started whenever possible (which is good for large files).
I probably should warn you that -u may be a dangerous option if both devices do not have their clocks synced periodically. Use it with care.
Finally, the most important switch is this one:
-n, --dry-run perform a trial run with no changes made
Always use -n before actually trying to rsync your data. If you messed up the switches, nothing bad will happen to your data.
Considering I have the rsync daemon running on my droboshare (which holds a first (named Drobo1) and second generation Drobo (named Drobo), shouldn’t I be able to rsync files from Drobo1 to another machine on the network?
I would like to copy a directory FROM Drobo1 to an external drive plugged into the back of my airport extreme base station.
If the airport extreme base station has an ip address of 192.168.0.141 and the name of the external drive plugged into it is Ravage, I would assume that the following would work:
But I end up with the following error:
rsync: failed to connect to 192.168.0.141: Connection refused (111)
Any idea how I can correctly rsync from the Drobo1 the airport disk?
Note: the error is a refused connection vs a broken pipe or “No such file or directory,” so I’m assuming that I’m hitting the right place and just need the correct credentials.
Not getting any of these:
rsync: Failed to exec ssh: No such file or directory (2)
rsync error: error in IPC code (code 14) at pipe.c(84) [sender=3.0.3]
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
rsync error: error in IPC code (code 14) at io.c(1544) [sender=3.0.3]
rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.3]