Storage Block Mapping for Rapid Virtual Machine Cloning

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current storage systems face inefficiencies in rapid cloning of virtual machines, particularly when cloning files on file systems like NTFS, as they require physical copies and consume host resources, and existing virtual machine managers like Windows System Center Virtual Machine Manager do not provide significant performance gains over traditional file copy methods.

Innovation Solution

The solution involves determining the source block range of a source data object, creating an empty data object in a destination logical storage unit, and mapping the source block range to the destination block range for cloning, which allows for fast and resource-efficient cloning without requiring physical copies and can be performed off-host, thus not consuming host resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional file copy methods are used for cloning virtual machines, then the cloning process is simple to implement, but the cloning speed is slow and host resources are consumed

Engineering Contradiction:

Improvecloning speedVSAvoidcloning process complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent implements rapid cloning by creating a copy of the virtual machine at the storage level rather than copying individual files. The system determines the source block range of the virtual machine data object, creates an empty destination data object, and maps source blocks to destination blocks, enabling fast cloning without traditional file-by-file copying that consumes host resources

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The storage system acts as an intermediary between the host and the cloning process. By performing block mapping and data object creation within the storage system itself rather than through the host file system, the patent eliminates the need for host resource consumption and achieves rapid cloning independent of host capabilities

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If virtual machine managers use Background Transfer Service technology for rapid cloning, then cloning can be performed, but performance gain over traditional file copy is not significant and memory consumption is high

Engineering Contradiction:

Improvecloning performanceVSAvoidmemory consumption

Core Design Contradiction:

ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent replaces the software-based Background Transfer Service mechanism with a storage-system-native block mapping approach. Instead of using host operating system services that consume memory and provide minimal performance improvement, the system performs direct block-level operations within the storage layer, eliminating the need for BITS technology and its associated memory overhead

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If sub LUN cloning is performed by providing LBA range input, then cloning capability is provided, but the LBA range of files on file systems is not known and cloned blocks are not recognized as files

Engineering Contradiction:

Improvecloning capabilityVSAvoidLBA range identification

Core Design Contradiction:

Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent inverts the traditional approach by not requiring the host to provide LBA ranges. Instead, the storage system automatically determines the source block range of the virtual machine data object and performs the mapping, reversing the information flow from host-provided ranges to storage-determined ranges

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS9483202B2Rapid cloning of data objects backed by non-contiguous extents

Publication Date: 2016.11.01 NETAPP INC

AI summary

A request is received to clone a source data object. A source block range of the source data object in a source logical storage unit is determined. An empty data object in the destination logical storage unit is created. A destination block range of the empty data object in the destination logical storage unit is determined. The source block range is mapped to the destination block range. The source data object is cloned based on the mapping.