Multilevel Snapshot Replication for Storage Hotspot Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional distributed storage systems face inefficiencies in data replication due to high journal lag and resource consumption during validation of point-in-time replicas, which increases recovery time and reduces system performance.

Innovation Solution

Implementing a multilevel snapshot replication method that identifies 'hotspot' and 'cold' regions within a production volume, replicating hotspots at longer intervals and cold regions at shorter intervals, reducing bandwidth consumption and storage overhead while maintaining low Recovery Point Objectives (RPOs).

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If snapshot replication is performed at frequent intervals for all regions, then data protection reliability is improved, but bandwidth consumption and storage overhead increase

Engineering Contradiction:
Improvedata protection reliabilityVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by differentiating replication frequencies based on regional data characteristics. Hotspot regions (frequently accessed) use longer snapshot intervals, while cold regions (rarely accessed) use shorter intervals. This localized approach optimizes bandwidth consumption by reducing redundant replication of frequently accessed data while maintaining adequate protection for less accessed data.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically adjusts snapshot replication intervals based on real-time identification of hotspot and cold regions. The replication frequency is not static but adapts to changing workload patterns, allowing the system to respond to varying data access patterns and optimize resource utilization dynamically.

Inventive Principle:
Principle #15Dynamics

2Reliability

If snapshot replication is performed at frequent intervals for all regions, then Recovery Point Objective (RPO) is improved, but storage overhead increases

Engineering Contradiction:
ImproveRecovery Point ObjectiveVSAvoidstorage overhead
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements local quality by applying different snapshot intervals to different regions based on their access patterns. Cold regions receive more frequent replication to ensure low RPO, while hotspot regions use less frequent replication since their data is more critical and can tolerate longer intervals. This reduces overall storage overhead while maintaining adequate RPO for each region's needs.

Inventive Principle:
Principle #3Local quality

3Reliability

If conventional validation of point-in-time replicas is performed, then data integrity is ensured, but system performance decreases and recovery time increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the validation process from the main replication workflow by performing validation asynchronously and selectively. Instead of validating every replicated snapshot immediately, the system validates replicas on-demand or in background processes, reducing the performance impact on the primary replication operation while still ensuring data integrity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10235060B1Multilevel snapshot replication for hot and cold regions of a storage system
Publication Date: 2019.03.19 EMC IP HLDG CO LLC
  • US10235060B1 patent drawing
  • US10235060B1 patent drawing
  • US10235060B1 patent drawing

AI summary

Described embodiments provide systems and methods for operating a storage system having a production volume. The system identifies one or more regions of the production volume and receives write requests to be written to the production volume during an operating time window. Each received write request is associated with at least one of the regions. Based upon at least one the received write requests, one or more regions of the production volume are identified as hotspot regions and one or more regions of the production volume are identified as cold regions. For write requests associated with a hotspot region, snapshot replication is performed at a hotspot region snapshot interval, and for write requests associated with a cold region, snapshot replication is performed at one or more cold region snapshot intervals. The hotspot region snapshot interval is longer than the one or more cold region snapshot intervals.