NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Backups failing
I have a 2100 running RAIDiator 4.2.21. On the system I have 5 jobs configured running backups from my Linux Server. Linux server is running CentOS 5.4. I have 3 of the 5 jobs running successfully.
The log simply says:
Same error log from Job 5 that is failing. Issue is that my other 3 jobs all succeed with the exact same information in the configuration. They all run rsync using root permissions, the data and home backups are / files just like z and etc.
Configs for Step 1:
I have typed and retyped the password to make sure it is correct. At this point I am unsure why I can't get these jobs to run correctly. Any assistance would be helpful.
The log simply says:
INCREMENTAL Backup started. Mon Dec 17 05:38:54 MST 2012
Job: 003
Protocol: rsync
Source: 192.168.1.10::z
Destination: [xxxx]/
@ERROR: access denied to z from unknown (192.168.1.13)
rsync error: error starting client-server protocol (code 5) at main.c(1534) [Receiver=3.0.9]
Backup failed. Mon Dec 17 05:38:55 MST 2012.
Reason for failure:
Error encountered copying data from remote source path 192.168.1.10::z ==> /xxxx/ due to unknown reason. Please see log.
Same error log from Job 5 that is failing. Issue is that my other 3 jobs all succeed with the exact same information in the configuration. They all run rsync using root permissions, the data and home backups are / files just like z and etc.
Configs for Step 1:
I have typed and retyped the password to make sure it is correct. At this point I am unsure why I can't get these jobs to run correctly. Any assistance would be helpful.
5 Replies
@ERROR: access denied to z from unknown (192.168.1.13)
I'm not sure, but this sounds like the problem is that rsync doesn't have permission to access the destination (meaning that this is perhaps not an issue with the backup source). What device is 192.168.1.13? Is it the local NAS?- Yes the NAS is the 192.168.1.13 my server is 192.168.1.10. I saw that, but that's why I mentioned that my other 3 jobs (same source and destination) all succeed where these two jobs fail. So why the other 3 jobs have permission and these 2 don't is frustrating.
- I think the place to start is to look at the permissions and ownership of the destination folders.
- You may have hit the nail on the head with that one Stephen! My owner/group are both default Nobody/nogroup on the two that are failing. On the 3 that are successful they are both set to root/root. I started to test it and my shares disappeared, so a bigger issue there. Just ran a restart though. Hope it was just a frontview glitch....
EDIT: Restart resolved the disappearing shares deal. Unfortunately changing Owner and Group did not solve the issue, so back to the drawing board, Any other ideas? :cry: - Anyone else have this same issue and have been able to resolve it? Unfortunately it looks like the issue may lay in some odd permissions issues on the server for access to these two particular files. I hope to find a solution.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
