Data Migration Geometry Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques fail to accurately handle discrepancies in device geometry parameters when migrating data from one storage system to another with different geometries, leading to potential data corruption and undesirable processing outcomes such as ignoring or reinitializing the target device's descriptor.
Innovation Solution
A method that involves receiving source and target device descriptors, translating the partition definition structure to match the target device geometry, performing data validation checks, and using a data pull technique to migrate data, ensuring compatibility and accuracy across different device geometries.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is migrated from a source device with first geometry to a target device with second geometry using existing techniques, then data transfer is performed, but device geometry parameter discrepancies cause data corruption or descriptor reinitialization
Solution Approach 1:
The patent transforms partition location parameters from cylinder-based coordinates to block-based offsets by applying geometric parameter transformations. The source device geometry parameters (cylinders, heads, sectors per track) are converted to block offsets using mathematical calculations that account for the target device's different geometry parameters, ensuring accurate data placement regardless of geometry differences
Solution Approach 2:
The patent introduces an intermediary data structure (migration map or translation layer) that mediates between the source device descriptor with first geometry and the target device descriptor with second geometry. This intermediary structure stores the transformed block offset information, allowing the migration process to handle geometry discrepancies without corrupting data or reinitializing descriptors
2Loss of information
If device geometry parameters are stored in the target device descriptor from the source device, then partition information is preserved, but geometry discrepancies arise when operations modify the partition definition structure
Solution Approach 1:
Instead of storing source device geometry parameters in the target device descriptor (the conventional approach), the patent inverts the approach by storing transformed block offset parameters that are independent of source geometry. The partition definition structure is rewritten with new parameters (block offsets) that directly reference target device geometry, eliminating the geometry parameter discrepancy problem
Data Source
AI summary
Described are techniques for migrating data from a source device to a target device. A source device descriptor of the source device including source device geometry parameters and a source device partition definition structure is received. Target device geometry parameters are received. The source partition definition structure is translated and a mapped partition definition structure in accordance with the target device geometry parameters is generated. A target device descriptor including the target device geometry parameters and the mapped partition definition structure is generated. The target device descriptor is stored on the target device. Data for one or more partitions of the source device is migrated to the target device.


