Jump to content

OS X won't backup remote when sleep

Recommended Posts

I have an OS X client with Retrospect Remote installed. When the computer goes into Energy Saver mode, it won't get backed up by my Retrospect 5.0 server. It is not seen in the Retrospect Server until I wake up the comptuer. When it's awake, it will get backed up.


I have set the computer's control Panel to "Wake for Network administrative access".


I know I can set the computers to never sleep, but doesn't that defeat the purpose of saving energy?




Does anyone have a solution?







Link to comment
Share on other sites

In reply to:

I know I can set the computers to never sleep, but doesn't that defeat the purpose of saving energy?


The OS X Client is a unix daemon living in a Macintosh world (I don't think traditional *nix machines have sleep functions). Apple made it so that processes such as these seem to be susupended during sleep.




You can't wake a sleeping Macintosh with ssh or ftp either.





Link to comment
Share on other sites

But you can wake up a Mac that supports Wake On Lan, even in MacOS X. Wake550 is a utility that provides a GUi interface for this.




Here is a link to Wake550:






There was a discussion of this on the MacOS X admin list hosted and archived at Omni's site. A couple of quotes:




"There is an extensive discussion of this feature (together with links to


various command-line & GUI clients) in this macosxhints article:






"this page should explain it ...


http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci214609,00.html "




"This setting permits the use of the so-called "Wake On Lan" mechanism


(an Intel brain-dropping(*)) to be enabled on the built-in interface.


This works, more or less, as follows:


- system goes to sleep, with at least one exception: the NIC


retains enough capability to recognize a so-called "magic


packet" (below) when it is received


- when one of these is received, the NIC will "pull the power


chain" on the system, causing all sleeping components to




- the magic packet itself is lost; no other (earlier) packets are




- of course, the system will take some finite amount of time to


shake the sleep out of its eyes, which has to be accounted for


when using this (back-to-back packets, the first of which is


the magic packet, and the second of which is important, will


probably see the second one dropped)."




I recently mentioned this feature on the Product Suggestions portion of this list.







Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...