Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
No problem - just a question about your backup schedule RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've had WHS 2011 in use for several years and all's well. My daily schedule used to be to hibernate my two desktops before going to bed. The backup schedule was set for a one hour period just before I got up in the morning. From the beginning, WHS would wake the units, do the backups but NOT put the units back in hibernation. Both units would then be there smiling at me and be ready for the day's work. Both PCs are home built with ASUS P7P55D motherboards and I figured they couldn't be re-hibernated.

    Since upgrading both to Windows 10 Creators Update, both are now put back into hibernation after the early morning backups and I must manually get them started after I rise. This isn't necessarily a bad thing but I think I should re-think my daily plan. Why not tell WHS to not wake a hibernated PC and set the backup window to be 10AM - 2PM or 6PM - 8PM. These PCs are not used for business and I wouldn't be inconvenienced by having a backup run during the day.

    So, what schedule do you use? Are seeing different behavior after Win10 CU?

    Don

    Wednesday, April 19, 2017 1:30 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I was under the impression that the Server woke up the Client so a backup occurs as scheduled but that the Client has the responsibility to go back to sleep?

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    Wednesday, April 19, 2017 3:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    My impression was that the client woke itself up by setting a timer at a random time in the first half of the backup window and then put itself back to sleep.  No matter - my system now works differently with Win10 CU than ever before.  I'm still interested in how you've configured your system.

    Don

    Wednesday, April 19, 2017 3:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You are right of course. There is a Task Scheduler task on the client that wakes it up and if the Server isn't busy with another backup, it backs up the client. Still think it's also the Client's responsibility to go back to sleep. I have various Clients that do not sleep after backups but rebooting them normally fixes the problem. I have not updated any of my clients to CU yet so can't comment on whether there is any difference. Not sleeping is often caused by an incompatible hardware driver.

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    Wednesday, April 19, 2017 11:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    I am checking to see how things are going there on this issue. Please let me know if you would like further assistance.

    You can click “Mark as answer” if the reply is helpful. It would make this reply to the top and easier to be found for other people who has the similar problem.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, April 24, 2017 3:13 AM