Snapshot Replication via Delta Data Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage systems lack the ability to efficiently replicate snapshots across volumes, especially in integrating with storage management software that manage automatic or manual snapshots and backups, and do not provide a unified approach for replicating both system and user snapshots.

Innovation Solution

A storage system with a controller that initializes replication processes between volumes, copies content from system and user snapshots, and identifies delta data for efficient replication, enabling the replication of both system and user snapshots across volumes, and allowing users to specify replication in a hierarchical snapshot tree.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional storage replication methods are used, then data can be replicated between volumes, but snapshots cannot be replicated across volumes and integration with storage management software is limited

Engineering Contradiction:
Improvesnapshot replication capabilityVSAvoiddata integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the snapshot replication process into distinct components: system snapshots taken by storage management software, user snapshots accessible to users, and delta data identification. This segmentation allows each component to be independently managed and replicated appropriately, enabling snapshot replication while maintaining data integrity through structured processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary replication process that acts as a mediator between storage management software and user applications. This intermediary mechanism captures snapshots at different levels (system and user), identifies changes (delta data), and replicates only the necessary portions, thereby enabling versatile snapshot replication while preserving data integrity through controlled intermediary processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If all snapshot data is replicated, then complete data redundancy is achieved, but bandwidth consumption increases

Engineering Contradiction:
Improvedata redundancyVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and replicates only the delta data (changes) from snapshots rather than replicating entire snapshot datasets. By identifying and separating the changed portions from unchanged data, the system achieves complete data redundancy through selective replication of only the necessary delta portions, significantly reducing bandwidth consumption while maintaining full reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by replicating only the necessary portion of snapshot data (delta data) rather than performing excessive full-data replication. This partial replication approach achieves sufficient data redundancy for reliability while minimizing bandwidth consumption by avoiding unnecessary transmission of unchanged data.

Inventive Principle:
Principle #16Partial or excessive action

3Ease of operation

If users can access and manage all snapshots, then user control is maximized, but system complexity increases

Engineering Contradiction:
Improveuser controlVSAvoidsnapshot management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments snapshot access rights by creating two distinct types: system snapshots (not accessible to users) and user snapshots (accessible to users). This segmentation allows users to control and manage their own snapshots easily while the system maintains separate system-level snapshots, thereby maximizing user control without increasing overall system complexity through clear role-based separation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal snapshot management system that handles both system snapshots and user snapshots through a unified replication process. This multi-functional approach allows the same replication infrastructure to serve dual purposes (system-level and user-level snapshots), simplifying the overall system architecture while providing comprehensive user control capabilities.

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

4Ease of operation

If replication processes are simplified, then ease of use is improved, but flexibility in failover configurations is reduced

Engineering Contradiction:
Improvereplication processVSAvoidfailover configurations
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic replication process that automatically adapts to different failover configuration requirements. The system dynamically determines what constitutes delta data based on the specific replication context and failover needs, allowing simplified user-initiated replication processes while maintaining flexibility for various failover scenarios through automatic dynamic adjustment of replication parameters.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables self-service replication where users can initiate simple replication processes without complex configuration, while the system automatically handles the complexity of delta data identification and failover configuration adaptation. This self-service mechanism simplifies user interaction while preserving flexible failover configurations through automatic system-level decision-making.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10394482B2Snap tree arbitrary replication
Publication Date: 2019.08.27 SEAGATE TECH LLC
  • US10394482B2 patent drawing
  • US10394482B2 patent drawing
  • US10394482B2 patent drawing

AI summary

Systems and methods for replicating a snapshot of a volume are described. In one embodiment, a storage controller of a storage system may be operable to initialize a first replication process between a first storage volume of the first storage system and a second storage volume of a second storage system, copy content from a first system snapshot of the first storage volume to a second system snapshot of the first storage volume, and copy content from a first user snapshot of the first storage volume to the first system snapshot of the first storage volume. In some cases, a system snapshot is not accessible to a user and a user snapshot is accessible to the user. In some cases, at least one of the system snapshot and the user snapshot include a point in time capture of data on the first storage volume.