Scheduled backup not executed, just delayed
I run ATI 2016 on 3 PCs at home. All 3 have been upgraded to Win 10 and to ATI 2016 build 6571. One PC has stopped taking backups on the schedule, but in a strange sort of way.
The schedule is to take an incremental every day, with a new full every 14 days - see attached pics schedule p1.png and schedule p2.png. I take the first full manually, then ATI says the next is scheduled for 06:00 next day - see attached pic Status 2016-08-22.png. However, no new backup is taken the next day, but the schedule is updated and now says 06:00 one day later! See attached pic Status 2016-08-23.png. There is no logfile at all, which seems to indicate that the backup was not even attempted - see attached pic logfiles_2016-08-23.png (note: the service log from 23rd August 09:51 was a manual backup. When I press the Backup Now button, a backup is taken correctly. It just will not do it automatically on the schedule).
I have tried a complete uninstall using Acronis CleanupTool_48_en-US.exe, and then reinstall, but the exact same symptoms appeared again.
I have the same schedule on my other desktop, and there it works perfectly as expected. Apart from being different hardware, the main difference between the 2 PCs is the Win 10 version: the one that works is Win 10 Home, the one that fails is Win 10 Pro.
Another strange thing is that the failing PC was upgraded Win 10 and ATI 2016/6571 in June. It started out by taking backups as expected, then suddenly stopped around the 8th August or so. Since then I've been trying to find a solution. Can anyone suggest something?
I suspect Windows 10 faststart/fastboot to be the issue and/or the system being asleep at 0600AM. If the system is sleeping, hibernating, or off during the scheduled time, it will not automatically run unless the system returns from a full start. Some power managmenet schemes also disable USB ports, the NIC and hard drives to save energy. You'd want to check in advanced power settings, as well as in computer managent >>> device manager which has additional power saving features for USB ports and the NICs there.
With fastboot/fast start, a full start only occurs in WINDOWS if you REBOOT or use command prompt and shutdown /s. If you have a fast SSD, disabling fasboot in Windows is probably the easiest way to go and you most likely won't notice much of a difference with boot times anyway. If you're using an older spinning drive though, you will see slower boot times with fast start disabled. Faststart essentially acts like the machine is shutting down but really only hibernating. Returning from hibernation does not trigger a missed backup either. This behavior seems to be fixed in Acronis 2017, but has been an issue in 2016.
ATI took a backup at restart this morning, so the problem seems to have gone away - at least for today.
@Steve: I downloaded the log viewer and SchedMgr yesterday as suggested. I did some looking around, but the only change command I executed was the set logflags support mentioned by Acronis. I don't understand the logs, even with the viewer. If the problem recurs, I will post logs as you suggest.
@Bobbo: I've never come across fastboot before, but what you describe is a promising start for me to dig into, especially as you say it's been an issue in 2016. I'm not aware that I use it, but it may have been turned on during the Win 10 upgrade process, or by something else. If it's hardware-related it might explain why the 2 PCs behave differently, as they're totally different at the hardware level (I just buy the best offer I can find when I get a new one, I don't stick to one brand).
Thanks to both of you for a quick response. I'll keep a watch on the system for 2-3 days and post an update; I'll either close the thread or ask for more help if it's stopped taking backups again.
The problem PC has taken backups on schedule for the last 3 days, so I reckon the problem is fixed.
It looks as though Bobbo_3C0X1's suggestion was spot on: the problem PC had fastboot enabled, while my other desktop, which never displayed these symptoms, did not. Fastboot is now turned off, never to return, but if I do meet the same problem again in the future, I'll know where to look - Microsoft is notorious for changing the settings on PCs when installing a 'simple fix,' which is where I suspect the problem came from in the first place (with the famous Win 10 Anniversary Update suspect #1).
Thanks again to you both for your interest and your help. Case closed.
Thanks for the feedback. I believe Acronis has tweaked the application in 2017 to work with fastboot now, but I haven't gotten around to testing. I have a Samsung 950 Pro NVME PCIE hard drive so I can't tell the difference with fastboot being disabled anyway. Eventually, I'll get around to testing to see if 2017 is working with fastboot enabled though. For those of us with SSD's disabling fastboot isn't the end of the world. However, those with slow spinning drives, probably appreciate how fastboot makes it "appear" like it's shutting down and starting up faster by kicking in hibernation