Aller au contenu principal

>550 Incremental Backups Crashes TI (Cant Mount OR Consolidate)

Thread needs solution

I have licensed copy of TI 2012 home that created full backup + 864 incremental backups over a 4 month period without issue.

When I tried to mount an incremental backup to locate a lost file, TI mount wizard HUNG and or randomly crashed. WER.REPORT indicated VC runtime dll access denied error (likely a buffer overrun)

After 3 full uninstall / reinstalls, I installed trial TI 2013.

TI 2013 doesn't crash, however it only will list first 564 incremental files. Nothing I can do will get it to display / select / mount any incremental backup later than that.

I was able to successfully validate the entire chain but the backup indicates only 564 versions available.
I tried to consolidate, but again, only 564.

Can someone help me workaround this frustrating problem? I have about 10 hours into it already.

Is there some limit to # of incrementals? Is this the wrong approach to take? I like the flexibility of being able to go back in time to any point when a file was changed.

Thanks in advance.

PS. Is the XMAS 2013 sale going to be renewed. Seems like Im going to be forced to upgrade to work around this bug. Seems disappointing to have missed the sale.

0 Users found this helpful

There may well be a limit on the amount of incrementals there can be. I have to say 864 incrementals increases the possibility of corruption happening at some time and rendering your complete archive worthless.

I would suggest either adding consolidation tasks or perhaps splitting the tasks so tha task one produces archive 1 (perhaps one months worth), then task 2 produces the next months archive etc.

That way you will still have the ability to go back in time, but each chain will be much shorter.

Hopefully Acronis might have an answer.

If there is a limit, I would expect that TI popup a polite, clear message indicating that backup cant proceed and that I should consolidate or split as you suggest. Silently continuing to produce backups that cant be mounted simply wastes my time and puts my system at risk - which I consider to be an unacceptable behavior for a backup product.

BTW: I would have setup a consolidate job from the start if the product indicated that this was required

However, in this case, I am running RAID 10 on enterprise class SCSI drives and the incrementals are not indicating corrupted. Running a validate, reports that the backup is 100% healthy.
Whats even stranger is that when I upgraded to 2013 and the backup job ran at next scheduled interval, it prompted for #565 even though it was present in the directory. After that, it proceeded to make new incrementals with a different filenaming standard.

This whole thing is very weird. I sure could use some advice. I need to get this mounted. I can consolidate AFTER getting this file restored.

Due to the new file naming system, I would be inclined to make a new set of images anyway.

Ah you missed out the RAID mention in your first post, that might have some bearing on what is happening, although I don't now why.