Snapshot Integrity Verification via Distributed Checksum Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In highly available computing systems, replicated snapshots can become corrupted due to hardware failures or malware, leading to potential data corruption during disaster recovery operations, and existing methods fail to detect corruption before it is too late, resulting in costly and resource-intensive failures.
Innovation Solution
The implementation of snapshot integrity verification techniques that check the integrity of distributed snapshot portions across multiple storage devices by calculating and comparing checksums, allowing for the identification of corrupted snapshots before they are used in disaster recovery operations, thereby reducing resource expenditure and ensuring data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If replicated snapshots are stored for long periods without verification, then storage resources are conserved and access speed is maintained, but data integrity deteriorates due to undetected corruption
Solution Approach 1:
The patent applies preliminary action by calculating and storing checksums for each snapshot portion at the time of replication, before any potential corruption occurs. This allows integrity verification to be performed quickly later by simply comparing current checksums against the pre-stored ones, without needing to perform time-consuming full snapshot comparisons or re-calculations.
Solution Approach 2:
The patent replaces the mechanical approach of fully assembling and verifying snapshot data with a computational checksum comparison system. Instead of physically checking data integrity through complex verification processes, the system uses lightweight cryptographic hash functions to generate and compare checksum values, dramatically reducing verification time and computational overhead.
2Reliability
If checksum verification is performed on all snapshot portions before assembly, then data integrity is ensured, but network bandwidth and processing resources are consumed
Solution Approach 1:
The patent extracts the integrity verification function from the snapshot assembly process by separately calculating and storing checksums for each portion. This allows the verification to be performed independently and efficiently using only metadata comparisons, without requiring the actual snapshot data to be moved or assembled, thus conserving network bandwidth and processing resources.
Solution Approach 2:
The patent creates a lightweight copy of the integrity verification information in the form of checksums stored in metadata. Instead of copying and verifying the actual snapshot data, the system copies only the small checksum values and compares them, reducing the verification overhead from gigabytes of data to kilobytes of metadata.
3Measurement precision
If distributed snapshot portions are assembled before integrity checking, then complete snapshot verification is possible, but resource expenditure increases due to data transmission and assembly operations
Solution Approach 1:
The patent performs preliminary action by calculating checksums for each distributed snapshot portion at replication time and storing them in metadata. This allows integrity verification to be performed later by simply comparing checksums without needing to assemble or transmit the actual snapshot data, eliminating unnecessary network bandwidth consumption while maintaining verification accuracy.
Data Source
AI summary
Systems and computer program products for highly available computing systems. Techniques for verifying a replicated snapshot integrity includes steps for storing a snapshot at a first computing system where the snapshot has a corresponding first data integrity value (e.g., a checksum). Another storing operation stores a replica snapshot as two or more portions at respective two or more computing nodes of a second computing system. A second data integrity value that corresponds to the snapshot that was stored at the two or more computing nodes is calculated. Corruption is detected by comparing the first data integrity value to the second data integrity value. Corruption of a to-be-assembled snapshot can be detected before incurring the cost of assembly of the two or more portions of a replica snapshot. Alternative snapshots that can be assembled from alternative portions are considered for assembly. Only uncorrupted snapshots are restored to a designated computing system.