Checkpoint Restart Backup System Partial Save Sets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In backup processes, interrupted data is often discarded as potentially corrupt or inconsistent, leading to inefficiencies and the need to restart from the beginning, which is not feasible within the short time windows allocated for backups, especially when large amounts of data are involved.
Innovation Solution
Implementing a system that allows for restarting an interrupted backup process from the point of failure by creating and managing partial save sets, which include metadata for successfully saved data, enabling the backup to resume from a checkpoint and linking subsequent partial save sets to previous ones, ensuring data integrity and reducing the need for full reprocessing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the backup process is restarted from the beginning after interruption, then data integrity is ensured, but backup time increases significantly and productivity decreases
Solution Approach 1:
The system performs preliminary actions by creating checkpoints during the backup process and storing metadata about successfully backed up data. When interruption occurs, these preliminary checkpoint records enable the backup to resume from the last valid checkpoint rather than restarting from the beginning, thus maintaining data integrity while improving productivity
Solution Approach 2:
The backup process is segmented into multiple independent units with defined checkpoints. Each segment represents a portion of data that can be independently tracked and resumed. By dividing the backup into segments with checkpoint markers, the system can restart from a specific segment rather than the entire backup, resolving the contradiction between reliability and productivity
2Reliability
If the backup process is restarted from the beginning after interruption, then consistency is maintained, but time consumption increases beyond the allocated window
Solution Approach 1:
Checkpoints and metadata are prepared in advance during normal backup operations, recording the state of successfully backed up data. Upon interruption, this preliminary information allows immediate resumption from the last valid checkpoint, maintaining consistency while avoiding time loss from full re-execution
Solution Approach 2:
The backup process maintains continuity by preserving the state of successfully completed portions through checkpoint metadata. Instead of interrupting and restarting the entire process, the system continues useful action by resuming from where it left off, thereby maintaining consistency without excessive time consumption
3Reliability
If large amounts of data are discarded due to interruption, then data consistency is preserved, but loss of substance increases
Solution Approach 1:
The system selectively discards only the incomplete or potentially corrupt portion of the backup after interruption, while recovering and preserving all previously successfully backed up data through checkpoint records. This selective discarding and recovering approach maintains consistency while minimizing data loss
Solution Approach 2:
The system extracts and separates the successfully completed backup portions from the incomplete portion using checkpoint metadata. By taking out only the necessary incomplete segment for re-processing, the system preserves the majority of backed up data, reducing loss of substance while maintaining consistency
Data Source
AI summary
A method for restarting backup including receiving an indication of an interruption to a backup process, saving data backed up prior to the interruption as a partial save set, and upon restart of the backup process, saving subsequently backed data in one or more subsequent partial save sets linked to a first partial save set.