NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rsync backup stopped working Feb 29th
I have 2 NAS. Older Sparc backs up using rsync from newer Ultra 2 Plus. There are 4-5 nightly backup jobs that run at 1am. The Sparc unit comes on and backs up and then shuts down at 4
It's been working like this happily for a long time.
Now all of a sudden, the backups are not working. First I got an email saying jobs were cancelled. I looked at the logs and cancelled the jobs as frontview showed them in progress but nothing was happening, but last night I got more errors for the 4 jobs. 3 said
One said
One job appeared to complete and the log for that shows
Note the Queued until 13:05:19. There was nothing to back up on that share.
Grep the log files for those delayed queues shows
So, frontview now shows that one job completed as above, but 3 jobs are 'In progress', but nothing is happening and the unit did not shut down.
So, it looks like it's Feb 29th related but that could be conicidence.
It's Raidiator 4.1.7
Any ideas
It's been working like this happily for a long time.
Now all of a sudden, the backups are not working. First I got an email saying jobs were cancelled. I looked at the logs and cancelled the jobs as frontview showed them in progress but nothing was happening, but last night I got more errors for the 4 jobs. 3 said
Error encountered copying data from remote source path xx.xx.xx.xx:documents ==> /documents/ due to unknown reason. Please see log.
One said
The backup job was cancelled.
One job appeared to complete and the log for that shows
INCREMENTAL Backup started. Sat Mar 3 01:05:15 EST 2012
Job: 004
Protocol: rsync
Source: xx.xx.xx.xx::other
Destination: [Other]/
Queued until: Sat Mar 3 13:05:19 EST 2012
receiving incremental file list
sent 33 bytes received 1209 bytes 99.36 bytes/sec
total size is 803888588 speedup is 647253.29
Backup finished. Sat Mar 3 13:05:31 EST 2012
Note the Queued until 13:05:19. There was nothing to back up on that share.
Grep the log files for those delayed queues shows
backup_002.log:Queued until: Wed Feb 29 13:10:15 EST 2012
backup_004.log:Queued until: Sat Mar 3 13:05:19 EST 2012
backup_004.log:Queued until: Wed Feb 29 13:05:24 EST 2012
backup_005.log:Queued until: Wed Feb 29 13:05:24 EST 2012
backup_007.log:Queued until: Wed Feb 29 13:05:24 EST 2012
So, frontview now shows that one job completed as above, but 3 jobs are 'In progress', but nothing is happening and the unit did not shut down.
So, it looks like it's Feb 29th related but that could be conicidence.
It's Raidiator 4.1.7
Any ideas
4 Replies
Replies have been turned off for this discussion
- I also use a duo and nv+ to backup my pro. Both are running 4.1.8, and rsync backups completed normally on the 29th.
Maybe try forcing a shutdown from the front panel?
edit - sparc systems running 4.1.8 StephenB wrote: I also use a duo and nv+ to backup my pro. Both are running 4.1.9, and rsync backups completed normally on the 29th.
Maybe try forcing a shutdown from the front panel?
I updated to latest Sparc f/w 4.1.8 and this morning at 7am, two job are In Queue and one is In Progress, but nothing is happening and there is nothing in ANY of the logs...- Maybe open an online support case?
StephenB wrote: Maybe open an online support case?
Did that, but not much help.
Anyway, I finally managed to reach a (temporary?) solution.
I had tried various reboots to no effect. Finally I read a couple of posts from ewok that said Jumbo Frames might be an issue. I set up a test backup job and tried it and noticed in syslog on the U2+Mar 8 06:57:50 surire rsyncd[3864]: building file list
Mar 8 07:13:30 surire rsyncd[3864]: rsync: read error: Connection timed out (110)
Mar 8 07:13:30 surire rsyncd[3864]: rsync error: error in rsync protocol data stream (code 12) at io.c(760) [sender=3.0.8]
and netstat on that box said there was no connection on port 873, whereas in the NV+ it had a TCPIP connection in ESTABLISHED state...???
So, I then- - Disabled jumbo frames on both NAS boxes and rebooted both and performed the test backup again and it worked.
- I then re-enabled JF on the U2+, rebooted and did the test backup and it worked
- I then re-enabled JF on the NV+, rebooted and did the test backup and it worked
so, back to the state where both machines have JF enabled and rsync now works again - at least on the test backup. Let's see what happens tonight.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
