Corruption-Resistant Backup Policy for Data Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage backup solutions using differential backups are prone to irretrievable data loss due to corruption, as even small data corruption can affect multiple backups sharing the same data.
Innovation Solution
Implementing a backup policy that generates complete, independent versions of data objects at a destination data storage system from differential backups, with the option to store these versions at new storage locations, thereby isolating corrupted data to only affect backups since the last full copy was made.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If differential backups are used to update remote storage facilities, then resource consumption is reduced, but data corruption can affect multiple backups sharing the same data
Solution Approach 1:
The backup system segments data into different storage locations with independent copies. The destination storage facility creates separate storage locations for backup data, ensuring that corruption in one location does not affect other independent copies. This segmentation isolates the impact of corrupted data to only those backups received since the last full copy was made.
Solution Approach 2:
The system creates multiple independent copies of backup data at different storage locations. When a full backup is performed, complete copies are made at the destination, and subsequent differential backups are applied to create additional independent versions. This copying ensures that if one copy is corrupted, other independent copies remain intact and can be used for restoration.
2Adaptability or versatility
If complete versions of data objects are stored at the destination, then data recovery options are improved, but storage space requirements increase
Solution Approach 1:
The system performs preliminary full backups at the destination storage facility before differential backups are applied. This preliminary action establishes a baseline complete version that can be used for recovery. The backup policy specifies when complete versions are generated, ensuring that sufficient recovery points are maintained without unnecessarily storing every possible version.
Solution Approach 2:
The system changes the storage parameter from storing only differential changes to storing complete versions at specific intervals. By controlling the frequency and timing of full backup operations, the system optimizes the balance between having sufficient recovery options and minimizing storage space consumption. The backup policy parameters can be adjusted to control this trade-off.
Data Source
AI summary
Improved techniques for managing backups of data objects involve specifying a policy for generating complete versions of a data object at a destination data storage system (destination) from differential backups of the data object previously received. The complete versions are independent of the previous differential backups and any complete versions of the data object that preceded them. A backup policy specifies when such a complete version is to be generated. Along these lines, a destination receives differential backups of a data object stored on a source. The destination may store these differential backups at the destination. However, according to the backup policy that specifies that a complete version of a data object is generated after the destination receives a certain number of differential backups, the destination creates a complete copy of the data of the data object at new storage locations at the destination distinct from previous storage locations.