Skip to main content

Full PC backup gets stuck at 373 MB for ever !!

Thread needs solution

Running Acronis TrueImage 2016 on a Win 10 Machine. Build is 6569 ( the latest )

Trying to do a full back and since last one week i have a funny issue. The back up starts and stops at 373MB trying to calculate time. See the attachment.

This is very annoying and i have tried a Repair with the latest build. Created a fresh Back Up task. Stopped the VSS service. Even tried praying !

My external HDD is a 500 GB one with about 300 GB free space. My whole PC requires about 190 GB space to be backed up.

Is there any way out of this ?? Thanks

Attachment Size
acronis_error.png 23.88 KB
0 Users found this helpful

Please download a copy of the Log File Viewer App from the forum and look at the messages being posted in the Service log for your 'stuck' backup task - this should be the first log shown in the viewer.

It is possible that ATIH is encountering a problem on your source disk drive that is causing it to stick at this point but hopefully the log may provide more information.

Raghunathan Ramak...

In addition to Steve's recommendation, I have ideas suggestions.

1) If this backup is occuring in Windows, it may very well be a Windows VSS issue.  Try disabling VSS temporarily and run the backup.  If that works, then VSS is teh issue and you can leave VSS disabled for the entiere machine (not recommended), or for your specific backup task(s) (that would be my recommendation).

Disable VSS 3 ways (try the 1st way - that is the one I'd recommend)

2) Try a full backup with your offline bootable media as well.  This is completley outside of Windows and if it can complete, then we can assume it is VSS or something else in Windows causing the issue.  The offline backup does not use VSS and will use the Acronis Snapapi backup method, which is what will be used in Windows if you disable VSS.

3) If even the Snapapi method in Windows, or the offline backup fail, chances are you have a bad disk or dirty sectors on either the source or destination drive.  You would then want to open an elevated command prompt and have Windows attempt to find, mark and repair bad sectors using:

chkdsk C: /F /R     (to run on the source disk)  (to run on the destination disk, change C: with the other drive letter

Raghunathan Ramak...

In addition to Steve's recommendation, I have ideas suggestions.

1) If this backup is occuring in Windows, it may very well be a Windows VSS issue.  Try disabling VSS temporarily and run the backup.  If that works, then VSS is teh issue and you can leave VSS disabled for the entiere machine (not recommended), or for your specific backup task(s) (that would be my recommendation).

Disable VSS 3 ways (try the 1st way - that is the one I'd recommend)

2) Try a full backup with your offline bootable media as well.  This is completley outside of Windows and if it can complete, then we can assume it is VSS or something else in Windows causing the issue.  The offline backup does not use VSS and will use the Acronis Snapapi backup method, which is what will be used in Windows if you disable VSS.

3) If even the Snapapi method in Windows, or the offline backup fail, chances are you have a bad disk or dirty sectors on either the source or destination drive.  You would then want to open an elevated command prompt and have Windows attempt to find, mark and repair bad sectors using:

chkdsk C: /F /R     (to run on the source disk)  (to run on the destination disk, change C: with the other drive letter

373MB is not a lot of data. The software could get stuck on a partition before getting to the C:\ partition.

Try to backup each partition of your disk separately, to make sure that the issue is with the Windows partition.

Thanks to all of you who took the trouble of posting solutions.

But i seem to be headed for more trouble. This is what happened :

1. Disabled VSS.

2. Ran chkdsk with /F and /R swithces on both C: ( source disk) and F: ( destination disk). No issues found

3. Tried to create a new full back single version scheme.

When I started backup it just did not start at all !. Tried to repair using the latest version. No luck. So unisntalled the application ( the application was showing 1.2 GB size !!) and and tried to install the latest build 6569.  But it went to the last stage and stopped saying Installation failed.

So it now looks I need to do a clean install after manually removing all traces of earlier installation. Not sure if there are other reasons for installatiuon to fail ?

If you downloaded the log viewer app you can view installer logs with it which might help in figuring out what went wrong with the installation.

When performing an uninstall & reinstall, you should run the Acronis cleanup utility before performing the reinstall.  Here's a link for the cleanup utility.  The link covers the entire process.  After running the cleanup utility, you will need to reboot...this is important.

https://kb.acronis.com/content/48668

FtrPilot

Sorry guys.. this is pretty frustrating. I know all of you who posted are trying to help but despite all that is done i am just wasting time something which i dont have :-(  Agreed.  file management is not a tiopic for the weak of heart. But then this is a commercial product and users cannot be expected to be semi-geeks or geeks. FOr those of you familiar with stuff kernel / services / registry it might be child play.

In my last post i said about Installation Failure. Then i rebooted and tried again. This time it passed. So created a new back up job and started. Same thing : It came upto 373 mb AND STOPPED for ever.

Check the destination HDD for errors - nothing. Change the HDD and try again with a new backup task. Same result. Thats 373 MB is starting to irritate now.

OK i downloaded Log Viewer 2.1 ( standalone version ) and ran the EXE .  I am attaching the log file copy. I waited for a long time at the 373MB mark and terminated the process ( it must have been there stuck for 10 minutes or so )

Does the log file say anything useful ?? Thansk for your support so far ....

 

Attachment Size
362560-129838.log 2.96 KB

I see in the service log that you are choosing to create an Entire PC backup.  This might be the issue.  When configuring the backup if you click on the Entire PC icon you will be given other choices for what to backup.  Select Disk and Partition backup then select your C: disk and see if this configuration will run successfully.

Enchantech wrote:

I see in the service log that you are choosing to create an Entire PC backup.  This might be the issue.  When configuring the backup if you click on the Entire PC icon you will be given other choices for what to backup.  Select Disk and Partition backup then select your C: disk and see if this configuration will run successfully.

Yes i need a full back up of the PC as i have two partitions on the single 500GB drive. C: is for Windows and programs and D: is for all my data.

Anyway I finally started a full back up and left it there and went to sleep - today morning i see that the operation has completed and taken something like 2 Hours and 50 minutes. Earlier to back up my 160 GB worth full PC data it used to take only about 1 hour 45 monutes or so.

Attaching the service log for this. To me it looks OK. Is it Okay ??

 

Attachment Size
362652-129841.log 4.22 KB

I have looked at your service log and it looks fine.

You should download the log viewer app, which  makes reading the service logs much easier.

https://forum.acronis.com/forum/115626

 

FtrPilot wrote:

I have looked at your service log and it looks fine.

You should download the log viewer app, which  makes reading the service logs much easier.

https://forum.acronis.com/forum/115626

 

Yes the service log that i attached was actually a copy of the one from Log File Viewer. Good one.

Its a good inside view of whats happening behind the screens - I think Acrnois can make it a part of thier HELP portfolio.

I wouldn't worry about the speed in this case.  It can fluctuate when backups are being taken in Windows depending on available resources and other things running in the background.  Also, as a disk fills up (the one where backups are being written), free space will become less and it may take longer to move files and sectors around to make space for new ones... especially for a large backup job (like a single .tib that is several Gb large).  I tend to break up my backups in 4Gb chunks for this reason and I think it makes backing up over a network more efficient too.   You can also change the priority of the backup in the script... the default is low, but can be changed to "normal" or "high".  I usually set mine at "normal", but if backups are running after hours, then I'll set it to "high" for those.