I was hoping for some help with what to check on for getting my server back to waking up for client backups. Last night was the second night in a row where I got up around 1 AM, found the server asleep. I resume by power button, and any and all client PC's scheduled after the time I resume will complete the backup, but of course any computer that was scheduled between midnight and the time that I happen to manually resume the PC show un successful backup.
What I know...
The server was asleep last night before I went to bed. It did, and shows in the event log, awakening at 11 PM for the server backup, then appeared to enter sleep at ~11:23, didn't wake at midnight for the client backups.
The lightsout XML file shows TRUE for being awake during client backup hours. Verified that the box is checked for lightsout to keep server awake during client backup hours. cleared the checked, re-checked and hit apply, just in case.
One client PC had a date showing for next backup as being early this morning, one client PC was unsuccessful (this was the only one that was scheduled between midnight and the time I resumed the server manually), all other PC's backed up as they should. It's almost as if it skipped over the one PC that was still showing a backup scheduled for around ~3AM this morning, yet said that was the next scheduled backup time. To correct this, I initiated a manual backup, after it completed, it then give a new time for the 25th.
I know a recent crash with the server is most likely to be the culprit, I'm just wondering if there is a database that needs rebuilt to get this going correctly or perhaps I need to remove the lightsout add in and reinstall? I believe the crash accured on the 18th or 19th, but since then, and having reconfigured what appears to be a 'new' entry for a the NIC, everything has been running smoothly with only the exception of the server not waking at midnight.
Is it possible there is a time issue with the clock on one of the client PC's?