Consolidation fails with Backup date cannot be found
I have a large set of backups, spanning more than a year, that I cannot consolidate because the program fails with "Backup date cannot be found" and event code 0x01E50003+0x000B03EA. The online error lookup interface has nothing for these code.
I believe that the problem is on Dec. 26, the disk was out of space, so the backup failed that day. I cleared some space, and it has been ok since then. However, I now cannot do any consolidation, even when the consolidation skips the bad day, or the consolidation is only for days prior to the bad day. The consolidation quickly fails with the backup date cannot be found error. The consolidation result is being written to an entirely separate disk, so space should not be an issue.
The backups were entirely incremental after the first full backup, and created using Acronis True Image Home 2011. When that program failed to handle consolidation, I installed True Image Home 2013, but that is no better.
Yes, the long chain of incrementals isn't what I really wanted, but I didn't see any good choice when I started it. I also didn't put any size limits on it, which I should have done. I was hoping to do a one-time consolidation to a smaller set, then do auto-cleanup thereafter so it wouldn't get out of hand.
Now it looks like version chain backup scheme is more like what I wanted in the first place.
I have file backups completely separately. This is just for quick restoration of my C drive if something goes wrong.
The version chain backup is a bit inflexible because it is a preset. Your choice.
Acronis 2013 - I ran into a similar problem today. Both of my backups are now failing because "backup date cannot be found". I'm using a disk backup with incrimental backups after the first full backup with auto-cleanup after 30 days. My backups started failing after 30 days (surprise surprise). I have lots of space on my destination drive, so that is not the problem. To resolve the problem I deleted the TIB files and recreated the backup (basically started over). I tried just deleting the TIB files but the backup failed (for a different reason). I suspect it will start failing again in 30 days. What, if any, are the Acronis options that will WORK for creating a disk backup scheme that will create incremental backups on a daily basis and either consolidate the backup when they get to be over a certain size or certain number of days or before they chew up all the memory on my backup drive. In the past I tried to have Acronis remove backups (or consolidate them) when there was not enough disk space left, but that did not work for me either. I'm just looking for a simply algorithm for backing up my stuff every day that will work... and not require that I keep a really close eye on them. Given the number of times I have seen Acronis fail, I'm going to see if the option to email me when a backup fails actually works!
Ta,
These settings work for me. Choose either the 11-Full; or the 11-Inc; or the 11-Dif ; type backup scheme.
These examples are based on the new backups being rotated in as the old backups are rotated out--much like an escalator as the old drops off as the new arrives. This involves no merging of one into the other.
My suggestion is NOT to use the option involving elapsed time nor not use the option based on consumed or remaining space.
Simply select how many backup chains you wish to retain and let TrueImage do the rest. Note, you must allow room for one extra full backup as there will be no deletion of backups until a new one has been created so there is temporary need for the additional space requirements.
My suggestion also involves perform NO edits on a backup scheme. Editing causes confusions and an edit may not perform as expected. If an edit needed, start a new task. My suggestion is that there be NO intermixing of backup files so each task has its own storage folder.
Figure 11-Full: Example of custom/full backup method settings
Change the 4 to fit your needs. Allow space for 1 more full than your selected number as TI will NOT delete the oldest full until its replacement has been created.
Figure 11-Inc: Example of custom/incremental backup method settings
Change the 6 or 4 to fit your needs. Allow space for 1 more full than your selected number (4) as TI will NOT delete the oldest full or chain until its replacement has been created.Understand the limitations of incremental backups. If one inc backups gets corrupt, all newer inc are worthless so avoid excessive number of incremental backups. Always maintain a full backup set which are current This explains why my keeping of x number of "recent version chains" can be important.
Figure 11-Dif: -Example of custom/differential backup method settings
Change the 6 or 4 to fit your needs. Allow space for 1 more full than your selected number (4) as TI will NOT delete the oldest full or chain until its replacement has been created.
I made another stab at this problem, trying to consolidate down to a couple backups onto another disk. I did a Validate on the backup. Acronis took 2 hours, and finally pronounced it perfectly valid. But trying to consolidate just a couple really old (meaning early) backups, I still get backup date can't be found. Clearly, you can't have it both ways - valid yet too broken to consolidate. I can't decide if the validity check is broken, or if the validity check is not a complete validity check, or if consolidation is broken.
< I can't decide if the validity check is broken, or if the validity check is not a complete validity check, or if consolidation is broken.
Well one way of finding out would be to run the validation from the recovery CD, if it validates there, then validation is unlikely to be broken. The other way to check if your images are OK, is to mount your image at an earliest date and a later date, if they mount OK, your images are not damaged.
Do you have enough room on your drive to contain the current archive plus 1.5 times the same amount of space again? Consolidation will make a temporary archive while it consolidates the archive, only once it has succcessfully consolidated will the old archive be deleted.
It is possible the error message doesn't quite mean what it says.