Re: Replicate error: Unable to connect to non-participating unit

replicant · ‎2015-12-02

Hi,

We have three units and one daily data replication job from Unit1 to Unit2. Now I am trying to start an additional Replicate job from Unit1 to Unit3, on their LAN. All three units appear in the 'Monitor' panel:

When I click the 'run now this instance' icon in the 'Monitor' panel, to start that additional job, it soon fails and reports the error 'unable to connect to [Unit2]. That is, the non-participating unit:

[2015-12-02 05:26:20] [Info] Replicate version: 1.2.1 build R1
[2015-12-02 05:26:20] [Info] Starting backup job "Filecentral EveDATA Replication"
[2015-12-02 05:26:20] [Info] Create target folder: /c/Replications/Filecentral EveDATA Replication
[2015-12-02 05:26:20] [Info] Locking target folder: /c/Replications/Filecentral EveDATA Replication
[2015-12-02 05:26:21] [Info] Making full backup
[2015-12-02 05:26:21] [Info] p2p connect to DANNY in 8818639 network
[2015-12-02 05:29:47] [Error] Unable to connect to DANNY
[2015-12-02 05:29:47] [Error] Connect error code: -50
[2015-12-02 05:29:47] [Info] Unlock target folder: /c/Replications/Filecentral EveDATA Replication
[2015-12-02 05:29:47] [Info] Job finished

Immediately afterwards, I tried to 'run now this instance' the replication job from Unit1 to Unit2, successfully. But re-running that Unit1 to Unit3 job, again gives the same 'unable to connect to Unit2' error. That job should be unaware of even the existence of a Unit2, right?

So what's going on here?! How to sort this out?

Thanks,

replicant

BrianL2 · ‎2015-12-02

Hi replicant,

Can you confirm if this replicate backup (unit1 to unit2) is working before? Consider doing the following:

* For restrictive firewalls and more complex networks, consider setting up port forwarding.

* On unit2, remove Replicate user binded and re-add the NAS to the Replicate account. Then, recreate the backup and try it again.

Kind regards,

BrianL
NETGEAR Community Team

replicant · ‎2015-12-03

Hi BrianL,

Yes, the Unit1-to-Unit2 replicate job has been working since May and automatically completed another incremental backup this morning. I also had a Unit1-to-Unit3 job working for three years until it started failing Sep3 and never recovered. I figured the incremental backups had overwhelmed the filesystem of Unit3 (Duo v.2). So I reset it to factory default, re-installed Replicate, re-registered it (with you guys' help) and created the Unit1-to-Unit3 job that now complains 'unable to connect to Unit2'.

Regarding your suggestions below, we have no firewall issues: the LAN of units 1 and 3 has always been on plain-vanilla DHCP / NAT behind a cable modem. No reason to set up port forwarding. To 'remove Replicate user binded', I guess means to delete it from the 'Network' panel, right? But if I remove Unit2 in that way, wouldn't that permanently disable use of the (currently working) Unit1-to-Unit2 backup? Would we risk recovery in case something happens to production Unit1 while we are solving this problem (which should only involve 1 and 3)?

One more thing: back in 2012, Capone helped us sort through problems about serial numbers and license keys that originated when we switched unit 1 and 2 and their names. Could today's problem still be some kind of leftover from that fix three years ago?

Thanks again,

replicant