Considering I have the rsync daemon running on my droboshare (which holds a first (named Drobo1), second generation Drobo (named Drobo) and Drobo-FS, 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]
Wait a minute. Is the other machine running rsync as well? If not, then your answer is no. Rsync can’t sync with a machine that does not have rsync.
Sorry, as far as I can google, Airport Extreme does not have an rsync server. Therefore, no rsyncing is possible*.
All of the error messages you are seeing are just rsync trying to establish a connection with something that isn’t there.
Well, technically, if the Drobo could mount remote shares locally, you could run rsync locally, between the Drobo own files and the mounted share. Since Drobos can’t mount remote shares, this is not possible either.
Ahhh, yes sir, you are absolutely correct. The AEBS does not run an rsync server. I was under the mistaken impression that you only needed it on one of the machines, so long as a destination/source path could be found. I thought that the owner of the process (in this case, the Drobo1) would handle both sides of the transmission and didn’t realize that you needed an rsync server on both ends.
Moreover, I appreciate you letting me know that Drobos cannot mount remote shares, as that would have been my next attempt. :o)
[quote=“ricardo, post:2, topic:2559”]
Wait a minute. Is the other machine running rsync as well? If not, then your answer is no. Rsync can’t sync with a machine that does not have rsync.
Sorry, as far as I can google, Airport Extreme does not have an rsync server. Therefore, no rsyncing is possible*.
All of the error messages you are seeing are just rsync trying to establish a connection with something that isn’t there.
Well, technically, if the Drobo could mount remote shares locally, you could run rsync locally, between the Drobo own files and the mounted share. Since Drobos can’t mount remote shares, this is not possible either.
[/quote][hr]
Yes, I do have a Mac and will go that route. I was trying to take the middle-man (Mac) out of the equation such that the Drobo could have a periodic scheduled job to sync with the external drive, but it looks like that isn’t in the cards.