Logical Object Pointer for Seamless Data Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data migration in cloud storage systems often results in performance degradation due to the high load on metadata servers from updating location pointers and inconsistent physical data layouts across storage tiers, leading to increased complexity and overhead during large-scale migrations.
Innovation Solution
Maintaining a logical object pointer in the metadata tier that remains unchanged during migration, allowing data to be accessed from both source and destination storage components, and optimizing read/write operations based on storage attributes to minimize load on the metadata tier.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If location pointers in the metadata tier are updated whenever data migration occurs, then the global namespace is maintained and data accessibility is preserved, but the metadata tier experiences severe performance degradation and high processing load
Solution Approach 1:
The patent segments the namespace management by introducing a separate namespace tier that maintains namespace mappings independently from the metadata tier. This segmentation allows the metadata tier to focus on data management while the namespace tier handles location mapping, thereby resolving the performance degradation caused by frequent metadata updates during migration.
Solution Approach 2:
The patent introduces a namespace tier as an intermediary layer between the client and the metadata tier. This intermediary maintains the global namespace mappings and handles location pointer updates during migration, protecting the metadata tier from high processing loads while ensuring data accessibility is maintained.
2Productivity
If data is migrated from one storage location to another, then storage capacity demands are met and cost optimization is achieved, but the physical layout inconsistency across storage tiers increases system complexity
Solution Approach 1:
The patent creates a logical copy of the namespace mapping in the namespace tier that mirrors the physical data locations. This logical copying allows the system to track physical layout changes across storage tiers without requiring the metadata tier to maintain complex consistency information, thereby reducing system complexity while enabling flexible data migration.
3Productivity
If large-scale data migration is performed, then storage optimization and cost reduction are achieved, but the processing load on the metadata tier increases significantly
Solution Approach 1:
The patent extracts the namespace mapping functionality from the metadata tier and places it in a dedicated namespace tier. This extraction removes the burden of maintaining location pointers during large-scale migration from the metadata tier, allowing efficient data migration without significant processing load on the metadata tier while maintaining global namespace consistency.
Data Source
AI summary
Techniques are described for migrating data between storage components. In one or more embodiments, a storage system receives a request to migrate data from a first storage component to a second storage component. Responsive to the request, the storage system initiates migration of the data from the first storage component to the second storage component. While migration is ongoing, the storage system may receive a request to access the data. Responsive to receiving a write request, the storage system executes the write request on the second storage component without executing the write request on the first storage component. Responsive to determining that the second request is a read request, the storage system selects one of the first storage component or the second storage component to execute the read request based on a first attribute associated with the first storage component and/or a second attribute associated with the second storage component.