Stuck in Consolidating backup
Quite frequently but not always, my True Image Home 2011 would get stuck at the "Consolidating backup" stage after a new Full backup is done and it tries to clean up the last week's incremental backup.
The backup scheme I use is Incremental, which creates a new full backup after seven increments. It keeps only one version chain at a time, which is why the old chain deletes when the new full is complete.
When TIH gets stuck, there will be a .tib file with a GUID suffix that is zero bytes.
22/06/2012 10:05 243,763,639,296 diablo_F(2).tib
23/06/2012 18:36 244,946,432 diablo_F(2)2.tib
24/06/2012 13:21 28,829,696 diablo_F(2)3.tib
25/06/2012 10:33 131,931,648 diablo_F(2)4.tib
//****************************************
// Backing up S drive here, complete but stuck in consolidating stage.
//****************************************
26/06/2012 11:31 187,609,674,752 diablo_s(2).tib
26/06/2012 11:31 0 diablo_s(2)_0B69EE25-388B-4EB4-963F-13E1DC6541861.tib
At this state, i have no choice but to cancel the backup otherwise it would be perpetual. After cancelling, the GUID .tib will disappear, and the backup will be considered failed. However the next increment would work just fine.
What kind of condition causes TIH to get stuck like this? What is it trying to consolidate?
yes automatic cleanup is turned on to store no more than 1 recent version chain.
It has happened today again and I don't know just what it is trying to do that gets it stuck.
Aaron,
There have been other reports of 2011 getting stuck in keeping only 1 recent version chain. I don't know whether changing to 2 would help or not. The 2012 version supposedly fixed that issue.
The replacement file is created.
The deletions take place.
A consolidation occurs
but I believe the consolidation is a misnomer as it really is a regrouping of numbers to be assigned and to be checked as part of the archive so my opinion is that no consolidation occurs but a resetting of settings--which is called a consolidation.
Edit-update:
Correction as to what happens during consolidation--as I have observed.
The replacement created.
A consolidation begins
the Deletions occurs of files to be deleted as part of the cleanup.
The replacement numbering occurs.
So consolidation is a combination of several pieces of maintenance.
I do not understand why this is only "fixed" in ver 2012. This is a defect, not a feature enhancement.
I am not associated with Acronis so I do not speak for them either. My response to you was that of a volunteer.
The last build of fixes for the 2011 version was Sept 29, 2011 which was #6942 and was the 7th build released for that version. If you are not using that build, upgrading to that build may help.
Whether there will be additional updates for the 2011 version is unknown. My "guess" is no based on the release date of the 2012 version which was Aug 23, 2011 but that is strictly a guess on my part.
Your problem may be an anomaly and creating a new task may be a solution. Any editing of the original task is discouraged and the results can be unpredictable and could be a factor in your problem if the original task was ever edited.
Aaron,
At this point, I would try a find a backup scheme that works for you, and/or I would wait for the 2013 version which I am guessing will be released in the fall timeframe.
More precisely, ideally, I'd wait until Acronis releases the first update after the new release of 2013...
I am already using build 6942, and i have recreated backup schedules various times; this problem still crops up every now and then, like right now. thanks anyway.
/sigh
Aaron,
Just curious. What/where is the target disk? Network, usb, eSata, internal, etc