Proactive backups - waking up and staying awake (error -559) in Retrospect 9 or higher for Macintosh Posted September 16, 2016 · Report reply The automatically repeated updating notice, which continued even after I had done the update, turned out to be from Adobe Flash Player Install Manager.app. I deleted the install app. I then reran the same tests early this morning. I got a -519 error on the first test, but the second test ran fine. My guess is that, on my MBP, letting the computer go to sleep after 1 hour temporarily disables the Retrospect Client. This may have something to do with my now having an ATEN CS782DP KVM switch, but I didn't have that switch in February. After disconnecting the ATEN CS782DP KeyboardVideoMouse switch from my MacBook Pro, repeated the same two tests early this morning. Got exactly the same results: "Sun.-Fri. Backup" script got a -519 error (which would be a -530 error after #6080 fix) with the MBP having gone to sleep after one hour per revised System Preferences->Energy Saver options, but ran fine with the MBP awake. So—after eliminating oddities such as simultaneous Adobe updater messages—the results for Wake-on-LAN for my MBP seem to be: works fine when a Mac laptop client is put to sleep via a special keyboard combination on the laptop keyboard, fails with a -519 error (which would be a -530 error after #6080 fix) when a Mac client automatically goes to sleep per System Preferences->Energy Saver options, fails with a -519 error (which would be a -530 error after #6080 fix) when a Mac client is put to sleep via the Apple Menu. To me that sounds as if presumably greater OS X involvement in the second and third cases is what causes Wake-on-LAN to fail on my MBP. That may not apply to other peoples' Mac clients with their own installations of OS X. P.S.: Just noticed (on 18 September) a bug fix for Retrospect Mac 13.0.1 "Fixed issue where clients not found on network incorrectly reported as error -519 instead of -530 (#6080)"; put in parenthetical note after every mention of -519 in this post—no doubt you should mentally do the same for previous posts in this thread.