Skip to main content

True Image 2012 Backups immediately fail

Thread needs solution

My computer is Windows XP so I can't use more recent Acronis True Image than 2012. It has been a life saver for many years. I recently had a major blue screen issue with my computer that turned out to be a failing ram chip and while I was working through it I used an identical spare computer updated with True Image (I do separate backups to 2 different drives every night). Then once I worked out the problem I went back to my main computer and just to be safe I loaded my latest image to yet another spare (I have quite a few). Suddenly last night my 2 scheduled Acronis backups failed and when I tried a "back up now" this morning it failed immediately. Each time I moved to a spare computer the Acronis successfully activated, and on the current About screen it says Full Version Activated so I don't think that activation is the problem...but I can't imagine what is. Help!

0 Users found this helpful

Marty, your initial statement about Windows XP is incorrect, all versions of Acronis True Image up to and including 2016 have support for Windows XP provided you have SP3 installed.

For the issue with your Acronis backups failing, you should check what messages are written to the Logs for the task and see if this will give you an indication of what the problem may be.

The other check that you can make is to create a new backup task, even if very small of a single folder, and point this to a separate / different folder on your backup drive - this will show if the application is working OK or not.

Thank you for answering. I did buy 2014 and not only wouldn't it install, it made my computer unusable! I had to use my 2012 resore disk to load back my image so, obviously, I never tried installing it again. I do, however, have a Windows 10 computer that I hate and only use to watch Google news all day. None of the programs I actually use are on it and I use 2014 on that to do a once per month backup.

I did create all new differential and incremental backups on the XP computer and spent an entire day and half the night backing up successfully with them. Hopefully they will continue working on schedule now, but I still have no idea why my previous backups failed...they were going along perfectly, on schedule, every night and then one morning, NO. 

Here's one of the logs from my 4 failed backup attempts. Yes, I do have SP3 installed.

1    Information    3/27/2017 6:37:12 AM    Stage Description
2    Information    3/27/2017 6:37:19 AM    Operation Differential T18 started manually.
3    Information    3/27/2017 6:37:40 AM    Analyzing partition '0-0'...
4    Information    3/27/2017 6:37:40 AM    Priority changed to Low.
5    Information    3/27/2017 6:37:41 AM    Analyzing partition 'C:'...
6    Information    3/27/2017 6:37:42 AM    Analyzing partition '0-0'...
7    Information    3/27/2017 6:37:43 AM    Analyzing partition 'W:'...
8    Information    3/27/2017 6:37:43 AM    Analyzing partition '0-0'...
9    Information    3/27/2017 6:37:44 AM    Analyzing partition 'T:'...
10    Information    3/27/2017 6:37:44 AM    Stage Description
11    Information    3/27/2017 6:37:48 AM    Updating backup database:  Setting verification requirement for database access.
12    Acronis True Image Home    3/27/2017 6:37:49 AM    Cannot find source partition with path '\local\hd_sign(EE1E3DAC)\part_sn(1C477B7DB21C47BD)start(63)'.
13    Information    3/27/2017 6:37:49 AM    Updating backup database:  Removing verification requirement for database access.
14    Information    3/27/2017 6:37:55 AM    Updating backup database:  Inserting new backup version creation information into backup with ID 490461533111991750.
15    Acronis True Image Home    3/27/2017 6:38:20 AM    Operation has completed with errors.

Marty, thanks for the log information - the key line that stands out for me is:

12    Acronis True Image Home    3/27/2017 6:37:49 AM    Cannot find source partition with path '\local\hd_sign(EE1E3DAC)\part_sn(1C477B7DB21C47BD)start(63)'.

This suggests that something has changed with regards to your source partition which in turn has caused the unique identifier for that partition to be changed.

The remedy for this is to edit your backup task and reselect the source partition again which will update the identifier information shown in the log entry.