Skip to main content

Backup running on startup after missing scheduled time even when told not to

Thread needs solution

I didn't have this issue in 2017, but after upgrading to 2018 I have this irritating problem. I have my backup set to backup my entire machine at 1am every day, and it then shuts the computer down when completing. I have also selected the option so that if I miss the update, to not run the update at the next system startup. Yet this is exactly what is happening. If I turn my computer off, so that the backup doesn't run, when I turn it on the next day it runs and then shuts everything down afterward. I don't get why it's running when I told it to not run after missing a backup. Is there another option now that controls this? If I miss a backup I just want it to wait til the next scheduled time. Really annoying being all set to work with a bunch of Visual Studio windows open and a debug session going and then the computer starts to turn off.

0 Users found this helpful

I have not seen other users reporting this type of issue in these forums and never seen it myself.

If you have upgraded from ATI 2017 to 2018 (and possibly previously upgraded from earlier versions of ATI too), then there is the possibility of the task being corrupted in some way?

Have you tried creating a completely new ATI 2018 backup task to do the same as this problem task?  If not, then it may be worth trying that to start with.

If you are still seeing an issue, then either a Repair install of ATI 2018 or even a clean install may be needed to completely resolve any strange issues.

This actually is a new backup task. And this is also a new install of my machine (I upgraded a hard drive a little while ago and used that opportunity to reinstall my system). Sorry about the "upgrade" comment, kind of misleading but no I did not actually go from 2017 to 2018 on this current install. I did that prior to the hard drive replacement. Just to be sure I'm not failing at my reading comprehension, I have "Run missed operations at startup with delay (in minutes)" UNCHECKED.

As a test I just now checked that option, saved, then unchecked it and saved again just in case something somehow wasn't set.

I wonder if you are seeing something similar to what I have seen myself today?

I have a daily Cloud backup task that is scheduled to run at 10:00am or else to Run missed operations at startup with a delay of 30 minutes, but this morning when I booted my laptop, the task started running immediately when it was after the schedule time and the delay at start was ignored.

What I believe has happened in my case is that my computer had gone into a hybrid sleep state rather than being shutdown fully, so when I restarted this morning, I saw that my system Up Time was showing that the computer had been up for over 15 hours at that point!

2018-04-09 13_17_05 Windows up time.png

Not sure if this helps with your problem but something to check?  I will think about raising a Support Case for my particular varient of this issue.