Snapshot Hardening in Journal-Based Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data protection systems face challenges in maintaining continuous data protection, particularly in keeping pace with high data transaction rates at production sites without slowing them down, leading to potential data backlog and system shutdowns.
Innovation Solution
A method and system for hardening snapshots in a journal-based replication environment by periodically checking the replication system's status, including splitter functionality, virus scans, application consistency, and configuration correctness, to denote which snapshots are acceptable and store this information as metadata, ensuring data integrity and preventing system instability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If continuous data protection uses journaling to keep pace with data transactions at the backup site, then data protection capability is improved, but system complexity and overhead increase significantly
Solution Approach 1:
The patent extracts the validation and consistency check functions from the main journaling data protection flow. By separating these validation tasks into independent snapshot hardening operations, the system reduces the overhead on the primary journaling mechanism while maintaining data protection capability. The validation logic is taken out as a distinct process that operates on snapshots rather than interfering with the continuous journaling operation.
Solution Approach 2:
The patent applies preliminary action by performing validation checks and hardening snapshots before they are fully integrated into the replication stream. By pre-validating snapshot consistency, checking splitter functionality, and verifying data integrity in advance, the system prevents problematic snapshots from causing issues later in the replication process, thereby reducing overall system complexity and overhead.
2Reliability
If the backup site processes all data transactions from the production site, then data replication completeness is improved, but processing speed and responsiveness deteriorate due to backlog
Solution Approach 1:
The patent applies partial action by not requiring the backup site to process and validate every single data transaction in real-time. Instead, it periodically validates snapshots at strategic points, performing sufficient (but not excessive) validation to ensure data protection completeness. This selective validation approach maintains replication completeness while preventing processing backlog and preserving speed.
Solution Approach 2:
The patent implements periodic action through scheduled snapshot validation and hardening operations. Rather than continuously processing every transaction with full validation, the system periodically checks snapshot consistency, validates splitter functionality, and hardens snapshots at intervals. This periodic approach ensures data protection completeness while maintaining processing speed and preventing backlog accumulation.
3Reliability
If the system forces the production site to slow down to match backup capacity, then backup site processing capability is improved, but production site productivity deteriorates
Solution Approach 1:
The patent applies preliminary action by pre-validating snapshots and performing consistency checks before they need to be fully processed by the backup site. By hardening snapshots in advance and verifying their integrity beforehand, the backup site can accept and process data at its own pace without forcing the production site to slow down, thus maintaining both backup capability and production productivity.
Solution Approach 2:
The patent segments the validation and processing tasks into distinct phases: snapshot creation, snapshot hardening with validation, and final replication. This segmentation allows the production site to continue operating at full speed while the backup site processes validated snapshots at its own capacity, eliminating the need for production site throttling and maintaining both backup capability and productivity.
4Ease of operation
If the system allows unchecked snapshots to be accessed, then system accessibility is improved, but data integrity and system stability deteriorate
Solution Approach 1:
The patent applies preliminary action by performing validation checks and hardening snapshots before making them accessible. The system pre-validates snapshot consistency, checks for corruption, and verifies data integrity before allowing access. This ensures that only verified, reliable snapshots are made available, maintaining both accessibility and data integrity simultaneously.
Solution Approach 2:
The patent implements feedback through a validation mechanism that checks snapshot integrity and provides information about snapshot status. The system validates snapshots, records their status, and uses this feedback to determine which snapshots should be accessible. This feedback loop ensures that only snapshots meeting integrity criteria are made accessible, maintaining both ease of operation and data reliability.
Data Source
AI summary
A method, system, and computer product for hardening a snapshot in a journal based replication environment comprising a production and replication site, the replicated environment running in production side protection mode, the method comprising sending notification of a start of the check from the production site to the replication site, receiving the notification at the replication site, and recording the start of the check, running a check on the replication environment, associating the check with one or more snapshots, upon completion of the check, and storing the results of the check on the replication site.