Data Storage Object Cloning Across Federation Appliances

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data storage federations lack the ability to create or migrate clones on a different appliance within the federation from the base volume, due to the inability to share blocks across appliances.

Innovation Solution

A method is disclosed to create a clone on a second data storage appliance by first creating a snapshot of the source storage object on the first appliance, then performing a full copy of the snapshot to the second appliance, and finally creating the clone from the copy snapshot and incorporating it into a federation-wide family association.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If clones are created as derivative objects sharing blocks with primary objects, then storage efficiency is improved, but the ability to create clones on different appliances is lost

Engineering Contradiction:

Improvestorage efficiencyVSAvoidclone placement flexibility

Core Design Contradiction:

Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent segments the clone creation process into two distinct phases: (1) creating a snapshot of the base volume on the source appliance, and (2) copying the snapshot to the target appliance to create the clone. This segmentation allows the clone to be placed on a different appliance while maintaining data integrity and enabling separate I/O workloads.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a snapshot as an intermediary object that bridges the base volume and the clone across different appliances. The snapshot serves as a mediator that can be copied to the target appliance, enabling clone creation without direct block sharing between appliances.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If block sharing across appliances is enabled, then clone creation on different appliances becomes possible, but system complexity increases

Engineering Contradiction:

Improveclone placement flexibilityVSAvoidblock sharing complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Instead of implementing complex block sharing mechanisms across appliances, the patent uses a copying approach where the snapshot is fully copied to the target appliance. This simplifies the system architecture by avoiding inter-appliance block sharing while still enabling clone creation on different appliances.

Inventive Principle:

Principle #26Copying

3Device complexity

If base volume and clone are on the same appliance, then block sharing is simplified, but I/O performance is limited

Engineering Contradiction:

Improveblock sharing complexityVSAvoidI/O performance

Core Design Contradiction:

Device complexityVSProductivity

Solution Approach 1:

The patent moves the clone to a different appliance, adding a new dimension (appliance distribution) to the storage architecture. This allows simultaneous I/O operations on the base volume and clone to occur on different appliances, improving overall system throughput and performance.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS12282493B2Data storage object cloning in a multi-appliance federation

Publication Date: 2025.04.22 DELL PROD LP

AI summary

A method of creating a clone, on a second data storage appliance of a federation, of a source storage object stored on a first data storage appliance of the federation, includes creating a snapshot (point-in-time copy) of the source storage object at the first appliance, and then performing a full copy of the snapshot from the first appliance to the second appliance to produce a copy snapshot on the second appliance. At the second appliance, the clone is created from the copy snapshot and incorporated into a federation-wide family association of the source storage object. Specific use cases include (1) creating a clone on a different appliance from a base volume, (2) migrating a clone to a different appliance from a base volume, (3) refreshing a clone from a base volume, and a base volume from a clone, across appliances.