Hypervisor-Free VM File Recovery via Pseudo-Disk Driver
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for recovering backed-up virtual machine data require a hypervisor, leading to increased configuration complexity, cost, and slower recovery processes, especially in disaster scenarios where compatible hypervisors may not be available.
Innovation Solution
A hypervisor-agnostic approach that segregates payload data from hypervisor-specific metadata during backups, allowing for block-level file recovery without a hypervisor, using a pseudo-disk driver to directly access and restore individual VM files to any platform.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a hypervisor is used to recover backed up VM data, then the recovery process can access and interpret VM metadata, but the configuration complexity and cost increase, and the recovery speed decreases
Solution Approach 1:
The patent extracts the hypervisor dependency from the recovery process by directly accessing backup media through a pseudo-disk driver. Instead of requiring a hypervisor to interpret VM metadata, the system extracts and recovers individual VM files directly from the backup media, eliminating the need for hypervisor software during recovery operations.
Solution Approach 2:
The patent introduces a pseudo-disk driver as an intermediary component that sits between the recovery system and the backup media. This driver enables direct access to backup data without requiring a hypervisor, serving as a mediator that translates recovery requests into direct media access operations while maintaining simplicity and reducing configuration complexity.
2Reliability
If a hypervisor is used to recover backed up VM data, then the recovery process can interpret VM metadata, but the recovery time increases and portability decreases
Solution Approach 1:
The patent removes the hypervisor layer from the recovery path, extracting only the necessary VM files directly from backup media. This eliminates the time-consuming process of hypervisor initialization, metadata interpretation, and virtualization overhead, enabling faster recovery by directly restoring individual files without requiring the entire VM infrastructure.
Solution Approach 2:
The patent segments the recovery process into individual file-level operations rather than requiring complete VM restoration through a hypervisor. By breaking down the recovery into discrete file operations that can be performed independently, the system achieves faster recovery times and enables selective restoration of only the necessary data components.
3Reliability
If a hypervisor is required for recovery, then VM metadata can be properly interpreted, but the system becomes less portable and more expensive
Solution Approach 1:
The patent creates a universal recovery mechanism that works across different platforms and hypervisor types without requiring platform-specific software. The pseudo-disk driver provides a standardized interface that can access backup media regardless of the original VM platform, enabling the same recovery process to be used for VMware, VirtualBox, and other virtualization environments, thereby achieving cross-platform portability.
Solution Approach 2:
The patent extracts the platform-specific hypervisor layer from the recovery process, allowing direct access to VM files through a platform-agnostic pseudo-disk driver. This extraction enables recovery operations to be performed on any system without requiring the original hypervisor software, achieving independence from specific virtualization platforms and enhancing portability.
4Productivity
If individual VM files are restored without a hypervisor, then the recovery process becomes faster and more portable, but the ability to access and interpret VM metadata is lost
Solution Approach 1:
The patent applies partial action by restoring only the specific VM files that are needed rather than requiring complete VM restoration with full metadata interpretation. This selective file-level recovery provides sufficient information for most recovery scenarios while achieving faster recovery speeds, accepting that some metadata interpretation capabilities are lost in exchange for improved productivity.
Data Source
AI summary
Hypervisor-independent block-level live browse is used for directly accessing backed up virtual machine (VM) data. Hypervisor-free file-level recovery (block-level pseudo-mount) from backed up VMs also is disclosed. Backed up virtual machine (“VM”) data can be browsed without needing or using a hypervisor. Individual backed up VM files can be requested and restored to anywhere without a hypervisor and without the need to restore the rest of the backed up virtual disk. Hypervisor-agnostic VM backups can be browsed and recovered without a hypervisor and from anywhere, and individual backed up VM files can be restored to anywhere, e.g., to a different VM platform, to a non-VM environment, without restoring an entire virtual disk, and without a recovery data agent at the destination.