Simulated Management Module for Fast Data Recovery

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Distributed data storage systems face inefficiencies in data recovery due to high bandwidth and processing power requirements during rebalancing after a storage device failure, leading to prolonged downtime and performance impact.

Innovation Solution

A method involving the creation of a simulated management module to redirect data to a second storage device, followed by the creation of a permanent management module and deletion of the simulated module, reducing rebalancing disturbances and optimizing data transfer within the same node to conserve network bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional rebalancing is performed after storage device failure, then data reliability is restored, but network bandwidth consumption increases and processing power efficiency decreases

Engineering Contradiction:

Improvedata reliabilityVSAvoidnetwork bandwidth consumption

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary data copying to a temporary storage device before the actual rebalancing operation. By pre-positioning data locally, the system reduces the need for extensive network bandwidth consumption during the subsequent rebalancing phase, thus resolving the contradiction between restoring data reliability and minimizing network energy loss.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

A temporary storage device acts as an intermediary between the failed storage device and the target storage device. This intermediary holds data locally during the transition period, reducing network bandwidth requirements while ensuring data reliability is maintained through the coordinated data transfer process.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If traditional rebalancing is performed after storage device failure, then data replication is completed, but system performance deteriorates due to high processing power requirements

Engineering Contradiction:

Improvedata replicationVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary data copying to a temporary storage device before initiating full rebalancing. This preliminary action completes part of the data replication requirement locally, reducing the processing power burden during the main rebalancing operation and thereby maintaining better system performance while ensuring data replication completeness.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The rebalancing process is segmented into multiple phases: preliminary local copying to temporary storage, followed by gradual data migration to target devices. This segmentation distributes the processing load over time, preventing system performance deterioration while ensuring complete data replication.

Inventive Principle:

Principle #1Segmentation

3Reliability

If traditional rebalancing is performed after storage device failure, then data availability is restored, but recovery time increases

Engineering Contradiction:

Improvedata availabilityVSAvoidrecovery time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary data copying to a temporary storage device immediately upon detecting failure. This preliminary action restores data availability quickly by making data accessible locally, while the subsequent rebalancing operates in the background, thus reducing overall recovery time without compromising data availability.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous data availability during the recovery process by using temporary storage devices to hold data accessible to the system. While rebalancing continues in the background, data operations can proceed without interruption, significantly reducing the effective recovery time while maintaining data availability.

Inventive Principle:

Principle #20Continuity of useful action

4Loss of energy

If simulated management module is created for data redirection, then network bandwidth is conserved, but device complexity increases

Engineering Contradiction:

Improvenetwork bandwidth savingsVSAvoidmanagement module complexity

Core Design Contradiction:

Loss of energyVSDevice complexity

Solution Approach 1:

A simulated management module acts as an intermediary layer that redirects I/O requests to appropriate storage devices. While this adds some complexity, it enables local data access and significantly reduces network bandwidth consumption. The module's complexity is justified by the substantial network energy savings achieved through intelligent request routing.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The simulated management module performs multiple functions: redirecting I/O requests, managing temporary storage devices, coordinating data transfer, and monitoring system state. This multi-functionality consolidates several operations into a single component, making the added complexity worthwhile given the network bandwidth savings and operational efficiency gains.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11023159B2Method for fast recovering of data on a failed storage device

Publication Date: 2021.06.01 LENOVO GLOBAL TECHNOLOGIES SWITZERLAND INTERNATIONAL GMBH

AI summary

A method for recovering data on a failed storage device includes detecting that a first storage device has a failure, creating a simulated management module where the simulated management module linked with a second storage device, writing a replica of at least some of the data as stored in the first storage device to a second storage device, creating a permanent management module and deleting the simulated management module.