NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
simsan
Dec 31, 2015Aspirant
Wake-On-LAN delay for Backup Job
I have an older "ReadyNAS Ultra 2 Plus" running RAIDiator 4.2.28, and I have configured some backup jobs (using the 'Backup' --> 'Backup Jobs' menu item in the admin web interface). The jobs will successfully connect to specific shares on my Dell Precision laptop and perform scheduled backups of the files.
I am, however, struggling to make this work if the laptop isn't powered on when the jobs are scheduled to start. I've checked the checkbox for the "Wake on LAN" feature (for each backup job) and added my Laptop's MAC address. I've also turned on the WOL feature in the Laptop's BIOS configuration. My problem is that the Laptop seems to wake up, but the laptop's boot process appears to be too slow for the backup jobs. They all fail with log entries like the one below:
Is there a way to configure a x minute delay for the backup jobs between the Wake-on-LAN message and the start of the Backup job?
(I'm using a setup with a gigabit switch and wired connection (cat 6 cables) between my laptop and the ReadyNAS)
----------------------------------
INCREMENTAL Backup started. Thu Dec 31 10:17:07 CET 2015
Job: 001
Protocol: cifs-ab
Source: //[Laptop-Share-Here]
Destination: [backup]/*********************
Connection to [Laptop] failed (Error NT_STATUS_BAD_NETWORK_NAME)
Files copied: 0
Backup failed. Thu Dec 31 10:22:10 CET 2015.
Reason for failure:
Unable to access remote path //[Laptop-Share-Here].
SOLVED: It turns out the Wake-On-LAN wasn't working after all. Perhaps one of my kids switched the laptop on while I was having a snack :-)
It turned out the MAC address hadn't been correctly configured in the backup Job's Wake-on-LAN configuration after all. It seems the colon (":") symbol between each hex number was important.
1 Reply
Replies have been turned off for this discussion
- simsanAspirant
SOLVED: It turns out the Wake-On-LAN wasn't working after all. Perhaps one of my kids switched the laptop on while I was having a snack :-)
It turned out the MAC address hadn't been correctly configured in the backup Job's Wake-on-LAN configuration after all. It seems the colon (":") symbol between each hex number was important.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!