Virtual Datastore Abstraction Layer for Non-Disruptive Storage Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In virtualization environments, managing physical storage for virtual machines is complex due to tight coupling with underlying physical volumes, leading to static storage configurations and significant downtime during changes, requiring administrators to handle intricacies of physical storage management.

Innovation Solution

An abstraction layer is introduced to create a virtual datastore with a unique identifier, decoupling it from underlying physical storage entities, allowing changes to physical storage without affecting virtual machines, and enabling transparent management and migration of storage resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If physical storage entities are tightly coupled to virtual machines through direct volume assignment, then storage management is straightforward at the physical level, but any changes to physical storage require virtual machine downtime and complex updates

Engineering Contradiction:
Improvestorage continuityVSAvoidstorage flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a virtual datastore as an intermediary layer between physical storage entities and virtual machines. This virtual datastore maintains a mapping relationship with physical volumes without being directly coupled to them, allowing physical storage changes to occur without affecting virtual machine operation. The virtual datastore acts as a buffer that decouples the physical and virtual storage layers, enabling independent management of each layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the storage system into distinct layers: physical storage entities, virtual datastores, and virtual machines. By separating the virtual datastore from direct dependence on physical volumes, the system allows independent modification of physical storage without requiring changes to virtual machine configurations. This segmentation enables parallel management of physical and virtual storage resources.

Inventive Principle:
Principle #1Segmentation

2Ease of manufacture

If virtual machines are directly assigned physical volumes, then storage provisioning is simple, but administrators must understand physical storage intricacies and changes cause downtime

Engineering Contradiction:
Improvestorage provisioning simplicityVSAvoidmanagement complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The virtual datastore serves as an intermediary that simplifies storage provisioning for virtual machines while abstracting away physical storage complexities. Administrators can manage virtual storage resources without needing to understand underlying physical storage intricacies, as the virtual datastore handles the complexity of physical volume management, mapping, and changes transparently.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a virtual representation (virtual datastore) that copies the essential storage interface functionality without replicating the physical storage complexity. This virtual copy provides the same storage access capabilities to virtual machines while eliminating the need for administrators to manage physical storage details, effectively decoupling management complexity from provisioning simplicity.

Inventive Principle:
Principle #26Copying

3Stability of the object's composition

If physical volumes are used directly as datastores, then storage capacity is fixed and identity is stable, but migration and changes require manual updates and policy verification

Engineering Contradiction:
Improvevolume identity stabilityVSAvoidstorage management efficiency
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent introduces dynamic mapping capabilities where the virtual datastore can be remapped to different physical volumes without changing its virtual identity. This dynamic approach allows physical storage entities to be changed, migrated, or retired while the virtual datastore maintains its stable identifier and continues to function seamlessly. The system dynamically updates the mapping between virtual and physical layers without requiring manual intervention or policy verification.

Inventive Principle:
Principle #15Dynamics

4Adaptability or versatility

If volume identity changes due to resignaturing or failure, then new volumes must be identified and assigned, but this process causes virtual machine unregister and considerable downtime

Engineering Contradiction:
Improvestorage resilienceVSAvoidvirtual machine downtime
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The virtual datastore acts as a protective intermediary that absorbs physical storage changes without transmitting them to virtual machines. When physical volumes change due to resignaturing, failure, or retirement, the virtual datastore maintains its identity and continues to provide storage access to virtual machines uninterrupted. The system handles physical volume changes at the virtualization layer, preventing downtime and eliminating the need for virtual machine unregister operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8291159B2Monitoring and updating mapping of physical storage allocation of virtual machine without changing identifier of the storage volume assigned to virtual machine
Publication Date: 2012.10.16 VMWARE INC
  • US8291159B2 patent drawing
  • US8291159B2 patent drawing
  • US8291159B2 patent drawing

AI summary

Computer implemented methods and systems for providing storage virtualization of physical storage include receiving a request for storage from a virtual machine during provisioning of the virtual machine. The request includes a capability and quota requirement for storage as required by the virtual machine. A virtual datastore that satisfies the capability and quota requirements of the request is identified. If not found, one or more volumes, that satisfy the storage requirements, are discovered or created. A virtual datastore is created and maps to one or more volumes which have unique volume identifiers. A unique virtual datastore identifier is generated for the virtual datastore. The virtual datastore identifier is distinct from the volume identifiers of the underlying volumes. The volumes are mapped to the virtual datastore while retaining the virtual datastore identifier for the virtual datastore. The virtual datastore identifier for the virtual datastore is not changed when modifications are made to the physical storage entities mapped to the virtual datastore.