Virtual Machine Recovery Block Segmentation and Copy-on-Write Thresholds
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current backup systems face challenges in efficiently copying large data volumes while an operating system is actively writing to the source volume, leading to performance issues and increased storage requirements due to the need for copy-on-write mode, which can result in prolonged copying times and potential storage failures.
Innovation Solution
The system implements a method to copy a source volume to a target volume by designating blocks, identifying written blocks, and adjusting the copying process based on a threshold, allowing the operating system to enter copy-on-write mode only when necessary, thereby reducing the time spent in this mode and optimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If copy-on-write mode is used to copy large data volumes while the operating system is actively writing to the source volume, then data consistency is improved, but copying time increases significantly
Solution Approach 1:
The patent divides the source volume into multiple blocks and processes them in segments. Instead of copying the entire volume in copy-on-write mode, the system identifies and copies individual blocks that have been written to, processing them in manageable segments. This segmentation allows the copying process to be more efficient and less time-consuming while maintaining data consistency.
Solution Approach 2:
The patent implements preliminary action by tracking and identifying written blocks before initiating the copy operation. The system monitors the source volume to identify which blocks have been modified, allowing it to prepare a targeted copy list in advance. This preliminary identification enables the copying process to focus only on necessary blocks, reducing overall copying time while ensuring consistency.
2Reliability
If copy-on-write mode is used to ensure data consistency during active writing, then reliability is improved, but storage requirements increase
Solution Approach 1:
The patent extracts only the necessary written blocks from the source volume for copying, rather than copying the entire volume or all blocks. By identifying and extracting only those blocks that have been modified, the system reduces storage requirements while maintaining data consistency. This selective extraction approach minimizes the storage overhead associated with copy-on-write operations.
Solution Approach 2:
The patent applies local quality by treating different blocks of the source volume differently based on their write status. Instead of uniformly copying all blocks in copy-on-write mode, the system identifies blocks with different characteristics (written vs. unwritten) and processes them accordingly. This localized approach optimizes storage usage by focusing resources only on blocks that require copying.
3Reliability
If the operating system enters copy-on-write mode frequently to maintain consistency, then data integrity is improved, but system performance deteriorates
Solution Approach 1:
The patent implements feedback mechanisms by continuously monitoring the source volume to identify written blocks. The system uses this feedback information to dynamically adjust the copying process, entering copy-on-write mode only when necessary based on actual write activity. This feedback-driven approach minimizes the frequency of copy-on-write mode transitions, thereby reducing performance impact while maintaining data integrity.
Solution Approach 2:
The patent applies dynamics by making the copy-on-write mode entry dynamic rather than static. Instead of entering copy-on-write mode at fixed intervals or for the entire copying process, the system dynamically determines when to enter this mode based on real-time identification of written blocks. This dynamic approach allows the system to maintain data integrity while minimizing performance degradation by activating copy-on-write only when necessary.
Data Source
AI summary
The Prioritization and Source-Nonspecific Based Virtual Machine Recovery Apparatuses, Methods and Systems (“MBR”) transforms backup configuration request, restore request inputs via MBR components into backup configuration response, restore response outputs. A backup configuration request to configure backups of a data storage volume of a source device is obtained. A paired backup device is determined. A recovery prioritization index is generated by determining a recovery priority ranking for each selected for backup data block of the data storage volume. A discrepancy hash for each selected for backup data block of the data storage volume that is available from at least one of a set of source-nonspecific locations is precalculated. The recovery prioritization index and the discrepancy hashes are periodically updated to account for data block use. Backup data including at least one of the recovery prioritization index and the discrepancy hashes is sent from the source device to the backup device.