NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jhaines
Aug 31, 2012Follower
Intermittent failure with WOL, backup to remote Rsync server
PC: WinXP SP3 with DeltaCopy 1.3 providing the Rsync server.
ReadyNAS: Pro 2, RAIDiator 4.2.19
Both are connected locally on the same subnet.
I have a job configured to backup a ReadyNAS share to a PC using the PC as Rsync server and with the backup job configured to send a WOL packet to the PC. When the PC is awake, the backup job runs reliably every time. When the PC is initially in standby mode, the backup job reliably wakes the PC with the WOL packet, but the backup job sometimes fails "due to unknown reason".
I've a suspicion that the there's insufficient time for the PC to wake reliably from standby between the WOL packet being received and the rsync beginning execution.
Can anyone tell me please:
1. How long is the time allowed from WOL packet to starting execution of the rsync?
2. Can I configure this time, either from the GUI or SSH? How please?
Any other ideas please?
ReadyNAS: Pro 2, RAIDiator 4.2.19
Both are connected locally on the same subnet.
I have a job configured to backup a ReadyNAS share to a PC using the PC as Rsync server and with the backup job configured to send a WOL packet to the PC. When the PC is awake, the backup job runs reliably every time. When the PC is initially in standby mode, the backup job reliably wakes the PC with the WOL packet, but the backup job sometimes fails "due to unknown reason".
I've a suspicion that the there's insufficient time for the PC to wake reliably from standby between the WOL packet being received and the rsync beginning execution.
Can anyone tell me please:
1. How long is the time allowed from WOL packet to starting execution of the rsync?
2. Can I configure this time, either from the GUI or SSH? How please?
Any other ideas please?
1 Reply
- StephenBGuru - Experienced UserIt sounds to me that your diagnosis is likely correct. On the PC side, what is the sleep timer set to?
One (ugly) workaround is to create a dummy backup job that runs an hour before the real one, and to set the sleep timer on the PC long enough that it would still be awake.
If you are backing up other devices you could even "cheat", by putting the PC MAC address into a backup job for a different device (the WoL packet is broadcast, so it still reaches the PC). I use Acronis backup (pushing from the PCs), and wake them up on schedule with a dummy backup job to another NAS (scheduled a few minutes before Acronis).
It would be a nice feature to be able to set the wakeup time. If the PC can boot from WoL, the lag could be several minutes. Alternatively, have a WoL schedule that is completely separate (would be a nice add-on).
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!