Compare by File Content as a more reliable alternative to VerifyCopiedFiles

[diegopau]

Hi,

I have read some of the posts about the VerifyCopiedFiles option to do a verification after the sync/mirror is done and I see the note "corruption may be hidden by deceptively reading valid data from various buffers in the application and hardware stack".

My question is: if the "Compare by File content" uses the same method or relies on the same OS systems to do the bit by bit verification, would it be a better option to then do the full mirror, turn off the computer, turn on the computer and do a "Compare by File content" between source and destination? it seems like a possible way to make sure that those buffers are flushed and get the same verification process done? (obviously with the distadvantage of having to restart your computer, but in my case it would be for a one time operation)

[Plerry]

If you are that paranoid/concerned about file corruption in combination with reading from memory/buffer instead of from disk, your method would work.

Rebooting between the sync and successive Compare by Content is a sufficient, but not necessary method to assure the memory/buffer is flushed.
For other methods see https://www.google.com/search?q=flush+memory+buffer

[diegopau]

Thanks! Good to know

[therube]

Anything every come of that google search?
(Some, perhaps much of the highest hits are outright wrong, btw.)

I've got something I came up with, but I'm not even certain that is correct, In order to "correctly" benchmark, YOU MUST CLEAR CACHE.