Storage Container Identity Preservation During Snapshot Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems are inefficient and time-consuming when copying the state of a snapshot in a file system to a virtual machine, as they often require creating a new copy of the data, which can replace the entire state of the virtual machine, including its identity, making it undesirable.
Innovation Solution
Implementing a process that allows for instantaneous change of a storage container's state to a snapshot while preserving its identity, enabling synchronization of a container to any snapshot while maintaining its original identity, using techniques such as B-tree data structures to map logical to physical offsets and allowing reference to snapshots without duplicating physical data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional systems create a new copy of snapshot data for the virtual machine, then the virtual machine can be restored to a former state, but the process is time-consuming and space inefficient
Solution Approach 1:
The patent uses copy-on-write technology to create a virtual copy of snapshot data without physically duplicating the entire data set. The system creates a new virtual machine instance that references the snapshot data through virtual file system links, enabling instantaneous restoration without time-consuming physical copying of all data blocks.
Solution Approach 2:
The patent extracts only the necessary data blocks that differ from the original snapshot when restoring a virtual machine. Instead of copying the entire snapshot data set, the system identifies and transfers only the modified data blocks, significantly reducing copying time and space requirements while maintaining restoration capability.
2Reliability
If conventional systems create a new copy of snapshot data, then the virtual machine state can be restored, but the entire state including identity is replaced which is undesirable
Solution Approach 1:
The patent creates a virtual copy of the virtual machine state that references snapshot data without physically duplicating identity-critical data structures. The virtual file system maintains separate identity metadata that preserves the original virtual machine's unique identifiers, allowing state restoration while maintaining identity integrity.
Solution Approach 2:
The patent segments the virtual machine state into data blocks and identity metadata. The snapshot restoration process only affects data blocks while leaving identity metadata intact and separate, enabling selective restoration of computational state without replacing the virtual machine's unique identity characteristics.
3Reliability
If the entire state of the virtual machine is copied, then the snapshot state can be restored, but space efficiency is reduced
Solution Approach 1:
The patent implements space-efficient copying through virtual file system references and copy-on-write technology. Instead of allocating physical storage for complete data duplication, the system creates virtual references to snapshot data blocks, allowing multiple virtual machines to share the same underlying storage resources until modifications are needed.
Solution Approach 2:
The patent performs partial copying by transferring only the necessary data blocks required for snapshot restoration rather than copying the entire virtual machine state. The system identifies and copies only modified or relevant data blocks, reducing storage space requirements while maintaining restoration capability.
Data Source
AI summary
Performing data synchronization is disclosed, including: receiving an indication to synchronize a container to a snapshot, wherein the container has a first data state and an identity, wherein the snapshot corresponds to a second data state; causing the container to have the second data state corresponding to the snapshot; and maintaining the identity of the container.