Storage Manager Snapshot Coordination for Replication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current replicated storage systems lack advanced functionality for managing snapshots, clones, and data replication, leading to inefficiencies in data management and recovery processes.

Innovation Solution

The implementation of a network environment with a storage manager that coordinates snapshot creation, quiesce instructions, and garbage collection across compute and storage nodes, enabling efficient snapshot management, cloning, and data replication, while maintaining error handling and resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is replicated across multiple storage devices, then data availability and reliability are improved, but system complexity and write operation overhead increase

Engineering Contradiction:
Improvedata availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A storage manager is introduced as an intermediary component that coordinates snapshot creation, quiesce instructions, and garbage collection across compute and storage nodes. This mediator handles the complexity of managing replicated data, allowing individual storage devices to maintain copies while the storage manager orchestrates the overall replication and recovery processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If snapshots are created for data recovery, then data recovery capability is improved, but storage space consumption and management complexity increase

Engineering Contradiction:
Improvedata recovery capabilityVSAvoidstorage space consumption
Core Design Contradiction:
ReliabilityVSVolume of stationary object

Solution Approach 1:

The system changes the state of storage volumes by transitioning them between non-replicated and replicated modes. When converting from non-replicated to replicated, the volume is copied to additional storage devices, and the replication factor is adjusted based on policy. This parameter change allows flexible control over storage space consumption while maintaining data recovery capability.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

Instead of replicating entire storage volumes immediately, the system creates snapshots that capture only the necessary portions of data at specific points in time. This partial action approach allows data recovery without requiring full duplication of all data, reducing storage space consumption while maintaining recovery capability.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If conversion from non-replicated to replicated storage is implemented, then data redundancy is improved, but data migration time and processing overhead increase

Engineering Contradiction:
Improvedata redundancyVSAvoiddata migration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by creating snapshots before initiating replication. The storage manager issues quiesce instructions to pause data modification, captures the current state, and then proceeds with replication. This preliminary snapshot creation allows the conversion from non-replicated to replicated storage to start from a known good state, reducing the overall migration time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The replication process is designed to maintain continuity of useful action by allowing read operations to continue from the original non-replicated volume while replication occurs in the background. Once replication is complete, the system seamlessly transitions to the replicated state without requiring complete system downtime, thus maintaining continuous data availability.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS10877684B2Changing a distributed storage volume from non-replicated to replicated
Publication Date: 2020.12.29 RAKUTEN SYMPHONY INC
  • US10877684B2 patent drawing
  • US10877684B2 patent drawing
  • US10877684B2 patent drawing

AI summary

A distributed storage system stores a storage volume as segments that are allocated as needed and assigned VSIDs according to a monotonically increasing counter. The storage volume may be provisioned by an orchestration layer that manages the storage volumes as well as containers executing executable components of the storage volume. The storage volume may be replicated, such as by replicating slices of the storage volume. A primary copy of the slice may be moved from one node to another within the distributed storage system by designating it as a replica, creating a new replica at the new location which is then brought current. The new replica is then designated as the primary replica and the former primary replica may be deleted. A non-replicated storage volume may be converted to a replicated storage volume and vice versa.