Virtual Storage Container Protocol Access via File Abstractions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current virtual storage systems lack flexibility in supporting various computing environments, as they cannot seamlessly transition between file- and block-based protocols, and do not efficiently provide block-level services like replication and snapshotting across virtual storage containers accessed via different protocols.

Innovation Solution

Provisioning all virtual storage containers as block-based logical storage devices that can be bound to either a block-based protocol endpoint as a LUN or a file-based protocol endpoint as a file, using a lightweight filesystem that creates file abstractions mapping to underlying logical storage devices, allowing access over file-based network storage protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a vVol is accessible only through block-based protocol as a LUN, then block-level services can be provided, but accessibility to VMs using file-based protocols is not possible

Engineering Contradiction:

Improveprotocol accessibilityVSAvoidmigration operations

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The vVol is designed to be universally accessible through multiple protocol interfaces. The same underlying vVol can be mounted as a LUN for block-based access or exported as a file for file-based access, eliminating the need for migration operations and enabling broad compatibility across different VM access patterns.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The virtualization layer acts as an intermediary that presents the same vVol through different protocol interfaces. The vVol remains a unified block-based storage container while the virtualization infrastructure enables both block-based (iSCSI, Fibre Channel) and file-based (NFS, CIFS) access paths without requiring transformation or migration.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If extensive migration operations are performed to transform file accessible over file-based network protocol into a LUN, then block-based access is achieved, but system complexity and time increase

Engineering Contradiction:

Improveaccess transformationVSAvoidmigration time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The vVol is pre-configured as a block-based storage container that can be simultaneously or alternatively accessed through file-based protocols via the virtualization layer. This preliminary setup eliminates the need for subsequent migration operations, as the infrastructure is already in place to support both access methods from the outset.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If block-level services are provided only to LUNs, then service functionality is maintained, but versatility across different protocol access methods is reduced

Engineering Contradiction:

Improveblock-level service functionalityVSAvoidprotocol-agnostic service support

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

Block-level services such as replication, snapshotting, and de-duplication are implemented at the vVol level in the virtualization infrastructure, making them protocol-agnostic. These services can be applied to vVols regardless of whether they are accessed via block-based or file-based protocols, ensuring both reliability and versatility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9613053B1Techniques for providing access to a virtualized block storage device over a file-based network storage protocol

Publication Date: 2017.04.04 EMC IP HLDG CO LLC

AI summary

Techniques are described for allowing a data storage system to provision all vVols (or other similar virtual storage containers) as logical storage devices, which can be bound to either a block-based protocol endpoint as an exposed LUN or to a file-based protocol endpoint as a file. This may be accomplished by operating, as part of the file-based protocol endpoint, a lightweight filesystem that creates file abstractions that map to underlying logical storage devices.