Hybrid Storage Block Replication via Volume Manager
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In hybrid storage environments, traditional storage block replication systems are unaware of file-level cloud tiering, leading to out-of-sync local data during asynchronous replication, which can result in inaccessible cloud objects in case of failures, especially when cloud storage provides a single data copy for both source and target.
Innovation Solution
The method involves a system and process for storage block replication that includes a volume manager module to receive requests for modifying cloud objects, store instructions, determine replication completion, and modify or delete cloud objects accordingly, ensuring data redundancy and accessibility by tracking replication operations and timestamps in a cloud modification database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cloud storage is used for block storage media in a hybrid storage solution, then storage cost efficiency is improved, but data accessibility and reliability deteriorate during replication operations
Solution Approach 1:
The system performs preliminary actions by storing modification instructions in a queue before actual cloud object modifications occur. This allows the replication process to be prepared and tracked in advance, ensuring that modifications are only applied to cloud objects after successful replication, thereby maintaining data accessibility and reliability while managing complexity.
Solution Approach 2:
A volume manager module is introduced as an intermediary between the replication process and cloud object modifications. This intermediary coordinates the replication operations, manages the queue of modification instructions, and ensures proper sequencing, thereby improving reliability without significantly increasing overall system complexity.
2Productivity
If asynchronous replication is used in hybrid storage environments, then replication flexibility is improved, but data synchronization deteriorates
Solution Approach 1:
The system implements feedback mechanisms by tracking replication operation status and using this information to control when cloud object modifications occur. The volume manager monitors replication progress and only permits cloud object modifications after confirming successful replication, thereby maintaining data synchronization while preserving asynchronous replication flexibility.
Solution Approach 2:
The patent replaces traditional mechanical synchronization mechanisms with a software-based queue system that tracks replication operations. This substitution allows asynchronous replication to maintain flexibility while ensuring synchronization through logical control rather than mechanical timing, improving both productivity and reliability.
3Speed
If cloud objects are modified immediately during replication, then replication speed is improved, but data integrity deteriorates
Solution Approach 1:
Modification instructions are stored in advance in a queue rather than executing immediately. This preliminary action allows the system to prepare modifications while maintaining data integrity by ensuring replication success before applying changes, thus balancing speed and reliability.
Solution Approach 2:
The system provides beforehand cushioning by implementing a buffer queue that absorbs modification requests. This cushioning mechanism prevents premature cloud object modifications that could compromise data integrity, while still enabling fast replication by processing modifications as soon as they are safe to apply.
Data Source
AI summary
The disclosed computer-implemented method for storage block replication in a hybrid storage environment may include receiving a request associated with a data source being replicated to modify a cloud object, storing an instruction for modifying the cloud object, determining that a replication operation for the source has completed, and modifying the cloud object and deleting the instruction for modifying the cloud object in response to determining that the replication operation has completed. In some examples, the request to modify the cloud object may include deleting the cloud object. Various other methods, systems, and computer-readable media are also disclosed.