Hi,
Joshua Kugler wrote:
This is just for the archives, and for anyone reading to file away in the back
of their mind for future reference.
...
This had had me stumped for a little while, until we figured it out: the
system was set to autosuspend, so would no respond at 1 in the morning.
Setting autosuspend to "never" fixed the problem. We still shut the display
and harddrive down automatically, just the system itself never suspends, so
we can run the backups.
I've implemented a similar, though more detailed solution.
Prepare a power saving setup which does not suspend the computer, but
may turn off screen and disk.
Setup the computer to use a power saving setting which either doesn't
turn it off when connected to the power supply (assuming that, when
power is connected, the notebook is available for backup). Wake on Lan
would work, too.
I use a run before script which first pings the computer to check if it
is available, and of course you could also have it send a WoL packet,
wait a fem minutes, then ping, and only when that is ok, go on.
My client run before script first switches to the prepared power saveing
configuration, i.e. sets everything up that the network connection will
not break. It then saves windows' system state.
The client run after script in deletes the system state backup and
resets the power settings to the normal ones.
Arno
Hope that helps someone.
j----- k-----
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
