Salta al contenuto principale

TI2010 creates a recurring consolidation error

Thread needs solution

This happened with TI2009, and TI2010 retail version. It never happened with the last TI2010 beta.

Essentially, I have two disks for backups. I backup my system drive each night as a full backup, and each day on the other disk as an incremental backup. The incremental is setup in a way that if more than 7 archives are there, there is a consolidation of the first 2 archives. That way I can keep 7 days worth of backups, as needed.

Trouble is, once every few weeks the consolidation fails, and I find myself with a lonely full backup. The files should be named C, C1,..., C7. When the error occurs, the remaining file is named C8 and all the other files disappear.

It happened today for the first time with the new TI2010 retail.

The OS is Windows 7 Ultimate 64bit RTM.

I have attached the log so somebody from support can check it out.

Thanks.

0 Users found this helpful

What beta build number were you using that didn't have the problem?

It was the latest build before the official release. The version should be 13.0.0.4027.

Cooper wrote:

It was the latest build before the official release. The version should be 13.0.0.4027.

The last beta build to my knowledge was 5008 with the remote possibility of build 5054 lurking somwhere.

Build 4027 was an early beta, so if your problem didn't exist at the 4027 stage, that might help Acronis work out what they altered which might now be causing your problem.

I believe the other betas were made available to those reporting specific problems that were thought to be solved in newer builds, which would explain why you might have only seen one version.

I'll wander off and try 5055 consolidation later and see if I can replicate your problem, though I'm using W7 Ultimate 64bit 7600.

bodgy wrote:

The last beta build to my knowledge was 5008 with the remote possibility of build 5054 lurking somwhere.

Build 4027 was an early beta, so if your problem didn't exist at the 4027 stage, that might help Acronis work out what they altered which might now be causing your problem.

I believe the other betas were made available to those reporting specific problems that were thought to be solved in newer builds, which would explain why you might have only seen one version.

I'll wander off and try 5055 consolidation later and see if I can replicate your problem, though I'm using W7 Ultimate 64bit 7600.

Thanks for your help. I'm using W7 Ultimate 64bit 7600 too, I'm a Technet subscriber. To replicate the problem, you should backup a small partition, with incremental backups, limit them to 2 or 3 archives before consolidation (instead of 7 to make it faster). Then keep on making backups until the problem comes out, apparently randomly. If it's too much of a hassle don't worry, I'll wait for an Acronis response or contact support.

My task 'auto consolidated last night' for the first time, the only strange thing I found is that it doesn't appear to have consolidated the complete archive, just the last 3 days and has produced a consolidated image plus a small remainder.

I'll see what happens with tonight's image as the image sequence number has been changed by TI.

My consolidated tasks are now causing a strange problem, that I've mentioned in my own thread. After the first consolidation, it then changed the file name sequence number and the following day's image reported an error in not being able to find volume 2 of the archive. However it had made a complete image and the image contained duplicate folders, when mounted. Every day since then the same error has happened. So my problem doesn't manifest itself as yours, but is the same module causing a problem.

bodgy wrote:

My consolidated tasks are now causing a strange problem, that I've mentioned in my own thread. After the first consolidation, it then changed the file name sequence number and the following day's image reported an error in not being able to find volume 2 of the archive. However it had made a complete image and the image contained duplicate folders, when mounted. Every day since then the same error has happened. So my problem doesn't manifest itself as yours, but is the same module causing a problem.

Yes, I guess it's two manifestations of the same problem, and yours is even worse.