Virtual Machine Backup via Hardware Snapshot and Direct Mount

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing VM backup methods using software snapshots face performance issues due to high computational costs and resource constraints, especially in high-load environments, while hardware snapshots are limited by regulatory retention requirements, storage dependency, and cost concerns.

Innovation Solution

A method that eliminates the need for a hypervisor host to mount hardware snapshots, allowing direct mounting to a backup server, and utilizes hypervisor-based changed block tracking for efficient incremental backups, reducing costs and improving performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software snapshots are used for VM backup, then backup capability is provided, but computational cost increases and performance deteriorates

Engineering Contradiction:
Improvebackup capabilityVSAvoidcomputational cost
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent introduces hardware snapshots as an intermediary mechanism between the VM and backup storage. Instead of using software-based snapshots that require hypervisor involvement and high computational resources, the hardware snapshot feature of the storage device creates point-in-time copies at the storage level, eliminating the need for software-based snapshot management and reducing computational overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the software-based snapshot mechanism (which requires hypervisor participation and generates high computational cost) with a hardware-based snapshot mechanism provided by the storage device. This substitution eliminates the need for software intervention in the snapshot creation process, thereby reducing computational cost and improving performance.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If hypervisor snapshots are used to create complete VM image copies, then backup completeness is ensured, but backup time increases and productivity decreases

Engineering Contradiction:
Improvebackup completenessVSAvoidbackup speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent utilizes hardware snapshots that are created preliminarily by the storage device before the backup process begins. These pre-created point-in-time copies serve as the basis for backup operations, eliminating the need for time-consuming software-based snapshot creation and allowing immediate backup of the complete VM image.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent leverages the storage device's hardware snapshot copying capability to create exact point-in-time copies of the VM data at the storage level. This hardware-based copying mechanism is more efficient than software-based copying, enabling complete VM image backups to be performed faster while ensuring backup completeness.

Inventive Principle:
Principle #26Copying

3Productivity

If storage snapshots are used, then backup efficiency improves, but storage dependency and cost concerns arise

Engineering Contradiction:
Improvebackup efficiencyVSAvoidstorage dependency
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent designs the backup system to utilize the universal hardware snapshot capability provided by modern storage devices. By making the backup process dependent on this widely-available storage feature rather than proprietary software, the system achieves broad compatibility and reduces complexity while maintaining high backup efficiency.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If hardware snapshots are mounted through hypervisor host, then compatibility is maintained, but unnecessary steps increase and time is lost

Engineering Contradiction:
ImprovecompatibilityVSAvoidmounting time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent extracts the hypervisor host from the snapshot mounting process, allowing the backup server to mount hardware snapshots directly without intermediate hypervisor involvement. This removal of the unnecessary intermediate step reduces mounting time and simplifies the backup workflow while maintaining compatibility through direct storage-to-backup-server connectivity.

Inventive Principle:
Principle #2Taking out (Extraction)

5Reliability

If complete VM image backups are performed, then data integrity is ensured, but backup size increases and storage resources are consumed

Engineering Contradiction:
Improvedata integrityVSAvoidbackup size
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the backup process into two stages: first, hardware snapshots create point-in-time copies of only the changed or critical data blocks; second, the backup server processes and stores these segmented data portions. This segmentation approach ensures data integrity while reducing the overall backup size compared to traditional complete image backups.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9823877B2Virtual machine backup from storage snapshot
Publication Date: 2017.11.21 VEEAM SOFTWARE GROUP GMBH
  • US9823877B2 patent drawing
  • US9823877B2 patent drawing
  • US9823877B2 patent drawing

AI summary

Disclosed herein are system, method, and computer program product embodiments for virtual machine (VM) backup from a storage snapshot. An embodiment operates by receiving selective backup parameters including a VM to backup and then creating a VM snapshot associated with the VM. Next, an offset table associated with a virtual disk of the VM stored on a storage is retrieved. The embodiment further includes generating a storage snapshot and deleting the VM snapshot and then promoting the storage snapshot to a new logical unit number. The promoted storage snapshot is then mounted to the backups server. The virtual disk data is backed up to a backup storage using the offset table from the storage snapshot. The storage snapshot is dismounted from the backup server and deleted from the storage.