NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Replicate SLOW on initial replication
Folks, I'm new to Replicate and have done a few test runs with it. I am finding it really SLOW in terms of replicating files between 2 servers, RN314 and RN316, both connected to my LAN. Both are ...
Let me close out this post and confirm that my attempt to plug double LAN cables into an unmanaged switch without bonding protocols caused this dramatic slowdown in Replicate performance. I had an extended call with Netgear technical support on this topic this morning and the Level 2 tech rep explained in detail what happens when two LAN cables are attached to each NIC port on the ReadyNAS. Refer to this article for more info ... http://kb.netgear.com/app/answers/detail/a_id/23076/~/what-are-bonded-adapters-and-how-do-they-work-with-my-readynas-os-6-storage
I've removed double cables on all of my boxes and all are operating as anticipated.
This item is now closed.
Hi,
rclementtx wrote:Connection Method 4
Using relayed connection; Consider using port forwarding
I'm presuming that the replication process is acting as if my 2 boxes are at remote locations vs. being on the same network, and thus all transfers are taking place thru ReadyNAS servers vs being within my LAN.
That's right, it means that a direct P2P connection could not be established between both NASes and that NETGEAR's Replicate Server has to relay the data between both NASes. So yeah, that's gonna be slow. In your case, you should see something like "Using LAN connection".
To narrow down the source of the issue, could you make sure that there is no Firewall policies blocking traffic for these two NASes? This is othen related to Firewall.
Or ACLs on your switch? Is the switch a dumb switch, ProSage Plus, Smart switch?
Could you try to temporarilly add Firewall exceptions to completely allow outbound traffic (allow inbound, but no port forwarding - don't overlook security even when troubleshooting), & make sure there are no ACLs.
In case, they're not far from each other, you could also try to connect both switches to the same dumb switch, to confirm it's not related to the switch.
Ultimately, you can try a packet capture on Wireshark (and port mirroring) to see if you're missing packets somewhere.
rclementtx wrote:(with 1GB connection LEDs enabled
I presume you mean 1Gbps (it might sound obvious, but it makes a big difference :D)
Thanks for the response. You are tossing around abbreviations that are a bit beyond me ... so here's what I've done - completely turned off the firewall in the Router to the point were inbound policy and outbound policy were both "accept".
Then ran my sample replicate job again. Extract of the report showed same situation ...
[2016-05-16 15:31:18] [Info] Resume folder is "/data/Replicate_AG_Houston/Test 314 to 316/2016-05-16 14-58/data"
[2016-05-16 15:31:19] [Info] p2p connect to nas-E6-85-36_dcXQQ in 11681505 network
[2016-05-16 15:31:57] [Info] Connection method: 4
[2016-05-16 15:31:57] [Warning] Using a relayed connection, consider setting up port forwarding
[2016-05-16 15:31:57] [Info] LAN connection not available
[2016-05-16 15:31:57] [Info] Using p2p connection
Then checked following windows under Firewall on Router
"Access Control" options on Firewall page - (Block access to internet services) - no devices identified.
"Port Forwarding" page - have port forwarding rules in place for ReadyNas Photo II in place - 2 for one NAS / 1 for the other - opening ports 10001-10003
"DMZ Host" page - "allow single networked device to be fully exposed to internet" - no IP numbers listed
"Port triggering" - 2 entries as follows
ProtocolOutgoing Trigger PortsIncoming Ports to OpenAction
L2TP Triggering - Layer Two Tunneling Protocol UDP Any -> 1701UDP Any -> Same as Initiating Ports
TFTP Triggering - Trivial File Transfer Protocol UDP 1024-65535 -> 69UDP Any -> Same as Initiating Ports
Static NAT and Advanced Filtering - no entries in place.
Suggestions?
By the way - dumb, unmanaged switch in place. Therefore no policies on it that should preclude port to port communication
Just tried an experiment - seems to have worked. I had dual LAN cables plugged into each of the LAN ports on each NAS. Removed one cable per box so that only one connection existed. Appear to have set up local connection as a result.
[2016-05-16 16:06:28] [Info] p2p connect to nas-E6-85-36_dcXQQ in 11681505 network
[2016-05-16 16:06:31] [Info] Connection method: 2
[2016-05-16 16:06:31] [Info] LAN connection available
[2016-05-16 16:06:31] [Info] Get LAN credentials
Will try more extensive replicate action now that I appear to have LAN communications and advise of results.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
