Direkt zum Inhalt

Missed Backup

Thread needs solution

I have TI 2016 and I have a client that I recommended and he purchased TI 2017. Both versions do not backjup if a scheduled backup is missed. For instance, if the computer is not on the day the backup is scheduled, or is turned on after the scheduled time, the backup does not happen. I've had TI since version 8. All the previous versions would perform a missed backup. I've tried both versions with "Run when the current device is attached" checked and unchecked. Neither will run a backup until the next scheduled backup. I've also tried deleting the history, still the same result.

0 Users found this helpful

Duplicate of post: 128440: Missed backup - no need to post the exact same issue to multiple forums.

Are these systems running Windows 10 or 8.1?  if so, I suspect fastboot is your problem, but it's hard to say since there's nothign to go on except for the behavior.  There are options in the application to run a missed backup - make sure that is enabled.  Don't use the option to "run the backup only when the computer is idle" if the computer never goes idle (which it probably never will) then the backup won't run either.

I'd also change the "run at the system startup with delay (in minutes)" to add a 2 minute delay - just to make sure the system is rully operational when it comes back to life before Acronis tries to run.  Likewise, i'd set the Acronis scheduler service to use "automatic-delay" instead of "automatic" - this will buy your some additional time for all services to get in order before any backups try to run - it's not uncommong for Windows to stop processing services at 120 seconds after boot as that is the set limit in Windows.  The automatic-delay adds another 2 minutes to the service to give it more time.

And, if backups aren't running when the machine comes alive, - fastboot may be the trouble.  Reboot/restart and see if the missed backup runs soon after, if it does, fastboot is probably the issue.