NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Upgrading openssh help
Hi all, I've been suffering from really slow rsync speeds when copying files from one NV+ to another. Speeds around 700k/sec compared to having a computer in between doing the copying via afp/nfs...
You're just not going to get 30 MB/sec on an NV+ with rsync. I get about 4 MB/sec on my rsync backup jobs (which uses the daemon method) - remote source is my Pro-6. So I think the results you are getting are normal.
Eirik in the original post says he got 7.5 MB/sec, but that was his only post (ever) so we can't follow up with him. But from the script, it appears that he built SSL, which isn't relevant if you don't use encryption. We don't know anything about his network setup, or how much memory was in his NAS. You could perhaps enable jumbo frames and see if you get any improvement.
Apart from that I have no suggestions.
So you're using Rsync, not Rsync over SSH...
http://www.tecmint.com/rsync-local-remote-file-synchronization-commands/
http://www.tecmint.com/rsync-local-remote-file-synchronization-commands/
jak0lantash wrote:
So you're using Rsync, not Rsync over SSH...Which means that upgrading ssl won't improve the performance - because you aren't using ssl for this anyway.
What performance are you seeing?
Sorry for the delay, had to sort out some cabling.
I'm quite confused.. My understanding is that by default rsync uses SSH for its communication - regardless of the -e prefix.I'm reading more about it,
http://linux.die.net/man/1/rsync
"There are two different ways for rsync to contact a remote system: using a remote-shell program as the transport (such as ssh or rsh) or contacting an rsync daemon directly via TCP. The remote-shell transport is used whenever the source or destination path contains a single colon (:) separator after a host specification. Contacting an rsync daemon directly happens when the source or destination path contains a double colon (::) separator after a host specification, OR when an rsync://"
I believe I'm using SSH, because this is how I'm running it,
xn1:/media/iso# rsync -av --progress large.iso xn2:/media/Files/
sending incremental file list
large.iso
21594112 3% 1.45MB/s 0:07:06
The above just has both NASs connected via a gigabit switch via cat6. Granted I'm surprised as usually it's half that speed.NAS1 ----(1G)---- Switch ----(1G)---- NAS2
While if I plug my MAC to the switch, mount both NAS's on my Mac via AFP/CIFS/NFS, drag and drop from one to the other via Finder, it's at least 10 times faster - 30MB+/sec. I could take a screenshot but it means I have to connect in the garage :)
Mac ----(1G)---- Switch -----(1G)----- NAS1 and NAS2
Edit: Here's an example from my Mac, connected via Wifi to the airport express connected via 100M link to the switch.
Mac ----(wifi)--- Airport Express ------(100M) ----- Switch -------(1G)------ NAS1 and NAS2
Yes it's not as fast as Gigabit ethernet, but again it's pushing some good limits with ~5.6M/sec and should show what I'm talking about when compared to the 2 NASs.
rsync -av --progress large.iso xn2:/media/Files/
This doesn't use SSH
http://www.tecmint.com/rsync-local-remote-file-synchronization-commands/
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
