FreeFileSync Forum

In the case of files unknowly corrupted on one side, "Compare File time and size" would not trigger copying the bad files to the other side in a sync, becasue the modify timestamp are the same on both sides, and Versioning only store the old version of updated files and deleted files, it do ...

In the case of files unknowly corrupted on one side, "Compare File time and size" would not trigger copying the bad files to the other side in a sync, becasue the modify timestamp are the same on both sides, and Versioning only store the old version of updated files and deleted files, it do not ...

You can make use of the file versioning function in FreeFIleSync, to keep old version of files to a chosen path with timestamp folder of sync time during file sync, this way you can still recover the uncorrupted files in the revision folder in case of files unknowly corrupted.

Manual: File ...

The best practice to detect bit rot is to create a checksum file for the known good copy of files, and verify the files to detect bit rot, or create parity files for known good copy of files to check and repair corrupted data in files.

Since FreeFileSync main purpose is for files sync, I think it ...

That is a great point. My current process is to test both files to see which one is working properly and keep that one. I have had one experience like this with FFS, where two files were different in the File Content initial "scan" where both of the directories both had a ".Trash-1000" folders in ...

I am new to the backup life style. I heard about bit rot being a really low possibility (like extremely low) for files. However, I would like to just try to mitigate that if possible at all. Would using the "Compare File Content" comparing the files bit-by-bit be a good way to detect bit rot between ...