I have a network with many ReadyNAS devices at each of multiple sites. Most of them are ReadyNAS 312's, but there is one older ReadyNAS 102.
The RN312's maintain a duplicate of each others critical data using ReadyDR, which provides local access to each site to other sites data.
The RN102 doesnt support ReadyDR so I have been using an RSYNC over SSH. This all works swimmingly well... until one of the sites the RN102 backs up to goes offline part way throught an RSYNC. Each time that happens, the RN102 becomes unresponsive. You cannot connect to it over the file shares, you cannot connect to it over the admin interface and you cannot gracefully shut it down with the power button on the front of the unit. The only way I've found to restore service is to pull the power out of the back of the device. The device has mirrored harddisks, which then need to resync each time it reboots after the power has been disconnected which takes about 12 hours before eveything settles down again. Needless to say, it is quite a remote location and although the drive is pleasant, it's getting rather annoying.
My configuration settings for the transfer are Source:
Running SSH over a VPN would be just plain stupid. That would be running encryption over encryption which would result in an exceptionally large amount of processing overhead on and already weakly powered CPU and performance degredation because you cant effectively encrypt something that is already encrypted.
Running SSH over a VPN would be just plain stupid.
I was thinking you could try logging in with ssh when it goes non-responsive, and use the linux CLI to see what is going on with the NAS.
You could of course just use port forwarding, but that exposes you to brute-force password attacks. So I suggested a VPN to eliminate that possible threat..
