Cloud VM Restore Using Snapshot Volumes Without IP Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack an efficient and centralized method to manage and restore virtual machines across multiple cloud servers and local data centers, particularly in the event of data loss due to disasters or corruption, without requiring individual logins and logins for each machine, and without changing the Internet Protocol address of the virtual machine.
Innovation Solution
A workload management system and interface that integrates snapshot management across multiple cloud servers and local data centers, enabling centralized backup, recovery, and file retrieval, with capabilities for scheduling snapshot capture and deduplication, and seamless restoration of corrupted virtual machines using captured snapshots.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If virtual machines are restored using existing systems, then restoration can be performed, but IP address changes occur and centralized management across multiple cloud servers is not achieved
Solution Approach 1:
The system segments the restoration process into distinct phases: snapshot capture, snapshot storage, recovery virtual machine launch, and data volume attachment. Each phase is independently managed, allowing the IP address to remain unchanged while restoring data volumes from snapshots. This segmentation enables reliable restoration without requiring IP address changes or complex reconfiguration.
Solution Approach 2:
The patent introduces a recovery virtual machine as an intermediary that facilitates the restoration process. This intermediary VM is launched with the same IP address as the corrupted VM, then attaches restored data volumes from snapshots. The intermediary approach allows centralized management and consistent IP addressing while enabling reliable restoration across multiple cloud servers.
2Ease of manufacture
If snapshots are managed individually for each virtual machine, then snapshot capture is simple, but centralized management and deduplication across multiple servers cannot be achieved
Solution Approach 1:
The system merges snapshot management across multiple virtual machines and cloud servers into a centralized repository. Snapshots are captured and stored in a unified location accessible by all recovery operations. This merging enables centralized management, cross-VM deduplication, and improved restoration efficiency without complicating the individual snapshot capture process.
Solution Approach 2:
The snapshot repository serves multiple functions: storing snapshots from different virtual machines, enabling deduplication across VMs, supporting restoration operations, and providing a centralized management interface. This universal snapshot system improves productivity by allowing efficient restoration from a single centralized location while maintaining ease of snapshot capture.
3Productivity
If data volumes are restored without centralized management, then restoration can proceed, but disaster recovery effectiveness and service continuity are reduced
Solution Approach 1:
The system performs preliminary actions by capturing and storing snapshots of data volumes before corruption or disaster occurs. These snapshots are preserved in a centralized repository with consistent IP address mapping. When restoration is needed, the pre-captured snapshots can be quickly restored without changing IP addresses, ensuring both fast restoration and reliable disaster recovery across distributed infrastructure.
Data Source
AI summary
The disclosed technology teaches recovering a first virtual machine or an instance with an Internet Protocol address, a first root volume and one or more data volumes that are corrupted. The first virtual machine is hosted by a first cloud server that hosts plurality of virtual machines. The disclosed technology includes instructing the first cloud server to launch a recovery virtual machine. The recovery virtual machine launches one or more new data volumes based upon captured file system images in one or more snapshots taken of corrupted data volumes of the first virtual machine prior to becoming corrupted. The recovery virtual machine detaches the corrupted data volumes and attaches the new data volumes launched to the first virtual machine. The Internet Protocol address of the first virtual machine remains unchanged.