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 same folders?
If so, would I run a "Compare File Content" and then a "Compare File time and size" to make sure everything is properly backed up?
Best way to use FFS to detect and mitigate bit rot?
- Posts: 2
- Joined: 28 Mar 2025
-
- Posts: 2607
- Joined: 22 Aug 2012
If you Compare identically named, sized and timestamped files by File Content and a difference would be detected, how would you know which of the two (left or right) is suffering from bit-rot?
- Posts: 2
- Joined: 28 Mar 2025
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 them. Once I deleted the ".Trash-1000" from both the scan came back clean.
However, I am more than happy to hear about a better way to think about this. My current workflow is where I backup files in a flow: Drive 1 -> Drive 2 -> Drive 3 -> Drive X. As such, if there was a rotted file, my worry is that it would pass down to all of my other drives.
However, I am more than happy to hear about a better way to think about this. My current workflow is where I backup files in a flow: Drive 1 -> Drive 2 -> Drive 3 -> Drive X. As such, if there was a rotted file, my worry is that it would pass down to all of my other drives.
