Multi-Volume Snapshot Generation via Single API Request

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud computing systems face challenges in generating consistent backups or snapshots for multiple volumes attached to a single instance, leading to incomplete or wasteful storage of snapshots, as existing methods require individual requests for each volume and do not ensure all snapshots represent the same point in time.

Innovation Solution

A multi-volume snapshotting technique that uses a single API request to generate consistent snapshots for all volumes attached to an instance by suspending I/O across all partitions, processing them in parallel, and ensuring that any failure results in the deletion of partially generated snapshots, thus ensuring all snapshots represent the same point in time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual snapshot requests are sent for each volume, then snapshots can be generated for each volume, but the snapshots may not represent the same point in time and storage efficiency is reduced

Engineering Contradiction:
Improvesnapshot consistencyVSAvoidstorage efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent combines multiple individual snapshot requests into a single multi-volume snapshot request. The system receives one request that identifies multiple volumes and generates snapshots for all of them simultaneously, ensuring they represent the same point in time while improving storage efficiency by avoiding redundant data duplication across separate snapshot operations.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements preliminary I/O freezing across all volumes before snapshot generation begins. By suspending input/output operations to all volumes at the start of the snapshot process, the system ensures data consistency across all volumes without requiring individual I/O control for each volume during the snapshot operation.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If multiple individual snapshot requests are processed, then each volume can be backed up, but the number of API calls increases and processing time is extended

Engineering Contradiction:
Improvenumber of volumes coveredVSAvoidsnapshot generation time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent merges multiple snapshot operations into a single coordinated process. By receiving one multi-volume snapshot request and processing all volumes in parallel after initial I/O freezing, the system reduces the number of API calls from multiple individual requests to a single request, thereby reducing processing time while covering the same quantity of volumes.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary I/O freezing for all volumes before initiating parallel snapshot generation. This preliminary action ensures that all volumes are in a consistent state before snapshots are taken, allowing parallel processing without compromising data integrity, thus reducing overall snapshot generation time compared to sequential processing.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If I/O is frozen for each volume individually, then snapshots can be generated, but the total I/O freeze time is extended

Engineering Contradiction:
Improvesnapshot consistencyVSAvoidI/O freeze duration
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The patent combines I/O freezing operations for multiple volumes into a single coordinated action. By freezing I/O across all volumes simultaneously at the start of the snapshot process and then generating snapshots in parallel, the system minimizes the total I/O freeze duration compared to sequentially freezing and snapshotting each volume individually, while maintaining snapshot consistency.

Inventive Principle:
Principle #5Merging (Combining)

4Productivity

If snapshots are generated without coordination, then individual volume backups are created, but incomplete backup sets are produced

Engineering Contradiction:
Improvesnapshot generation speedVSAvoidbackup completeness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary I/O freezing across all volumes before snapshot generation begins. This preliminary coordination ensures that all volumes are captured at the same point in time, preventing incomplete backup sets while allowing parallel snapshot generation to maintain high productivity. The system also implements a commit mechanism that ensures all snapshots are successfully created or none are, maintaining backup completeness.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11032156B1Crash-consistent multi-volume backup generation
Publication Date: 2021.06.08 AMAZON TECH INC
  • US11032156B1 patent drawing
  • US11032156B1 patent drawing
  • US11032156B1 patent drawing

AI summary

Aspects relate to a framework for utilizing a single API request to manage the creation of consistent snapshots for a set of volumes attached an individual instance in a distributed computing environment. Responsive to receipt of an API request identifying the instance, the multi-volume snapshot service identifies a set of volumes attached to the identified instance. The identified set of volumes can be processed or filtered to eliminate specific volumes or types of volumes, such as boot volumes. In the event that any snapshot creation attempt fails, the multi-volume snapshot service fails the API request and can delete any snapshot data generated prior to the failure.