Storage Volume Tracking During Data Migration Rollback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data migration between storage systems can be inefficient, leading to resource-intensive rollback processes due to unsynchronized changes between source and destination storage volumes, causing delays and high latency in I/O operations.
Innovation Solution
The use of tracking data structures that track changes made to data portions in destination storage volumes during migration, allowing for selective rollback of only changed data portions, reducing the need for full copies and minimizing resource consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full data copies are performed during rollback operations, then data consistency is restored, but resource consumption and time delay increase significantly
Solution Approach 1:
The patent extracts only the changed data portions from the destination storage volume using tracking data structures, rather than copying entire volumes. This selective extraction approach restores data consistency while minimizing resource consumption and time delay during rollback operations.
Solution Approach 2:
The patent segments the rollback process into identifying changed portions and transferring only those segments. Tracking data structures divide the storage volume into trackable portions, allowing the system to process and restore only the necessary segments rather than handling complete volume copies.
2Measurement precision
If tracking data structures are activated for all destination storage volumes, then changed data can be precisely identified, but system complexity and overhead increase
Solution Approach 1:
The patent applies tracking data structures selectively rather than universally. Tracking is activated only for destination storage volumes that require rollback capability, avoiding unnecessary overhead for volumes that don't need this functionality while maintaining precise changed data identification where needed.
3Reliability
If I/O accesses are blocked during data migration, then data consistency is maintained, but operational productivity decreases
Solution Approach 1:
The patent segments I/O blocking by storage volume, allowing I/O operations to continue on source storage volumes that have completed migration while blocking only those volumes still in progress. This selective segmentation maintains data consistency for migrated volumes without completely halting system productivity.
Data Source
AI summary
In some examples, a system transfers, in a first transfer operation, data of a first storage volume of a first storage location to a second storage volume for a second storage location. Responsive to a completion of the transfer of data of the first storage volume to the second storage volume, the system activates tracking information to track changes to data portions of the second storage volume, the tracking information comprising a plurality of indicators that map to respective different data portions of the second storage volume. As part of a second transfer operation following the first transfer operation, the system transfers changed data indicated by the tracking information from the second storage volume to the first storage volume, without transferring unchanged data in the second storage volume to the first storage volume.