Direkt zum Inhalt

Aero for two

The second time I needed to do a quick restore of a failing disk is the second time I was unable to get one.

This time every attempt with Windows, WinPE and Linux yielded a message before and after the restore that the .tib file had a "corrupted Index" yet every attempt to validate the backup gave an all clear response. 

I had excellent support from a technician but the conclusion was that the file must have been corrupted. The file size was correct and I can't believe that ATI doesn't include a checksum in the .tib file.

My guess is that the OS disk had an index problem at the time it was backed up but ATI did not check and does not check when it validates the file but fails to restore. 

I was able to clone the OS disk but I wanted it back at the last full backup. Anyway, I expect all the differentials would have had the same problem.

ATI scorecard:

Technician A+

Backup A

Restore F

In my experience it is a write only backup system.

Since this is for information etc. I will mention that through the process and for years my Windows Home Server backups have been working non-stop though I know, or expect, that only a Windows 7 system disk can be restored to boot. My other computers being UEFI and Windows 10 just have the backed up data available, though I did once restore a Windows 10 UEFI machine but I had to use a third party boot repair.

BTW, does anyone know how to induce an Index Corruption so that I can do additional testing.

Richard

 

 

 

0 Users found this helpful

Richard, was the subject meant to read as 'Zero for two' rather than Aero?

Unfortunately, if there are file system index issues these can get caught up in the backup files but they tend to be very rare as far as reports here in the forums.

I would normally expect ATI to throw an error during the Backup operation but that obviously doesn't always happen. 

I do recall seeing some earlier forum topics suggesting doing a CHKDSK of the Mounted backup image but that would only be of value if any changes could be 'consolidated' back to the image, but Acronis removed the consolidation option back around ATI 2014.

All backup image files do contain regular checksum values embedded for each block within the file, these are used by validation to confirm that the file data remains unchanged from how it was captured and written.  Again, validation only proves the file is unchanged and not that it contains valid index data, which confirms the need for ATI to check the drive index(s) as part of the backup task preparation, and to flag up if a corrupt index is encountered rather than blindly going ahead!

While I understand that you are wanting to recover your backup image, is the original drive that the backup was taken from still viable to boot into Windows?  If so, can you run CHKDSK /F against the partitions for that drive?

An associated question, what is the issue that has brought you to want to recover the image?