NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RSYNC failure between two ReadyNAS (?)
I've added a 524x to my system for backup (was using an EDA500 off my 716) and am using rsync to do it per the instructions in the backup FAQ.
Most of my jobs set up with the backup manager work just fine. However, two of the larger ones fail with the following message in the logs.
Backup Job Name: HM Archives
Backup Job Type: Full
Protocol: rsync
Backup Source: [HM_Archives]//
Backup Destination: [remote:rsync]/192.168.1.29::HM_Archives
Backup Start Time: Wed Jun 12 2019 12:16:47 PM
Backup Finish Time: Wed Jun 12 2019 12:19:47 PM
Backup Status: Fail: Failure during copy.
Failed to run rsync, return rc 10
rsync: failed to connect to 192.168.1.29 (192.168.1.29): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(127) [sender=3.1.3]
Any thoughts?
Number of files?
Drive issues (SMART stats are clean)? But note I have 2 4TB Reds and 2 6TB Red Pros - rotation speed issues?
Thanks!
OK, the issue almost for sure is not using the actual IP address of the destination.
The backup manager will allow one to search for the destination NAS and will show its name (not IP address). This can be used to complete the parameters for the backup.
BUT as we've seen this apparently forces the NAS to periodically resolve the name and this can fail at any point in the backup.
Too bad, because if one is using dynamic addressing on one's local network the device addresses can change if one needs to reboot the local router. And this means going through all the backup jobs and changing the address (ugh!).
It would be simpler to resolve the name once and then store the value for the duration of the backup . . .
6 Replies
Replies have been turned off for this discussion
It shouldn't be related to number of files or certainly not rotation speed.
The first thing to check is whether rsync is enabled for the destination share(s).
Thanks StephanB
Yes, rsync (read and write) is enabled.
Curious thing is that I can restart the backup job and it completes. And if I start the job again - as in incremental job - it will complete again with no additional files copied.
I have not done a full compare of the two shares to make sure everything was copied completely and correctly . . . but am assuming that running the backup job a second time (as in incremental) checks this.
??
hmuessig wrote:
I have not done a full compare of the two shares to make sure everything was copied completely and correctly . . . but am assuming that running the backup job a second time (as in incremental) checks this.
Yes.
hmuessig wrote:
Curious thing is that I can restart the backup job and it completes. And if I start the job again - as in incremental job - it will complete again with no additional files copied.
It might be some other resource constraint. I've occasionally seen a failed (or stalled) rsync backup. Re-starting it always seems to fix it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
