NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Duo Backup using Rsync doesn't react
Hi,
I have some troubles with my Duo running Sparc firmware 4.1.13
I try to make backups to another NAS over the internet using the in the frontview available options. We use the Rsync protocol. If I test the connection all is fine. For some reason the backup does not seem to transfer files.
Timeline.
- For some years all was fine running 4.1.9. I did do incremental backups using Rsync.
- Last oktober my Nas gone down... For some reason.. (another thread http://www.readynas.com/forum/viewtopic.php?f=23&t=77995)
- I did a complete new fresh start (by putting in an empty disk) and used the oppertunity to update to 4.1.13
- I was able te recover the data from one disk using a Linux PC and copied all data to my second, empty disk wich I placed in the NAS
Now before I put the second disk in, I want to be sure I have a complete backup, but this seems not to work.
- I recreated the Backup-Tasks and checked the connections, all fine
- I started the task 001
- I installed nTop to check the data troughput, wich was extreme low. Only 10 to 20mb per hour. I was used to something about 1gig per hour
- I tried to check the log (Icon besides the running task). It says "opening logs..." but nothing shows up
- I tried to cancel the task. It does not. It takes ages. I switched of the NAS using the frontview option shutdown and restart.
- I tried again, let the task run for several days but no sigar. Same behaviour....
Who can help me?
Oh, We checked the "other" side, but no changes where made there during the last functioning backups about 1.5 months ago... I downloaded a complete Log about one hour ago if it is helpfull I can sent it.
Any idears?? Regards,
Mark
I have some troubles with my Duo running Sparc firmware 4.1.13
I try to make backups to another NAS over the internet using the in the frontview available options. We use the Rsync protocol. If I test the connection all is fine. For some reason the backup does not seem to transfer files.
Timeline.
- For some years all was fine running 4.1.9. I did do incremental backups using Rsync.
- Last oktober my Nas gone down... For some reason.. (another thread http://www.readynas.com/forum/viewtopic.php?f=23&t=77995)
- I did a complete new fresh start (by putting in an empty disk) and used the oppertunity to update to 4.1.13
- I was able te recover the data from one disk using a Linux PC and copied all data to my second, empty disk wich I placed in the NAS
Now before I put the second disk in, I want to be sure I have a complete backup, but this seems not to work.
- I recreated the Backup-Tasks and checked the connections, all fine
- I started the task 001
- I installed nTop to check the data troughput, wich was extreme low. Only 10 to 20mb per hour. I was used to something about 1gig per hour
- I tried to check the log (Icon besides the running task). It says "opening logs..." but nothing shows up
- I tried to cancel the task. It does not. It takes ages. I switched of the NAS using the frontview option shutdown and restart.
- I tried again, let the task run for several days but no sigar. Same behaviour....
Who can help me?
Oh, We checked the "other" side, but no changes where made there during the last functioning backups about 1.5 months ago... I downloaded a complete Log about one hour ago if it is helpfull I can sent it.
Any idears?? Regards,
Mark
6 Replies
Replies have been turned off for this discussion
- Hi,
I am still confused why it is not working. To explain a bit more I created a few screenshots.
So I have two tasks.
Task 1 is one which schould backup all files in a share. Here is the test done by hand in a terminal sesion:
The job starts. This is what I did in frontview:
Task 2 is slightly different as it has to backup alle files in a subfolder of a share. Again the test by hand in a terminal sesion:
Again the job starts. So this is what I did in frontview:
In both cases I have the behaviour like above:
- Check connection says OK
- No error messages
- No data in the log
- Job can't be canceled without restarting the NAS
What do I do wrong?? Is there a limited length of the password using the frontview settings?
Thanks in advance
Mark - Maybe try using top with the command line toggle (with the backup job running) so you can see how the backup job command line compares with the terminal session?
You are not using the rsync over ssh add-on correct? - For the source try the Pad "/Fotos" (no quotes)
For the destination try "/BackupMark/fotos/" (no quotes)
You got the slashes the wrong way around in the destination. In Linux \ is used to e.g. escape a space. StephenB wrote: Maybe try using top with the command line toggle (with the backup job running) so you can see how the backup job command line compares with the terminal session?
How do I do that??
I checked after I started the job with a terminal session using TOP if I saw a process called rsync. I don't see it...StephenB wrote: You are not using the rsync over ssh add-on correct?
No I'm not. What is the "big" advantage? Safety, but why and how.mdgm wrote: You got the slashes the wrong way around in the destination. In Linux \ is used to e.g. escape a space.
I wonderd that. I noticed the difference ofcourse. But giving your suggestion as destination ("/BackupMark/fotos/") it says "unkown path" . With the \ in stead of / it says "connection OK"
But after playing around I aslo tested "BackupMark/fotos/" so without the first forward slash. Than frontview says the connection is OK aswell.
Well the result is what I was looking for. Now I see the proces running in TOP and the log files contain data.. :)
So thanks a lot.
Mark- So It's isn't completely solved.
Backup is running on a schedual. First time I did a complete backup wich was succesfull.
Now the first one, incremental with new data gives an errorrsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Connection timed out (60)
rsync: connection unexpectedly closed (3731 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
Itried to search the internet but I can't find a reason for such a message. Can anone help??
Grz
Mark
If you enter a "c" when top is running (lower case) it will toggle between showing you the command name and the full command line. It's best if you also make the terminal window full screen before you run top.SliceTheAir wrote: StephenB wrote: Maybe try using top with the command line toggle (with the backup job running) so you can see how the backup job command line compares with the terminal session?
How do I do that??
Normal rsync is not secure - the data is sent unencrypted. Running over ssh results in the data being encrypted. There is a security downside - exposing ssh potentially allows someone access to the destination machine if they can guess the user credentials. So you'd want a strong passwords (which is a good idea in any case).SliceTheAir wrote: StephenB wrote: You are not using the rsync over ssh add-on correct?
No I'm not. What is the "big" advantage? Safety, but why and how.SliceTheAir wrote:
Now the first one, incremental with new data gives an errorrsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Connection timed out (60)
rsync: connection unexpectedly closed (3731 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
I'm not certain, but this may be a bug in the rsync server (on the destination machine). https://bugs.launchpad.net/ubuntu/+sour ... bug/988144
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
