In Situ Virtual Volume Conversion via Metadata Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems face inefficiencies in converting virtual volumes with configuration changes, leading to increased storage space allocation and loss of features like snapshots and replication during conversion, making disaster recovery challenging.
Innovation Solution
In situ virtual volume conversion method, where configuration changes are applied by modifying metadata and using dataless write requests processed by the OS kernel to update data without creating a new volume, ensuring transparent conversion during I/O operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a new virtual volume is created to store converted data, then data conversion can be performed, but additional storage space is allocated and feature consistency is lost
Solution Approach 1:
The patent implements in-situ conversion by nesting the conversion process within the existing virtual volume structure. The target virtual volume is converted directly in place by updating metadata and using dataless writes, rather than creating a separate container. This nesting approach eliminates the need for additional storage space while maintaining all original features including snapshots and replication.
Solution Approach 2:
The patent uses metadata copying and dataless write operations to replicate the effect of data conversion without physically moving data. By copying updated metadata back to the storage system and using dataless writes to trigger conversion, the system achieves feature consistency without allocating new volume space.
2Adaptability or versatility
If virtual volume conversion is performed, then configuration settings can be changed, but snapshots and replication features are lost during conversion
Solution Approach 1:
The patent performs preliminary actions by updating the virtual volume metadata before actual data conversion occurs. The metadata is modified to reflect new configuration settings, and dataless write requests are prepared in advance. This preliminary metadata update ensures that snapshots and replication features are preserved throughout the conversion process, maintaining disaster recovery protection.
Solution Approach 2:
The system uses feedback mechanisms where the storage system processes dataless write requests and returns status information. This feedback loop ensures that conversion operations complete successfully while maintaining feature consistency. The metadata updates are verified through feedback from the storage system, confirming that snapshots and replication remain intact.
3Ease of operation
If data conversion is performed during I/O operations, then transparent conversion is achieved, but I/O performance may be affected
Solution Approach 1:
The patent implements periodic action by processing conversion operations in background threads that periodically perform dataless writes during normal I/O operations. This periodic background processing allows the conversion to proceed transparently without blocking host I/O operations, maintaining both transparency and performance by separating conversion tasks from I/O processing.
Data Source
AI summary
A technique includes changing a configuration setting of a virtual volume of data stored in a storage system. The technique includes converting data of the virtual volume in place to reflect the changing of the configuration setting.