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 thi...
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:
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.
There would be about 3.5TB free after the backup was complete (8TB total free on both devices, about 4.5TB used on the main NAS). My largest share is around 4TB, so twice the size of your largest.
Going forward I can't really re-organise the contents of the share as they are set up in a particular way for another application, but I suppose I could do it temporarily for testing purposes. I'll start with the file that killed it last time on it's own and see if that works.
I could use Free File Sync instead of RSync of course, but that's what I'd been doing my backups with upto now and the whole point of buying another NAS was to take the PC out of the loop, increase automation and reduce power requirements (by having the backup NAS sleep unless it was actively backing up).
It will be interesting to see if the subsequent backup jobs complete properly, as this one is only the first of about half-a-dozen (one per share) that were scheduled. The jobs themselves are running on the backup NAS (the RN104).
daKlone wrote:
Going forward I can't really re-organise the contents of the share as they are set up in a particular way for another application, but I suppose I could do it temporarily for testing purposes. I'll start with the file that killed it last time on it's own and see if that works.
If you know what file killed it last time, then you can simply try copying that. I was thinking about re-organizing just to help you isolate it.
daKlone wrote:
...the whole point of buying another NAS was to take the PC out of the loop, increase automation and reduce power requirements (by having the backup NAS sleep unless it was actively backing up)...The jobs themselves are running on the backup NAS (the RN104).
Yes, and that should work. I also run the jobs on the backup NAS.
What is the main NAS? (it doesn't matter if it is netgear or not btw).
StephenB wrote:If you know what file killed it last time, then you can simply try copying that. I was thinking about re-organizing just to help you isolate it.
Well, I don't know that it was that particular file for sure, just that it failed while working on a particular file and that the previous attempt failed at around the same duration, so it could have been the same one that caused the problem last time.
StephenB wrote:What is the main NAS? (it doesn't matter if it is netgear or not btw).
The backup jobs are pulling data from an RN314 (main NAS) to an RN104 (backup NAS) on the same network.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
