This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have a replication job that had been running succesfully for years that is now failing. This job has over 320 Gb of data already replicated and I'm hoping I can keep all the already replicated data rather than have to restart the whole process again. I have created a new test replication job that only has a few files in it and it is replicating fine.
Here is the email log of the failure.
----------
**Please do not reply** Report for ISUL BC to Ottawa (FAILED)
Log:
[2017-10-07 18:16:07] [Info] Replicate version: 1.3.0 build R2 [2017-10-07 18:16:07] [Info] Starting backup job "ISUL BC to Ottawa" [2017-10-07 18:16:07] [Info] Locking target folder: /data/ISULReplicate/ISUL BC to Ottawa [2017-10-07 18:16:08] [Info] Resume folder is "/data/ISULReplicate/ISUL BC to Ottawa/2017-10-06 03-00/data" [2017-10-07 18:16:19] [Info] p2p connect to nas-36-B7-4C_L0ZjA in 6307655 network [2017-10-07 18:16:19] [Error] Unable to connect to nas-36-B7-4C_L0ZjA [2017-10-07 18:16:19] [Error] Connect error code: -501 [2017-10-07 18:16:19] [Error] Please check network connection between devices [2017-10-07 18:16:19] [Info] Rotate backups (1) [2017-10-07 18:16:20] [Info] Rotation marker is "2017-10-06 03-00" [2017-10-07 18:16:26] [Info] Unlock target folder: /data/ISULReplicate/ISUL BC to Ottawa [2017-10-07 18:16:26] [Info] Job finished
It does appear you are for some reason getting replicate error -501 where in it was working fine before. It does appear that you would like to preserve your old backup that was previously running and encountered the error. Please check this thread here that appear to be encountering the same problem.
It does appear you are for some reason getting replicate error -501 where in it was working fine before. It does appear that you would like to preserve your old backup that was previously running and encountered the error. Please check this thread here that appear to be encountering the same problem.
We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance. If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as solution so others can be confident in benefiting from the solution.
The Netgear community looks forward to hearing from you and being a helpful resource in the future!
Sorry for being so slow to respond, I just found some time to try the solution.
The solution worked perfectly. As an experiment I first tried to edit the replication job and that did not work. I then deleted the job and recreated it with the same name and directories and that worked perfectly. The replication is now working and all the previously replicated files did not need to be replicated again.
