Source & Destination ReadyNAS are in different locations and ReadyDR replicates over an Internet connection. ReadyDR Job is configured and can successfully connect to destination ReadyNAS and create ReadyDR Snapshot Share. Job fails with ReadyDR Job Failure: Protocol Error. Have searched online and can't find information about cause or correction.
Model: RN424| ReadyNAS 424 4-Bay with up to 40 TB total storage
How do you connect both devices on internet? ReadyDR needs ports(80,443,5253) open on destination device if the NAS is behind of router.if you use VPN to connect both devices then we need to check the log to determine the issue(email to:nsbu_logs@netgear.com)
The FAQ only says 5253 ( https://kb.netgear.com/31224/ReadyDR-FAQ ) If you're certain it needs the http/https ports forwarded, can you request that the FAQ be updated?
FWIW, I think that requiring http/https to be forwarded would be a non-starter for lots of folks, as it opens up the possibility of someone gaining administrative access to the NAS over the internet. Also, it prevents http/https from being used to reach another server.
. Connection is not an issue. Port Forwarding has been setup and the two devices connect. A ReadyDR has been setup and will begin the transfer process. After some period of time, hours or days, the job will fail with eitehr an input/output error or a protocol error. This is the first protocol error received. Have done the internet searches and little or no information about this error, cause, or correction.
I have been using Ready Replicate for years and it works very well. In this case a Ready Replicate job will complete in about in about 10 hours; approx 125GB. The same data using ReadyDR so far has been running for 36 hours and transferred 62GB of data. Have tried going thru a VPN as well and job takes just as long if not longer considering VPN overhead on abndwidth. In addition ReadyDR is difficult to setup with incomplete documentation. Have worked with tier 2/3 support on two different occasions for days to get jobs setup. I now have ReadyDR setup and running on 2 of 3 customers and beginning setup/testing of the 3rd.
The source ReadyNAS is being used as storage for backup jobs instead of tape. The destination ReadyNAS is being used as offsite backup storage for DR; to replace taking a tape offsite. Ready Replicate performed this service well. The rate of transfer using ReadyDR makes using it very inefficient.
ReadyDR needs port 443 open to authenticate with remote device for uploading ReadyDR key,port 5253 is for data transferring,port 80 is not needed for ReadyDR(my mistake in previous reply)
I received a message from Netgear accepting this as the solution, Below is my reply.
This is NOT the solution and in addition I did not get an answer to the basic initial question – What is a Protocol Error?
I have worked on ReadyDR with Tier 2 & Tier 3 support for extended periods of time. You do NOT need ports 80 & 443 open or NATing to connect devices. I have 3 ReadyNAS Source devices connecting thru a common firewall/router to 3 internal Destination ReadyNAS devices without opening or NATing these ports. Only using ports 5253 and SSH 21/22.
Port 5253 seems to be the ONLY port that the source ReadyNAS will use; even though you can manually set a port in the ReadyDR Job setup. With Tier 3 support we setup the 3 Source ReadyNAS devices ReadyDR Jobs using ports 5253, 5254, and 5255. We then setup the destination firewall/router with 3 NAT rules to forward traffic from these ports to a specific Destination ReadyNAS. In ALL attempts traffic was only routed the Destination ReadyNAS that was using port 5253. In setting up the ReadyDR job on each Source ReadyNAS devices the connection to the Destination ReadyNAS could be established, and the Snapshot Share could be created, but always on the Destination ReadyNAS that was using port 5253.
Here is the work around I found to allow this to work. I use a Sonicwall TZ300 firewall/router so could be difficult to setup on other routers.
All Source & Destination ReadyNAS devices ReadyDR Job are configured to use port 5253.
Separate NAT Policy created for each of Destination ReadyNAS devices – all set to route port 5253 to the appropriate IP address for each Destination ReadyNAS.
In the NAT Policy configuration the “Original Source” was set using the static WAN IP of the Source ReadyNAS.
Effectively routing inbound port 5253 traffic – from a specific WAN IP – to a specific individual Destination ReadyNAS IP
After setting up the configuration detailed in item 3 I was able to create the ReadyDR Jobs and this last weekend was able to perform my first complete ReadyDR replication from all 3 Source ReadyNAS devices.
In working with Tier 3 support they concurred that all ReadyNAS devices were sending traffic on port 5253 regardless of the ReadyDR Job configuration port setting. I also validated with them the workaround detailed in item 3. Tier 3 support was submitting the port 5253 issue for further consideration.
In regards to the excessive time for the ReadyDR Job to run I found my Source ReadyNAS connected to a network switch 3 levels down from the “Parent” switch. Reconfigured the network cabling to connect the Source ReadyNAS directly to the top level switch speed increased from around 150kbs to approximately 1.2mbps.
