Skip to main content

"The file is corrupted" - unhelpful error log

Thread needs solution

After running a backup for a couple of hours the validation task dies in a few minutes with this completely unhelpful message. Acronis needs to do a lot better with its diagnostic communications.

--------------------------------------------------------------------------------Log Entry Details
Type: Error
Date and time: 3/01/2010 9:36:22 p.m.
Backup plan: M
Task: Validation task
Code: 4,194,395(0x40005B)
Module: 64
Owner: alanw@ALANWS3
Message:
Failed to validate backup archive 'M.tib_2010_01_03_14_26_44_203F' from the location with ID 'file:Z:\TI_Backups\'.
Additional info:
--------------------
Error code: 91
Module: 64
LineInfo: 86092f0ba8acbc04
Fields:
Message: Failed to validate backup archive 'M.tib_2010_01_03_14_26_44_203F' from the location with ID 'file:Z:\TI_Backups\'.
--------------------
Error code: 13
Module: 4
LineInfo: c847b314771c5f19
Fields:
Message: The file is corrupted.

0 Users found this helpful

Further to this, after the (Tower of Hanoi) backup plan twice failed to validate this file giving the above message both times once after running 3 minutes and then after running 6 minutes, I went to the vault and from there started a manual verification of the same file. This "completed successfully" in just 3.5 minutes.

Amazingly the log doesn't even document which file or archive the validation ran against.

Worryingly, a similar validation from the vault of an almost identical also full backup from the same plan completed successfully after 10 minutes, while the actual backups which created both files took 3.5 hours to complete.

I have little confidence this software is operating correctly.

Hello Alan Wilkinson,

Thank you for your post. I will definitely help you with this.

I have checked with our Expert and Quality Assurance teams about this issue and I was told, that this is a known problem in our software. We are currently working on a fix for this, and it will be available in the next update of Acronis Backup and Recovery 10.

As a workaround, I suggest creating a separate validation task for your backup.

Please accept my apologies for the inconvenience.

If you have any other questions, please let me know.