(Please do not tell me to contact support. They are thoroughly unhelpful.)
I recently purchased a second ReadyNAS RN102. Both ReadyNAS RN 102's are running on OS 6.6.0 and are on the same network.
I enabled ReadyNAS Replicate on both devices and registered them with the same ReadyNAS Replicate account. Both have static IP addresses, are a part of the same DNS server with 8.8.8.8 added as alternative DNS's, and IPv6 is disabled completely.
Eventually, I want to be able to move one of these devices to another location, but still have them replicate to each other.
When I create a job that is supposed to replicate some data (a small amount for test purposes) from one ReadyNAS to the other (and vice versa), I receive the below error in an email message stating, "Connect error code: -51". What is this error and how can I fix it?
[2016-11-10 12:11:35] [Info] Replicate version: 1.3.0 build R2 [2016-11-10 12:11:35] [Info] Starting backup job "Data Backup [2016-11-10 11h 41m AM]" [2016-11-10 12:11:35] [Info] Locking target folder: /data/Replicate-Test/Data Backup [2016-11-10 11h 41m AM] [2016-11-10 12:11:36] [Info] Resume folder is "/data/Replicate-Test/Data Backup [2016-11-10 11h 41m AM]/2016-11-10 11-42 (failed)/data" [2016-11-10 12:11:36] [Warning] Incremental not possible [2016-11-10 12:11:36] [Info] p2p connect to nas-xx-xx-06 in xxxxxxxx network [2016-11-10 12:11:59] [Info] p2p connect to nas-xx-xx-06 in xxxxxxxx network [2016-11-10 12:12:12] [Error] Unable to connect to nas-xx-xx-06 [2016-11-10 12:12:12] [Error] Connect error code: -51 [2016-11-10 12:12:12] [Error] Please check source device is online and Replicate service is running [2016-11-10 12:12:12] [Info] Unlock target folder: /data/Replicate-Test/Data Backup [2016-11-10 11h 41m AM] [2016-11-10 12:12:12] [Info] Job finished
Model: RN10200|ReadyNAS 100 Series 2- Bay (Diskless)
@StephenB How would I test this? I know that when I shut down or disconnect either NAS the ReadyNAS Replicate icon representing the ReadyNAS that is no longer connected states that it is disconnection. Correct me if I'm wrong, but I'm assuming that means the devices are connected if there isn't that error message?
Model: RN10200|ReadyNAS 100 Series 2- Bay (Diskless)
but I'm assuming that means the devices are connected if there isn't that error message?
Probably it does.
You can independently check that the NAS can reach the internet by trying to install an app. Pick something simple (AV plus perhaps), and remove it after it installs.
I suspected that, but thought it was worth checking before you go crazy with more esoteric possibilities.
My backups are all local (other than CrashPlan) so I just use rsync. Replicate is on my list to set up, but likely you'll get this figured out before then.
Hopefully some Netgear folks will chime in with suggestions.
Check the Internet connectivity and service connectivity on both sides.
ReadyNAS OS 6. ReadyNAS Remote should be enabled on both sides.
For restrictive firewalls and more complex networks, consider setting up port forwarding. (port 6300).
Remove Replicate user binding and re-add the NASes to the Replicate account. Then, recreate the backups. Use the “resume from…” option to avoid having to send all of the data again.
@mdgm-ntgr How would I look for that? I have SSH'ed into the system but I'm not familiar with linux systems, so if you could direct me with the path and commands to use to view this file, that would be excellent.
@mdgm-ntgr How would I look for that? I have SSH'ed into the system but I'm not familiar with linux systems, so if you could direct me with the path and commands to use to view this file, that would be excellent.
Download the log zip file from the web ui, it's in there.
@mdgm-ntgr My most recently purchased ReadyNAS has:
[2016/09/09 19:13:03] Factory default initiated by RAIDar (format used disks)! [2016/09/09 19:13:06] Defaulting to X-RAID2 mode, RAID level 1 [2016/09/09 19:13:29] Factory default initiated on ReadyNASOS 6.0.8. [2016/09/09 19:13:31] Factory default initiated by Frontview! [2016/09/09 11:38:33] Updated from ReadyNASOS 6.0.8 () to 6.2.5 (ReadyNASOS). [2016/09/09 11:51:24] Updated from ReadyNASOS 6.2.5 (ReadyNASOS) to 6.5.1 (ReadyNASOS). [2016/09/20 10:50:35] Updated from ReadyNASOS 6.5.1 (ReadyNASOS) to 6.5.2 (ReadyNASOS). [2016/10/06 15:31:19] Updated from ReadyNASOS 6.5.2 (ReadyNASOS) to 6.6.0 (ReadyNASOS). [2016/10/31 07:49:08] Updated from ReadyNASOS 6.6.0 (ReadyNASOS) to 6.6.0 (ReadyNASOS).
And my older ReadyNAS has:
[2013/09/13 02:45:24] Factory default initiated due to new disks (no RAID, no partitions)! [2013/09/13 02:45:29] Defaulting to X-RAID2 mode, RAID level 1 [2013/09/13 02:45:57] Factory default initiated on ReadyNASOS . [2013/09/12 19:33:50] Updated from ReadyNASOS 6.0.0 to 6.1.2. [2014/01/01 10:02:24] Updated from ReadyNASOS 6.1.2 to 6.1.5. [2014/02/24 08:31:51] Updated from ReadyNASOS 6.1.5 to 6.1.6. [2016/02/15 18:57:31] Updated from ReadyNASOS 6.1.6 () to 6.2.5 (ReadyNASOS). [2016/02/15 19:08:41] Updated from ReadyNASOS 6.2.5 (ReadyNASOS) to 6.4.2 (ReadyNASOS). [2016/10/07 14:08:07] Updated from ReadyNASOS 6.4.2 (ReadyNASOS) to 6.6.0 (ReadyNASOS). [2016/11/03 08:20:34] Updated from ReadyNASOS 6.6.0 (ReadyNASOS) to 6.6.0 (ReadyNASOS).
Let me know if you need anything else. I was told there may be something wrong with a config file but no one seems to want to offer any assistance on that. It would be nice if you would give me a specific issue it may have and a few troubleshooting steps.
