× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

RSYNC Over SSH

hecs1969
Aspirant

RSYNC Over SSH

Hello Team,

Having an issue with RSYNC over ssh. Remote RSYNC server appears to be working; however, when attempting to do the operation with the "RSYNC over ssh" nothing happens.
I've exported the public ssh key and have imported it on the second NAS via CLI and per instructions on "METHOD 2" of this article:

http://kb.netgear.com/app/answers/detail/a_id/12263/~/setting-up-rsync-over-ssh-(x86)#sync_remote

I've also created a new public key using ssh-keygen and added it to the 'authorized_keys' on the second NAS but no luck.

Anyone out there been successful using the RSYNC over ssh?

Thanks
Message 1 of 6
mdgm-ntgr
NETGEAR Employee Retired

Re: RSYNC Over SSH

What model ReadyNAS units are these? What firmware version are they running?

Have you forwarded the necessary port to the remote NAS?

Is the SSH service running on the remote NAS? Be sure to set a strong admin password before enabling SSH.
Message 2 of 6
hecs1969
Aspirant

Re: RSYNC Over SSH

Thanks for the reply.
I've got ReadyNAS pro6 initiating the rsync pulling from a ReadyNAS 516
Both firmwares are up-to-date on both NAS
Yes, ports have been forwarded. Normal rsync job works, the rsync over ssh does not. I'm trying without password first just to establish successful connection, when it works, I will establish strong password.
SSH running on both units as well as each share set for rsync access.
Message 3 of 6
mdgm-ntgr
NETGEAR Employee Retired

Re: RSYNC Over SSH

What are the full settings for the backup job?

Do you get any error messages? Does anything show up in the backup job log?
Message 4 of 6
hecs1969
Aspirant

Re: RSYNC Over SSH

NAS Pro6
Remote: Rsync Server, added the remote host with check-box "tunnel Rsync over ssh" enabled, Tested connection successfully. I had an issue earlier when testing the connection, as it only would connect successfully if 'tunnel rsync over ssh' was not enabled. Adding a "\" (back slash) to the path resolved the issue of testing the connection successfully with "tunnel rsync over ssh" enabled. I still think its something related to the path as the logs only say this:

Note that I replaced the public ip to remain private
-----------------------------------------------------------------------------
INCREMENTAL Backup started. Sun Mar 1 20:15:27 PST 2015

Job: 004
Protocol: rsync
Source: 66.66.66.66:/Shared\
Destination: [vdibkup]//avat

This is the only thing that appears on the log of the web interface. I've also downloaded all logs but don't know were to look for other errors.

Thanks for your help
Message 5 of 6
hecs1969
Aspirant

Re: RSYNC Over SSH

I believe I've got it figured out.
On the READYNAS516 units, the volume shares start with "/data" then the name of the shares.
It would connect successfully during the 'test connection'; however, when running the backup the log would only say "backup started" but never completed nor could cancel.
In a nuthshell, to successfully connect via RSYNC over SSH this must be done:

-Import the public key to the NAS that data will be transferred from or copied to. You may use this for reference:
(http://kb.netgear.com/app/answers/detail/a_id/12263/~/setting-up-rsync-over-ssh-(x86)#sync_remote)
-SSH services have to be started on each NAS and each share enabled for SSH access.
-Implement security for SSH for data to be as secure as possible
(Please note that ReadyNAS Pro series and ReadyNAS 300/500 use a different volume setting for data structure and when entering the paths to be backed up or copied to, this data structure must be followed.)

You can test your authentication settings for ssh communication by establishing an telnet session (putty.exe) to the first NAS and typing:

rsync -v root@host
Replace the host for the IP of the second NAS
If all settings are in order, you will get authenticated without password as the public key will be recognized.

There may be a bit more to it and may you have to create the public keys manually using "ssh-keygen -t dsa" command to create public keys for SSH version 2.0.
This requires a file created on the remote NAS to be named 'authorized_keys2'. The public and ssh-keygen keys content need to appended to the authorized_keys2 file.
Those files are located on the ~/.ssh folder of the NAS.
Just wish the rsync over ssh was a little more friendly to use as its powerful. I had to utilize this method as the readynas replicate just does not seem to work smoothly.


Hope this helps anyone as I've spent quite a few hours until finally got it done.
Contact me if you'd like more details

Good luck
Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 3665 views
  • 0 kudos
  • 2 in conversation
Announcements