corrupt in bootable media
I recently purchased ATI 2015 and have run and validated a couple of backups , full, and incremental.
Today I decided to test validation of one of the full backups with my bootable media disk. This validation reported the backup as 'corrupted, but you may be able to recover files and folders'
What should I believe? Is there an explanation for why the installed program would validate, but the bootable media version of the program would report the backup as corrupt?
I use my backups mainly as protection against drive failure, and need to be able to do a complete recovery.

- Log in to post comments

This backup is on an internal drive connected directly to a motherboard SATAII port.
Tried another validation from bootable media, again reports corrupt.
Booted back to the windows installation, ran validation, validates fine.
I didn't have this problem with the version I just upgraded from - ATI Home 2010
- Log in to post comments

Make sure you are using a 2015 Recovery CD to validate a 2015 tib backup file.
A 2010 CD will not validate a 2015 backup.
- Log in to post comments

I am using a bootable media cd made with ATI2015. The validation begins and runs for about 30 minutes (~25% complete) before reporting the corruption
And I have build 6525
- Log in to post comments

If you copy the archive to another disk, is it reported as well as corrupted?
- Log in to post comments

I don't have a spare disk big enough to test that theory at the moment.
I did successfully validate a different backup with the bootable media. There is a difference in the two backups in that the one that the bootable media reported as corrupted had a name that started with "My Disks..." (ATI generated this prefix and I didn't change it). I suspect that the unix environment of the bootable media may have had a problem with the space in the name that the windows version would not object to. I'm hoping that is the reason it validated under the windows installation, but would not validate under the bootable media version.
- Log in to post comments

Dear All,
I have experienced precisely the same problems with TI 2016.
My platform is Windows 7 SP1 and I record my images onto a 1TB external HDD connected via a USB port.
- Create image (.TIB) with installed application.
- Create image (.TIB) with Bootable Recovery CD.
- Both images Validate perfectly using the Windows TI application.
- Neither image will complete validation using the Bootable Recovery CD.
This is repeatable and what is more, the 2016 app loaded to another completely different computer, running Windows 10, produces the exact same results using a Bootable created via the installed Windows application.
I do notice that although this problem appears to be nothing new, there is no 'eureka' answer.
Any clues, anybody?
- Log in to post comments

Stephen,
Do you have a spare drive where you could perform a "restore" operation using rescue media? The test would be to see if the restore fails at or near the same location where the validation fails.
Is the rescue media Linux or WinPE? If the rescue media is Linux, you should create a WinPE rescue media, and perform the same tests.
Also, please start a new thread in the ATI 2016 section...this needs to be resolved.
Regards,
FtrPilot
- Log in to post comments

The best and only true answer will be restoring to a new drive and seeing what the final outcome is. If one is reporting incorrectly but the image restore is successful, it is most likely a bug. Software validation, should only be taking with a grain of salt. Anyone who does not test an actual restore of their backups is asking for trouble down the road, regardless of the backup type and or backup application.
- Log in to post comments

More on Image Validation with ATI 2016
For imformation and confirmation, I always validate an image immediately after creation. In the past and I've used ATI for around the last 15 years, once an image is successfully validated I've experienced complete reliability. When validating using the 2016 Recovery Bootable Media the cancellation and error declaration that states the image is corrupt, but you can try data recovery anyway (or words to that effect) fills me with an uncomfortable feeling. I did indeed try a couple of recoveries under these conditions. The first of these worked alright. Another rendered the o/s useless! Fortunately I found a time consuming and convoluted work around, thus making a proper recovery from the image that was properly validated using the ATI Windows application.
It seems there is probably a bug in the build of the Emergency Recovery Media tool, so what about issuing a fix? I'm sure it's not beyond the wit of those talented engineers at Acronis to make this work reliably, as has been my experience with the product over the last many years.
- Log in to post comments

Hello there, FtrPilot!
Please advise how I start a thread in the ATI 2016 section. Okay, I'm a dummy - give me some slack and a little help here, please.
- Log in to post comments

Stephen,
Go to the 2016 section and hit the button marked "New Topic"...picture below.
My bad...I should have said "New Topic" instead of "New Thread"
FtrPilot
Attachment | Size |
---|---|
338914-126679.jpg | 281.33 KB |
- Log in to post comments