NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RSync Backup Failed...Why?
I'm having trouble getting a backup job to run to completion. I've run it twice so far and it has failed both times, sadly I didn't record the error message for the first one, but this time I got this in the main log:
Tue Aug 2 2016 5:57:57 Backup: Error backup job Weekly Backup - Videos: failure during copy.
And this in the backup job's log:
Backup Job Name: Weekly Backup - Videos
Backup Job Type: Full
Protocol: rsync
Backup Source: [remote:rsync]/192.168.0.200::Videos
Backup Destination: [Videos]//
Backup Start Time: Mon Aug 1 2016 1:05:03
Backup Finish Time: Tue Aug 2 2016 5:57:57
Backup Status: Fail: failure during copy.
Failed to run rsync, return rc 2560 (10)
'rsync' command returns rc=2560
<list of files>
rsync: [generator] write error: Connection reset by peer (104)
rsync error: error in socket IO (code 10) at io.c(820) [generator=3.1.1]
rsync error: received SIGUSR1 (code 19) at main.c(1434) [receiver=3.1.1]
Can anyone tell me what's actually gone wrong please?
Well, the news is finally good! :smileyhappy:
I ran a scrub on the main NAS (which took ages!) and waited for the backup jobs to run on Sunday night. They all ran (incrementally) to completion and I double-checked the folders using FreeFileSync and they are indeed identical.
I call that a win.
Thanks everyone for thier help, it's much appreciated :smileyhappy:
11 Replies
Replies have been turned off for this discussion
I had simular problems with setting up rsync on my 104 and 314... Check the slashes/backslashes of the rsync command. I.e. the numer of slashes at the end of source / targets dirs.
daKlone wrote:
Backup Destination: [Videos]//
Normally would be just one / here, not two. That is, share: Videos in the name field with path blank.
But the backup ran for 29 hours before failing, correct? So it is unlikely to be a syntax error, that would fail right away.
Did it run about the same amount of time on the first backup run? I'm wondering if it failed on the same file.
I tend to agree with StephenB - if there were a command syntax error then the backup wouldn't have run at all. I will double-check it though.
It did fail at about the same duration when I tried to run it the first time, so it is possible that the same file has "killed" it.
I had another thought along those lines. Is there a limit on the number of files that can be sync'd, or a limit on the size of an individual file?
That folder contains a lot of files, and one or two are really big (~40GB) so it is possible that either a) there are too many files to enumerate (unlikely), or b) it bombs out when it hits the first really big file.
What do you think?
I did a factory reset on both my RN102 and RN202 (backup NAS) a couple months ago, and repopulated the data using RSYNC backup from my main NAS (pro-6). This was done share-by-share.
-biggest share is about 2 TB
-share with highest file count has 280K files
-several files bigger than 40 GB, the largest about 65 GB
So I'm thinking its not that likely to be a problem with size or enumeration.
How much free space would be on the destination NAS if the backup completed successfully?
One option is to focus on the source - checking the disk, or (if RAID) doing a scrub. Maybe resetting file permissions (though that should have given a different error).
Another approach is to organize the source into a few folders, and try using rsync to copy them them folder at a time. The idea there is to the problem down to the problem file.
You could even try a drag/drop from a PC, telling the PC to skip files that are already on the destination. That only makes sense if the bulk of the data was successfully transfered.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
