xaibex
Patron
- Joined
- Mar 19, 2013
- Messages
- 340
Are you starting your Backup job from your Synology or your FreeNAS?Update: I'm finding WOL a bit frustrating. Worked again after the last fix above and seems to work reliably from EtherWaker app on my Android phone, but, with my Synology box sending a WOL packet 5 mins before backup, the backup failed again last night (always because the target wasn't available). I'm going to increase the delay before the backup starts but not convinced it's that -- I did have a failing disk once which caused long startups but not now (I haven't timed it).
Xaibex, I thought I could use the one liner above, thanks again, but I found that rsync stays running (doh!), so it's always found even if inactive.
Currently my Synology is waking the FreeNAS box with this scheduled task at 4AM
/usr/syno/sbin/synonet --wake <mac address> eth0
and my NL54 FreeNAS shuts itself down at 5AM. Maybe I should give up and have a timed boot on the NL54 with an rysnc cron job that shuts down at the end and no need for any WOL from the Synology? BUT... IT SHOULD WORK! And it used to work.
I know this isn't really a FreeNAS problem but WOL capability does matter.
I would experiment how to detect the Backup job with ps. Or try to run the Backup job from FreeNAS itself with a script, which shuts down FreeNAS when the job is finishend.