Virtual Machine Disk Signature Mapping for Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data protection systems face challenges such as system shutdown during backups, limited recovery points, and lengthy data recovery processes, which can result in significant data loss in the event of a disaster.
Innovation Solution
The system employs an apparatus and method for reading signatures from a virtual machine disk, mapping offsets, and sending these signatures to a replication site for data synchronization, allowing for efficient replication and recovery of data by using hash values to identify and synchronize changed data blocks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data replication is performed at the data block level, then data protection reliability is improved, but device complexity increases
Solution Approach 1:
The patent segments data into fixed-size blocks and uses cryptographic hashes (e.g., SHA-256) to represent each block. This segmentation allows efficient identification of changed blocks through hash comparison, enabling reliable data protection while maintaining manageable system complexity through modular block-level operations rather than handling entire files or volumes.
Solution Approach 2:
The patent introduces hash values as an intermediary representation of data blocks. Instead of directly comparing or copying large amounts of data, the system uses compact hash signatures to identify which blocks need replication. This intermediary mechanism significantly reduces network bandwidth requirements and simplifies the replication process while maintaining data integrity.
2Reliability
If continuous data replication is implemented, then data loss prevention is improved, but use of energy increases
Solution Approach 1:
The patent implements partial replication by using hash comparison to identify only the specific data blocks that have changed since the last replication. Instead of continuously copying all data, the system performs partial updates based on hash mismatches, reducing energy consumption while maintaining continuous data protection capability.
Solution Approach 2:
The system maintains continuous data protection through persistent hash tracking and incremental replication. By continuously monitoring data block hashes and replicating only changed blocks, the system achieves continuous protection without the energy overhead of continuous full-data replication, enabling efficient near-real-time synchronization.
3Quantity of substance
If data is backed up on a daily basis, then storage cost is reduced, but loss of time increases
Solution Approach 1:
The patent implements continuous data protection by continuously tracking data block hashes and maintaining a replication state. This continuous monitoring enables recovery to any point in time, eliminating the data loss window associated with periodic backups while using efficient block-level replication to minimize storage requirements compared to full continuous duplication.
Solution Approach 2:
The system performs preliminary hash computation and change detection before replication is needed. By continuously computing and comparing hashes in advance, the system prepares replication data incrementally, enabling rapid recovery operations and any-point-in-time restoration without requiring extensive storage capacity.
4Productivity
If hash-based synchronization is used, then productivity is improved, but measurement precision requirements increase
Solution Approach 1:
The patent replaces traditional data comparison mechanisms with cryptographic hash functions. Instead of comparing actual data block contents (which would be time-consuming and bandwidth-intensive), the system uses hash values as compact representations. This substitution dramatically improves synchronization speed and productivity while requiring high precision in hash computation and comparison to ensure data integrity.
Data Source
AI summary
A computer implemented method for reading signatures corresponding to a portion of data on a virtual machine disk on a production site, wherein reading the signature includes mapping the virtual machine disk offset into a physical storage offset, and reading the signature from the physical storage; sending the signature of the portion of data to a replication site; obtaining a mapping from a virtual disk to a physical disk at the replica site; issuing a command to write a portion of data corresponding to the signature to a the physical storage based on the mapping of the replica of the virtual machine disk on the replication site; determining if the command was successful; and based on a determination that the command was not successful, marking the locations corresponding to the signature for synchronization in a synchronization structure.


