Multi-level Erasure System for Data Rebuild Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed data storage systems face challenges in minimizing data rebuild times and maintaining data durability due to device failures, especially with limited lifespan storage devices and increased data access latency, which can lead to performance degradation and overhead.

Innovation Solution

A rebuild strategy is implemented using a rebuild module connected to data storage devices, network controllers, and pods controllers, which proactively and reactively configures data storage to minimize rebuild times by predicting failures, altering strategies, and employing multi-level erasure to efficiently rebuild data across distributed systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional data storage systems store data across multiple devices for durability, then data reliability is improved, but rebuild time increases significantly when device failures occur

Engineering Contradiction:
Improvedata durabilityVSAvoidrebuild time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by proactively predicting device failures using machine learning models before they actually occur. When a failure is predicted, the system pre-rebuilds the data onto other healthy devices in the array. This means that when the actual failure happens, the data is already restored, eliminating the need for time-consuming rebuild operations and maintaining high data durability throughout the process.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If data is distributed across multiple storage devices, then data access capacity is improved, but data access latency increases

Engineering Contradiction:
Improvedata storage capacityVSAvoiddata access latency
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The system applies local quality by implementing a hierarchical data organization structure where frequently accessed data is cached in high-speed local memory (DRAM) on the storage device itself, while less frequently accessed data resides on slower storage media (NAND flash). This allows the system to maintain large total storage capacity while providing fast access latency for hot data through localized high-speed caching, rather than treating all data uniformly.

Inventive Principle:
Principle #3Local quality

3Productivity

If storage devices operate at high capacity utilization, then storage efficiency is improved, but device lifespan decreases due to increased wear

Engineering Contradiction:
Improvestorage efficiencyVSAvoiddevice lifespan
Core Design Contradiction:
ProductivityVSDuration of action of stationary object

Solution Approach 1:

The system implements feedback mechanisms by continuously monitoring device health metrics, wear levels, and performance characteristics. Based on this feedback, the system dynamically adjusts data placement strategies, migrating data away from devices showing signs of degradation or high wear. This allows the system to maintain high overall storage efficiency while extending individual device lifespans by balancing the workload and preventing any single device from becoming a bottleneck or failure point.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11334434B2Multi-level erasure system with cooperative optimization
Publication Date: 2022.05.17 SEAGATE TECH LLC
  • US11334434B2 patent drawing
  • US11334434B2 patent drawing
  • US11334434B2 patent drawing

AI summary

A data storage erasure system may have a host connected to a plurality of data storage devices via a network controller with each of the plurality of data storage devices and the network controller connected to a pods controller and each of the plurality of the data storage devices having a device controller. A rebuild strategy can be generated with a rebuild module connected to the plurality of data storage devices, the network controller, and the pods controller. The rebuild strategy may be directed to minimize data rebuild times in the event of a failure in the plurality of data storage devices by executing the rebuild strategy in response to a detected or predicted failure in at least one data storage device of the plurality of data storage devices.