Proactive backups - waking up and staying awake (error -559) in Retrospect 9 or higher for Macintosh Posted September 9, 2016 · Report reply Random -505 errors on clients is an issue we are investigating. In this case, it could have been a timing issue between when the machine woke up and when the client started and bound itself to the network adapter. Most users will not get that error. The Wake on LAN works by Retrospect sending a magic packet to the client machine. The Magic Packet should then wake the machine and allow a backup. I'd love for not-Waking-on-LAN to be a peculiarity of my MacBook Pro hardware and/or its OS. However color me sceptical. Mayoff, the key word for me in "The Magic Packet should then wake the machine and allow a backup" is should. How recently has Retrospect Inc. tested that it does do this? On what versions of Mac OS X? With what versions of client hardware? With scheduled scripts or only with proactive scripts? Were the clients put to sleep via the Apple Menu, or only from the keyboard? Note that Apple itself has gotten sloppy with testing recently, which is why I have never upgraded either of my two modern Macs to OS X 10.11 El Capitan. And Apple has a lot more money than Retrospect Inc.. And what of Retrospect Windows, as discussed in my first paragraph of post #5 in this thread? Is a Retrospect Windows 11 "backup server" still incapable of sending a Magic Packet to an OS X client? Finally, for completeness, how about my Digital Audio G4 (mentioned in the last paragraph of post #7, but whose test is linked-to in my fourth paragraph in post #5 ) booted under OS X 10.3? Obviously it runs the legacy Mac PowerPC 6.3.029 Retrospect Client. Is that Client incapable of acting on a Magic Packet, because Apple's last PowerPC Mac came out 3 years before Retrospect Mac 8?