Skip to main content

Backup doesn't run when I startup computer after scheduled backup time

Thread needs solution

Recently did a clean install for ATI 2016 Build 6559 and the backup doesn't run when I startup the computer after the scheduled backup time. I thought there was an option for this but I can't find it. Can someone point me in the right direction?

Thanks, Bob

0 Users found this helpful

Hello Bob,

There is an option on the Schedule page for File Backup Options, in the Advanced Setting section to:

Run at the system startup with delay (in minutes) to launch a missed backup schedule on the next start.

I have the same problem.  It worked OK under TI 2014 but it does not work under TI 2016.  I reported the problem to support on Sunday and send additional information, as requested, yesterday.

If before shutdown it shows next backup at 08:00 next day and I boot after 0800 the next day the backup has been skipped and the shedule for the next backup has moved to the next day.

I'm waiting for a response from support.

 

 

George,

As Steve S. has correctly stated:

"There is an option on the Schedule page for File Backup Options, in the Advanced Setting section to

"Run at the system startup with delay (in minutes) to launch a missed backup schedule on the next start. "

Here's a screen grab:

 

FtrPilot

Attachment Size
352742-128404.png 51.44 KB

George, please see post https://forum.acronis.com/forum/117256#comment-352708 where another user hit a similar problem and resolved it by deactivating Windows Fast Start (Windows 8.1 or 10).

I have the option you suggsted set. It worked fine in earlier builds but not in 6559.

I see your suggestion in another post on this thread to disable Win Fast Start but I can't find where to change the setting - it does not show on my Win 10 Task Manager -> Startup Tab. Can you point me in the right direction?

Thanks, Bob

UPDATE: Found the Fast Startup option in Power settings. Both Fast Startup and Hibernate were unchecked so I guess this isn't my problem. Other suggestions?

Thanks, Bob

Bob, please see http://lifehacker.com/enable-this-setting-to-make-windows-10-boot-up-faster-1743697169 for where these settings are configured.

For those with decent SSD's, you may want to disable fast startup and test boot times to see if there is any noticeable difference in booting.  I disable fast startup on all of my systems with SSD's and see no difference in boot time because the SSD's are plenty fast by themselves.  I find the behavior of actually shutting down (when I click to shutdown) to be preferable.  Of course, those using spinning drives and hybrid drives (or super cheap SSD's) may prefer the saved time with fast startup, but unfortunately, since there is no actual "shutdown" with fast startup enabled, it is a tradeoff that one has to pick between - faster "boot" (not really a boot, but wakeup up from hybrid sleep), or automated backups running when scehduled ones have been missed.

Thanks for the suggestions to disable Fast Start as a circumvention.  I do have it enabled.  I will try disabling it.

If this is the cause then, since I have not changed this option between running TI 2014 and TI 2016, I don't understand why TI 2014 worked perfectly in respect of running missed backups at next boot and why TI 2016 cannot tolerate this Windows setting.

It seems to me that the TI code has changed and introduced this problem as a bug.

 

 

Acronis did admit this was a bug in v6027 and it's now supposed to be fixed in v6559.  So far, most of the people who had this issue are reporting it fixed in v6559.  If it's not though, I would submit feedback to Acronis with a system report and reference this thread link as well so that an engineer takes not and hopefully contacts to you to look into this more.  If it is a lingering problem, they would want to know and be able to help troubleshoot so that it can be remedied in future releases.  

Before you do though, if possible, please make sure fast startup is indeed enabled and reboot at least once (to fully shutdown, a reboot will not use faststart and will force the system to start fresh... since shutting down actually does not shutdown with fastboot enabled perhaps the changes have not had a chance to apply in the registry yet after upgrading to v6559?).  After rebooting, then try to shutdown and start up and check and see if fastboot is disabled again or not.  

Thanks Bobbo.

I've turned off fast boot and rebooted twice since (fast boot still off).  I'll find out late tomorrow if that has circumvented the problem.

Originally I upgraded TI2014 to TI2016 but after seeing the problem I removed all Acronis products and did a clean installation.  Made no difference.  I'll see what tomorrow brings.

I have already raised the problem with support (Sunday) and have a case.  They have a system report and scheduler logs with tracing turned on.

 

Downloaded Build 6569 and looks like Acrois fixed the problem. I notice that Fast Start is disabled. I wonder if I can enable Fast Start without the problem recurring. Has anyone tried?

It depends on the situation.  Fast startup is actually the problem because when you "shudown" it's not really shutting down - just hibernating.  As a result, when you "power on", since you never really shutdown, it doesn't trigger with Acronis that the machine was off which is what it's looking for to run the "missed" backup.  

You could, however, create a Windows Scheduled task to run a backup after coming out of hibernation, but that's a bit more in depth and would run anytime the system came out of hibernation, so might not be ideal either. 

Personally, if you're using an SSD and boot times are tolerable (should be relatively fast), I'd leave fast boot disabled.  I do this on all of my systems (regardless of using ATIH or not) now.  The 5 seconds fastboot saves, prevents things like my other bootable media (multiboot, yumi, etc ) from working correctly because it's not really shutting down either. 

If you have a super slow spinning drive or hybrid drive, I could see why fastboot would be good though, but if startup time is that important, investing in a $80 250GB OS drive and putting all of the user data on the spinner might make more sense in the longterm.  

Evidence seems to point at Fast Start being a cause of Acronis TI 2016 failing to run a backup that should have deferred due to the system not being booted when the backup was scheduled.  

I appreciate the helpful comments that helped identify the cause and suggested circumventions.  However, I really don't believe that itwould be that difficult for the code to be changed to recognise that the system has been shutdown and handle the situation correctly.

Using the Event Viewer there are a number of Kernel Boot Events logged on a Fast Boot so it is clear that information is available if interrogated.  I believe that Acronis can and should fix their code in this area rather than expect users to either accept a slow boot or upgrade their hardware. 

(P.S. In my wife's almost new laptop I'm not sure that it is feasible to upgrade it to a SSD without a lot more cost than 80 dollars since it is not intended to be taken apart except by service staff and is still under warranty.)

George,

I'd hope to see some ability to change this behavior in future updates as well.  As the program was written though, it is still currently dependent on the system fully shutting down and not hibernating, which is what fastboot is doing so it's not meeting the requirements of an actual shutdown.  I'd guess this is something that we'd see in 2017, but can only speculate.  

And correct, not all systems can easily gain access to the Hard Drive - tablets and 2-in-1's like the Surface line come to mind.  The higher end tablests like the Surface to have nice SSD's in them already though - worth a shot to see how much time is lost doing a full shutdown with fastboot off vs on.  What kind of tablet did you happen to pick up - perhaps I can help find a tutorial on hard drive replacement - Dell tablets are accessible, others, perhaps not.

I don't have fast start on any of my systems (and hibernation disabled) so I don't have the event ID to test, but you could create a Windows scheduled task in the meantime using the following code (change the startupscript with the one in your system)

"C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:"2D01277E9-8320-9E8D-BF7A-725EBB9DE06A.tib.tis"

Then in your scheduled task "trigger" change it to "on event" and put in the event ID for resuming from fastboot and it would technically run anytime the system resumes from a fastboot shutdown.