Data Replication Storage Resizing Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data replication systems face IO failures due to inconsistent storage size changes between source and destination file systems, as they lack synchronization mechanisms for storage area resizing, leading to potential operation failures and rollback complexities.
Innovation Solution
Implementing state machines with communication functions on both the source and destination file systems to synchronize storage area resizing operations, ensuring that data replication only proceeds once both sides have completed size changes, and facilitating rollback operations when necessary.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If storage area sizes are automatically expanded or shrunk based on user data usage, then storage flexibility is improved, but storage size inconsistency between source and destination file systems occurs leading to IO failures
Solution Approach 1:
The patent implements feedback mechanisms where the source file system monitors storage area size changes and sends notifications to the destination file system. The destination file system responds by adjusting its storage area size accordingly, creating a closed-loop control system that maintains size consistency while allowing automatic adaptation to user data usage patterns.
Solution Approach 2:
The patent introduces an intermediary coordination mechanism between the source and destination file systems. This intermediary layer receives size change requests from the source, processes them through a standardized protocol, and ensures the destination applies corresponding changes, preventing size inconsistency without restricting storage flexibility.
2Reliability
If synchronous replication is implemented to ensure zero data loss, then data security is improved, but complexity of storage size synchronization increases
Solution Approach 1:
The patent segments the storage size synchronization process into distinct, manageable components: size change detection at the source, notification message generation, message transmission, and size adjustment at the destination. Each component handles a specific aspect of the synchronization task, reducing overall system complexity while maintaining data security through synchronous replication.
Solution Approach 2:
The patent implements preliminary actions by detecting storage size changes at the source file system before they affect data replication operations. By proactively notifying the destination file system and adjusting its storage area size in advance, the system prevents potential IO failures and maintains synchronization complexity at a manageable level.
3Ease of operation
If storage area size changes are made independently at source and destination, then operational autonomy is improved, but storage size mismatch occurs causing IO failures
Solution Approach 1:
The patent merges the storage size management operations of the source and destination file systems into a coordinated process. While each system retains operational autonomy for data operations, size changes are combined through a unified notification and response mechanism, ensuring both systems adjust their storage areas consistently without requiring centralized control.
Data Source
AI summary
Techniques for data replication involve: in response to a first source state machine associated with a source file system being booted up, booting up a second source state machine associated with the source file system, the first source state machine performing a first operation for resizing a first storage area of data for replication from the source file system; transmitting a resizing message from the second source state machine to a destination file system, to enable the destination file system to perform a second operation for resizing a second storage area for storing the data to be replicated into the destination file system; and in response to the first operation and the second operation being successfully performed, enabling the data for replication from the source file system to be replicated into the destination file system.