Granular Dump Backup Restart Using Phase Offset Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data replication and backup systems face challenges in restarting a dump backup process at a precise granularity due to the lack of detailed restart points, often relying on unavailable file histories, leading to redundant workflows and incomplete backups.
Innovation Solution
Implementing a phase offset table and offset map to track directory and file transfer phases, using a bytes written value to identify the exact restart point within the backup process, allowing for precise restarts without relying on file history information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the dump backup is restarted from a particular phase, then the backup process can be resumed, but redundant backup workflow occurs because already transferred directories and/or files are transferred again
Solution Approach 1:
The backup process is segmented into distinct phases (backup data identification phase, metafile phase, directory transfer phase, file transfer phase), and within each phase, further segmentation occurs at the granularity of individual directories and files. This segmentation enables the system to identify and resume from the specific point of failure rather than restarting the entire backup process, thereby eliminating redundant workflows while maintaining reliable restart capability.
2Reliability
If the dump backup restartability relies on file history creation, then restart information can be tracked, but the solution fails when file history is not available
Solution Approach 1:
The system performs self-service by automatically maintaining phase offset tables and offset maps during the backup process itself, without requiring external file history creation. These data structures are updated incrementally as each directory and file is processed, enabling the system to track its own state and resume from the exact point of interruption. This self-service approach ensures restartability is always available regardless of whether file history is created.
3Ease of operation
If the dump backup cannot be restarted at a granularity of where it aborted, then restart is simpler, but redundant backup workflow occurs requiring complete re-transfer of directories and/or files
Solution Approach 1:
The system performs preliminary actions by maintaining phase offset tables and offset maps throughout the backup process, continuously recording the state of each directory and file as it is processed. This preliminary tracking of backup progress enables the system to quickly identify the exact restart point when an abort occurs, avoiding the need to re-transfer already backed up data and eliminating time waste while keeping the restart mechanism simple and automated.
Data Source
AI summary
One or more techniques and/or computing devices are provided for restarting a dump backup. For example, a phase offset table is used to track a directory transfer phase offset and a file transfer phase offset of phases of a dump backup. An offset map is used to map inodes, of data being backed up, to offsets within a backup image within which the data is being backed up. The phase offset table and/or the offset map are evaluated using a bytes written value to identify a phase during which the dump backup aborted and to identify a restart point. Accordingly, the dump backup is restarted at the restart point. In this way, the dump backup may be restarted during any phase and/or at any point using the bytes written value, the phase offset table, and the offset map without the need for additional information such as a file history.