Hi,
When I noticed that FFS creates database files on the source drive volume an idea popped up in my head.
It would be nice to have a feature in FFS that calculates the checksum of all the files and their "last modified date" time stamp on the source drive and then stores this information in the db file.
Before overwriting files on the backup drive FFS could automagically search the database for the date stamps of the previous backup session so it can detect files that have changed but that did not change their "last modified" time stamp.
FFS could pop up a dialog to warn the user that this could be a sign of data corruption or infection by a computer virus.
After updating the backup volume FFS could compare the checksums of the files it just copied and check for discrepancies with the files on the source drive.
This would be a second integrity check to fight against data corruption due to hardware failure.
Backup would be more time consuming but data integrity would be guaranteed...
Feature request: an idea for file corruption detection and prevention
- Posts: 1
- Joined: 16 Aug 2013