Cloud Volume Snapshot Cloning for Fast Failure Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional processes for recovering from storage volume failures in cloud computing systems are time-consuming and inefficient, often requiring re-protection and rebalancing procedures that lead to data unavailability and loss.

Innovation Solution

A system and method that utilize volume suspension, snapshotting, and cloning components to suspend I/O operations, capture a snapshot of a failed volume, and create a new volume based on that snapshot, enabling rapid replacement without re-protection or rebalancing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional re-protection and rebalancing procedures are used for volume failure recovery, then data consistency is maintained, but system downtime increases and productivity decreases

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system creates snapshots of storage volumes before failures occur and maintains them in readiness. When a volume fails, pre-prepared snapshots enable immediate restoration without waiting for complex re-protection procedures, thus maintaining data consistency while minimizing downtime

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates copy snapshots of storage volumes that can be rapidly deployed as replacements. These snapshots are copies of the original volume state and can be mounted immediately upon failure, providing a fast restoration path that avoids time-consuming rebalancing operations

Inventive Principle:
Principle #26Copying

2Productivity

If rapid volume replacement is implemented without re-protection procedures, then productivity and system availability improve, but data consistency and reliability may be compromised

Engineering Contradiction:
Improvevolume restoration speedVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system creates accurate snapshots that copy the complete state of storage volumes including all data and metadata. These snapshots serve as reliable replacements that maintain data consistency while enabling rapid deployment without re-protection procedures

Inventive Principle:
Principle #26Copying

Solution Approach 2:

Snapshots are created and validated in advance before failures occur. This preliminary action ensures that when a volume fails, a known-good copy is immediately available for restoration, maintaining both speed and reliability

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If snapshots are created frequently for rapid restoration, then recovery time decreases, but storage system complexity and resource consumption increase

Engineering Contradiction:
Improverecovery timeVSAvoidsnapshot management complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The snapshot system serves multiple functions: it enables rapid restoration, provides backup capability, and supports volume cloning operations. This multi-functionality justifies the added complexity by delivering multiple benefits from a single snapshot infrastructure

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

Solution Approach 2:

The system allows flexible adjustment of snapshot parameters such as retention period, frequency, and storage location. These parameter changes enable optimization of the balance between recovery speed and system complexity based on specific operational requirements

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12541434B2Volume replacement using cloud volume snapshots
Publication Date: 2026.02.03 DELL PROD LP
  • US12541434B2 patent drawing
  • US12541434B2 patent drawing
  • US12541434B2 patent drawing

AI summary

A method facilitating volume replacement using cloud volume snapshots includes halting, by a system including at least one processor, input/output (I/O) activity to a first volume of a cloud computing system in response to the first volume being determined to be unreachable; obtaining, by the system, a snapshot of the first volume in response to the halting; and creating, by the system, a second volume, of the cloud computing system and other than the first volume, using the snapshot.