readydr job failure: protocol error

---

Retired_Member wrote:

ReadyDR needs ports(80,443,5253) 

---

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.