After a backup finishes: sleep, hibernate or shut down
Let the last backup of the day put the PC to sleep or shut it down, after a sixty-second countdown.
"Back up, then shut down" is worth automating. When a backup finishes does it, after a sixty-second countdown.
Set it#
The choices are Do nothing, Sleep, Hibernate and Shut down.
| Where | What it sets |
|---|---|
| The job's Settings step ▸ Advanced ▸ When a backup finishes | this job, every run |
| Settings ▸ Schedule & power ▸ When a backup finishes | the value new jobs start with |
| The run page's Performance card, while a backup runs | this run only |
What happens#
When the run has finished, a sixty-second countdown starts.
If the GBM AI window is open, a dialog shows it: Shut down after this backup. Documents & Desktop has finished. The computer will shut down when the countdown ends, with the seconds left and one button, Keep the computer on. Press it and the PC stays on; nothing else changes.
With the GBM AI window closed, a Windows notification says so, for example This PC goes to sleep in 60 s, and the icon in the notification area counts down: Going to sleep in 42 s. To cancel, right-click the icon and choose Keep the computer on.
Warning
Let the countdown run down and the PC does as asked. If you work late on a PC whose backup shuts it down, save your work first.
When other work is still going#
The PC is never put to sleep or shut down under a backup that is still to run. If other backups are running or queued, or a restore is going, the action waits. With the window open, a strip at the top says so, for example Shut down when everything has finished. Asked for by Documents & Desktop. Still to finish: 1 backup., with Keep the computer on.
The countdown starts once everything is done. A backup that starts during the countdown sends it back to waiting. When several jobs ask for an action, the strongest one wins: shut down over hibernate, hibernate over sleep.
When it does not run#
- After a run you stopped: you are at the PC.
- When the setting is Do nothing.
It does run after a run that finished with skipped files or failed.