Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 7

...

Quite simply, it means that data that was written to the backup or image file is not the same as is read back from the same file.

Errors of this type are symptomatic of a computer system with a marginal hardware problem. The most likely suspect is your backup media - but memory and motherboard faults can also cause this issue.

How does Macrium Reflect check the data integrity?

...

Why can't Macrium Reflect validate the data as it is written?

It isn't possible to verify the file as it is written because the buffers and caches in the write process aren't flushed to disk until after the file is closed. The only way to verify data integrity is to close the file at the end of the backup process and then read the file back. It's possible to do this automatically by selecting the 'Auto-Verify' option in the Advanced backup definition properties.

Include+
scrollEditorUrl/display/KNOW/._HOW_VERIFY_WORKS+v7
scrollEditorDisplayTitle_HOW_VERIFY_WORKS
scrollPageId0A03050401601CD91F3766A8376967B8

Why don't I have any other problems with my system?

...