rsyn with SSH pushed from another offsite NAS

Oh, also, I just got some instruction from the Qnap support.
I downloaded putty.exe and tried to connect to the Ultra on port 22.
It failed, indicating there is no SSH service enabled on the Ultra, according to him.
So... how to enable?

Install this add-on (via Add-Ons > Add New in Frontview): http://www.readynas.com/?p=4203

Put the ssh key from the QNAP on the Ultra and run the backup job on the QNAP.

I think the above should work.

http://www.readynas.com/?p=4203 will enable ssh for putty.

To enable rsync over an ssh tunnel on the ultra, you might need to try this: http://readynasxtras.com/readynas-x86-a ... nabler-x86

In the pro line, Netgear builds this feature into frontview, but not for the ultra (which is considered a home product).

The Rsync over SSH Enabler may be better. If you install EnableRootSSH and forward to port 22 on the NAS you will want to make sure you have setup a strong root password.

Forwarding port 22 with root access enabled in the NAS means that anyone on the internet can reach the box - and if they guess your password, will have full access.

So I agree with mdgm - if you do need EnableRootSSH, you will want to ensure that you maintain a strong password.

Astonishing that this is considered a pro feature.
One of the things I want to do is backup my family photos offsite in case my house burns down. The notion that I would want to make photos of my kids and other personal documents available to anyone through an unencrypted transfer just because I'm not a pro....Jeeeez Netgear!

Anyway, I'll give what you've suggested a try. Many thanks.

I am using a competitor's NAS product. On all of their models SSH and rsync are available. As all these NAS devices, no matter which brand, run on some Linux-derivative, I guess my experience should be transferable to your problem.

Concerning SSH port 22, I was pretty shocked when I opened it, within hours, failed login attempts started to mushroom and the NAS blocked more and more IPs from which these login attempts originated. I traced the IPs back and most of these were located in China, Russia or some Arab countries. Can't tell if the people controlling these computers were in fact located there, however, there seems to be a security issue emanating from certain regions.

My solution and what remedied the problem in respect to SSH break in attempts was that I simply changed the SSH port to a different/non-standard one. A year passed since I made that change and ever since my NAS did not block a single IP although it is running 24/7 and reachable via a dynamic host name.

Concerning your backup problem, I wrote a script exactly for the purpose of doing offsite backups over the internet with rsync and SSH. As network disruptions can be a serious issue for rsync, my script basically restarts rsync, whenever it fails to complete the synchronization. Upon completion the script either sends an email or displays a growl notification on my Mac's desktop. Each backup job is stored in a small configuration file which is fed to the script (this is also helpful in that you don't have to learn about the different rsync parameters). It is possible to set backup intervals, split up big backup tasks into smaller folder jobs and also to create a backup history by transferring the backup into a dated folder upon each run.

By adding the backup jobs to cron, they run in the background according to a predefined schedule without needing any further user attention.

I would like to share this script, which I called Space Machine :wink:, on my blog: http://goo.gl/d3VKd

I hope this is helpful. If you like the script, I would be happy if you could leave a short post on my site.