This can happen if the files are updated on the right. SyncToy 2.0 appears not to sync deleted files when I have the sync option set to 'Echo'Ī. If you are looking for end to end checks, you would have to do an MD5 hash of the original file, then do an MD5 hash of the written file, then compare them. With luck your unchanged/non-updated backup will still be OK" You might be better off leaving things alone till you discover the corruption at a later date (when trying to open it, maybe). If the file can still actually be read (copied) you will then overwite your OK backup with a corrupt copy :shock: This would - if you set the above options - trigger a copy (assuming the rules are set that way). Imagine if the size and LastMod stamp are unchanged (same on both Source & Dest) but the Source file is corrupt and now produces a different hash value. And in any case, what if they are different? This only means the contents have changed, not necessarily that one of the files is corrupt (example: TrueCryot containers never change size or LastMod stamp, but the hash value might - indicating 'changed contents', which might be perfectly 'valid' changes)īut be aware that this may in fact cause you grief. There is no list of what the hash values were last time. But this only compares the hash values of the files on either side, 'on the fly'. "You can switch on hashing ('slower but more reliable method of file change detection') as per the options on Modify > Expert > Compare Options page. Whether this makes sense to do depends, here is a clip from their forum: I recommend SyncBack Pro, it has a verify option which does MD5 checks hashes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |