Virtual Service Layer for Asynchronous Journal Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data protection systems face challenges in maintaining continuous data protection by keeping pace with high data transaction rates at production sites without slowing them down, leading to potential backlogs and system shutdowns.
Innovation Solution
A virtual service layer is introduced to intercept I/O operations and split them for journal-based replication, enabling dynamic adaptation to changing transaction rates and ensuring data consistency across multiple sites, including geographic locations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If journaling is used to enable continuous data protection and rollback capability, then data recovery flexibility is improved, but system overhead increases and may force production site shutdown at high transaction rates
Solution Approach 1:
A virtual service layer is introduced as an intermediary between the production site and backup site. This layer intercepts I/O operations, performs journaling locally, and manages replication asynchronously, thereby isolating the overhead of continuous data protection from the production site while maintaining data recovery flexibility.
Solution Approach 2:
The data protection system is segmented into distinct functional layers: the production site generates data, the virtual service layer handles journaling and replication coordination, and the backup site stores replicated data. This segmentation allows each component to operate independently at its own pace, preventing backup overhead from impacting production performance.
2Reliability
If the backup site processes all journaling operations synchronously with the production site, then data consistency is improved, but production site performance deteriorates due to forced slowdown
Solution Approach 1:
The system dynamically adapts the replication pace to match production transaction rates. The virtual service layer buffers journal entries locally and transmits them to the backup site at varying rates based on production workload, allowing the system to maintain data consistency while accommodating fluctuating production performance requirements.
Solution Approach 2:
The virtual service layer performs preliminary journaling and buffering of data changes before replication to the backup site. This preliminary action allows the production site to commit transactions immediately while the backup site processes replication asynchronously, ensuring data consistency without forcing production slowdown.
3Device complexity
If the backup site operates at a slower pace than production transactions, then backup system simplicity is improved, but data transaction backlog increases leading to system failure
Solution Approach 1:
The virtual service layer implements feedback mechanisms that monitor the state of journal buffers and replication progress. When the backup site falls behind, the system dynamically adjusts replication pacing and buffer management to prevent backlog accumulation, ensuring continuous data protection while maintaining backup system simplicity through automated control.
Data Source
AI summary
A method, system and computer program product for enabling a virtual service layer to consume a storage medium at a first site and map the storage medium as one or more virtual storage volumes, enabling the virtual service layer to present the one or more virtual storage volumes for consumption at the first site, enabling a splitter of the virtual service layer to intercept I/O written to the one or more virtual storage volumes, splitting intercepted I/O to a journal based replication appliance, enabling the virtual storage volumes to be accessible at a second site, wherein the one or more the virtual storage volume are mirrored at the second site by the virtual service layer; and replicating IO from either the first site or the second site to a third site.