Virtual Machine Snapshot Layer Metadata Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtual machine (VM) disaster recovery processes fail when the chain of VM records is not synchronized with the chain of storage unit layers, leading to difficulties in determining which snapshot layers correspond to which VM records, resulting in failed recovery operations.
Innovation Solution
A method is implemented to generate and store VM records with unique identifiers in metadata associated with snapshot layers, allowing for synchronization analysis during recovery to establish correspondence between VM records and snapshot layers, even in the absence of synchronization, and providing options for operators to resolve synchronization issues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If VM records and snapshot layers are maintained separately without synchronization mechanisms, then the system complexity is reduced, but the reliability of VM recovery fails when synchronization is lost
Solution Approach 1:
The patent applies preliminary action by embedding the VM record identifier into the metadata of snapshot layers during the snapshot creation process itself. This ensures that the correspondence relationship is established in advance, before any potential synchronization issues arise. The identifier is stored proactively in the snapshot layer metadata, so that even if the VM record chain becomes disconnected or corrupted, the snapshot layers retain their identity information and can be matched to the correct VM records during recovery operations.
2Reliability
If VM record identifiers are stored in snapshot layer metadata, then the ability to recover VMs during synchronization issues is improved, but the storage overhead and metadata complexity increase
Solution Approach 1:
The patent extracts the critical identification function from the complex VM record chain structure and places it directly into the snapshot layer metadata. By taking out the VM record identifier and embedding it in the snapshot layer, the system separates the identification capability from the main VM record management structure. This allows snapshot layers to be independently identified and matched to VM records without requiring the entire VM record chain to be intact and synchronized.
3Measurement precision
If the system requires strict synchronization between VM records and snapshot layers, then the precision of recovery operations is improved, but the productivity and ease of operation deteriorate due to manual intervention requirements
Solution Approach 1:
The patent implements self-service by enabling the snapshot layers to carry their own identification information (VM record identifiers) within their metadata. This allows the system to automatically match snapshot layers to VM records during recovery operations without requiring external synchronization mechanisms or manual intervention. The snapshot layers essentially identify themselves to the correct VM records through the embedded identifiers, making the recovery process autonomous and eliminating the need for strict external synchronization control.
Data Source
AI summary
Virtual machine synchronization and recovery is disclosed. At a first instance in time, a first snapshot request to generate a first snapshot of a virtual machine (VM) is received. The VM utilizes a storage unit. A first snapshot layer is generated for the storage unit. The first snapshot layer preserves a state of the storage unit at the first instance in time. A first VM record that corresponds to the first snapshot request and that includes a first VM record identifier (ID) is generated. The first VM record ID is stored in metadata associated with the first snapshot layer, and the first VM record is stored in a first location.