You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My PC is automatically backed up each night with the client backup feature of Windows Server 2012 R2 Essentials.
If the PC is suspended via the Windows toolbar menu, it automatically resumes at the scheduled backup time and the backup job is executed.
If the PC is suspended via the remote-shutdown-pc tool, it doesn't resume and the backup job isn't executed.
Why is the suspend-behavior different, and is there a way to also have the PC resume for the backup when suspended via the tool?
The text was updated successfully, but these errors were encountered:
It works as expected. I specifically disable wake events in suspend command (third parameter): Application.SetSuspendState(PowerState.Suspend, true, true);
I guess I can make the third parameter part of the settings.
I already figured that out and tried to fix it in a local build, but I was unable to compile a fully working binary (I even tried multiple versions of Visual Studio), so I'm currently using a simple Python script I wrote.
But if this issue gets fixed in this app, I'll switch back to it.
I can't imagine why someone would like to ignore wake events, as they were probably scheduled for a reason, so I would expect that just changing the third parameter to "false" should work for everyone, but making it configurable via settings is fine for me as well.
My PC is automatically backed up each night with the client backup feature of Windows Server 2012 R2 Essentials.
If the PC is suspended via the Windows toolbar menu, it automatically resumes at the scheduled backup time and the backup job is executed.
If the PC is suspended via the remote-shutdown-pc tool, it doesn't resume and the backup job isn't executed.
Why is the suspend-behavior different, and is there a way to also have the PC resume for the backup when suspended via the tool?
The text was updated successfully, but these errors were encountered: