Storage Snapshot Layer Volume Chunk Versioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current storage systems face challenges in efficiently managing data snapshots and versioning, particularly in maintaining consistency and resource allocation across snapshot operations, leading to complexities in handling writes and reads effectively.

Innovation Solution

The implementation of a storage system with a snapshot layer that utilizes volume-version and chunk-version data structures, including timestamps and pointers to storage resources, allows for efficient management of snapshot operations by maintaining a unique association of snapshot-layer chunks with volume IDs and logical chunk addresses, enabling seamless handling of writes and reads through advanced data structures and controllers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional snapshot management methods are used, then snapshot operations can be performed, but data consistency and resource allocation become complex and inefficient

Engineering Contradiction:
Improvesnapshot operation efficiencyVSAvoidsnapshot management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments snapshot management into two distinct data structures: volume-version data structures for volume-level snapshot operations and chunk-version data structures for chunk-level data management. This segmentation allows independent optimization of each layer, improving snapshot operation efficiency while reducing overall management complexity by dividing the complex task into manageable parts.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimensional approach by maintaining version information at both volume and chunk levels simultaneously. This multi-dimensional versioning system adds a chunk-level dimension to traditional volume-level snapshot management, enabling more granular control and more efficient resource allocation without increasing management complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If detailed version information is maintained for each snapshot, then data integrity is improved, but storage overhead and management complexity increase

Engineering Contradiction:
Improvedata integrityVSAvoidstorage overhead
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges volume-version and chunk-version data structures through shared identifiers and cross-referencing mechanisms. By combining these structures, the system maintains comprehensive version information for data integrity while avoiding redundant storage of duplicate information, thus reducing storage overhead.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The volume-version and chunk-version data structures serve multiple functions: they track snapshot operations, maintain version history, enable data recovery, and support resource allocation. This multi-functionality reduces the need for separate dedicated structures for each function, minimizing storage overhead while maintaining data integrity.

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

Data Source

PatentEP3000059B1Managing data in a storage system
Publication Date: 2023.10.25 THE SILK TECH ILC LTD
  • EP3000059B1 patent drawingFigure 1
  • EP3000059B1 patent drawingFigure 2
  • EP3000059B1 patent drawingFigure 3

AI summary

According to an aspect of the presently disclosed subject matter, there is provided a system for managing data in a storage system, the system including a storage layer which provides storage resource, and a snapshot layer that includes: a volume- version data structure, a chunk-version data structure and a IO handler.