Backup Validity Check for Data Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional backup solutions do not validate data during incremental or full backups, leading to potential corruption of user data, which can result in undetected corrupted files being stored and lost over time, especially in large collections like picture files.
Innovation Solution
A data backup method that checks the validity of files during both incremental and full backups by comparing file format parameters against known standards, notifying users of corrupted files and allowing for restoration from previous backups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional backup solutions are used without validity checks, then backup speed and simplicity are maintained, but data integrity deteriorates as corrupted files are unknowingly backed up and stored
Solution Approach 1:
The patent applies preliminary action by performing validity checks on files before they are backed up. The system detects corrupted or invalid files and prevents them from being included in the backup process, thereby ensuring data integrity before the backup operation commences. This proactive approach catches data quality issues early, preventing propagation of corrupted data across multiple backup cycles.
Solution Approach 2:
The patent implements feedback mechanisms by monitoring the validity of files during the backup process and providing information about corrupted files to the user. The system feeds back status information regarding file validity, allowing users to take corrective actions. This feedback loop ensures that only valid files are backed up while maintaining awareness of data quality issues.
2Reliability
If validity checks are performed on all files during backup, then data integrity is improved, but backup time and processing resources increase
Solution Approach 1:
The patent applies local quality by performing validity checks selectively rather than uniformly on all files. The system identifies and validates only those files that are likely to be corrupted or are critical to the backup process, rather than subjecting every single file to comprehensive validation. This targeted approach maintains data integrity for important files while reducing overall processing time.
Solution Approach 2:
The patent employs partial action by implementing validity checks on a subset of files during backup rather than all files. The system performs comprehensive validation on new or modified files while using lighter validation or skipping validation on files that have been recently validated. This partial validation strategy provides sufficient data integrity protection without the full time cost of validating every file.
3Loss of information
If corrupted files are not detected during backup, then backup simplicity is maintained, but data loss increases as corrupted files replace original data over time
Solution Approach 1:
The patent applies self-service by enabling the backup system to automatically detect and identify corrupted files without requiring manual user intervention. The system performs self-validation of files during the backup process, automatically flagging corrupted or invalid files. This automated self-check mechanism prevents data loss while maintaining operational simplicity, as users do not need to manually verify file integrity.
Solution Approach 2:
The patent implements feedback by providing users with information about detected corrupted files during the backup process. The system feeds back status information regarding file validity, allowing users to take corrective actions. This feedback mechanism maintains ease of operation by automatically handling detection while keeping users informed, preventing data loss without requiring complex manual intervention.
Data Source
AI summary
A data backup application checks validity of data being backed up during an incremental or a full backup. In case of the file backup, the full backup checks the validity of data during the backup, because in case of data corruption the user will not have any original data since no data has been backed up yet. In case of the incremental backup, only the new files or the files that have changed compared to the last backup are now backed up. All new and modified files can be checked for validity by comparing internal format of the user files against a corresponding file format standard. If corrupted files are detected among the modified files, the user is notified.