Skip to main content

Stopped Backup always resumes from initial start

Thread needs solution

Hi

I am using Acronis TrueImage 2016.
I scheduled a weekly Full System backup which takes some hours to complete.
Most of the time my computer is not running for that long period, so Acronis stops the backup when I am shutting down.
At the next start of the PC it does not resume/continue the backup, but starts completely new from the beginning.

How can this behaviour be changed?

Thank you
Markus

0 Users found this helpful

Hello Markus, I do not believe that this behaviour can be changed due to the way in which a full system backup is performed by the Acronis software.

When you start the full system backup, ATIH creates a snapshot of the system as it is in that particular moment in time, it uses the Windows Shadow Copy Service (aka VSS) by default to capture this system snapshot so that system files and programs that would otherwise be inaccessible can be included in the backup.

When you shutdown your computer and interrupt the Acronis backup, you are also killing the system snapshot which means that this has to be created again when you restart the computer and resume / restart the Acronis backup task.

The only method whereby you can preserve the system snapshot across a shutdown / restart of Windows is if you use the system hibernation facility which saves a copy of all running processes / programs etc into a hibernation file on the system hard drive and uses this to restore all these same processes and programs back into memory when the system is resumed.

I have never tried to hibernate a system which is performing an Acronis Full System backup, so I cannot be confident that the VSS snapshot would also be captured within the hibernation file (C:\hiberfil.sys) - if it is, then this file will be of a very large size as you will essentially have duplicate copies of all this information being stored.

The alternative approach here is to select to Shutdown the computer when the Acronis Full System backup task has completed rather than interrupting it.

Ditto to Steve's post.  If the full backup does not complete, it will not continue where it picked up and a new backup will start again the next time it is run because the snapshot point in time will be different in Windows.  I would think hiberation could be a work-a-round instead of fully shutting down, but haven't personally tried.  

If the backup task is taking a long time, I would start it after hours and let it run to completion.  You can configure the backup to shutdown when complete to avoid the system staying on after that.