Storage Reliability Prediction via Dependency Simulation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Predicting the reliability of large-scale storage systems is challenging due to the complexity of scaling, redundancy schemes, distribution architectures, and component dependencies, which affects data integrity and economic decisions in data centers.

Innovation Solution

A method that identifies components and dependencies within a storage system, simulates its operation based on size, strength, and placement schemes, and determines the mean time between loss events to assess reliability, using combinatorial models and event-based simulation to handle arbitrary failure models and dependencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If large scale storage systems are implemented with extreme scaling to meet data intensive application requirements, then storage capacity and performance are improved, but the risk of data loss from component failures increases

Engineering Contradiction:
Improvestorage capacityVSAvoiddata loss risk
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The storage system is divided into multiple independent racks, each containing multiple hosts and drives. This segmentation allows the system to scale capacity by adding more racks while limiting the blast radius of failures to individual racks. The patent implements this by organizing storage resources into discrete rack units that can be independently managed and replaced without affecting the entire system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically adjusts redundancy parameters based on the desired reliability level and storage capacity requirements. By changing the redundancy factor (ratio of data drives to parity drives) and erasure code strength, the system can optimize the balance between storage capacity and data loss risk for different deployment scenarios.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If redundancy schemes such as replication and erasure codes are implemented to reduce data loss probability, then reliability is improved, but system complexity and storage overhead increase

Engineering Contradiction:
Improvedata loss probabilityVSAvoidredundancy scheme complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements redundancy by creating multiple copies of data across different racks using replication and erasure coding techniques. Instead of complex active-active failover mechanisms, the patent uses straightforward copy-based approaches where data is duplicated or encoded across multiple physical locations, simplifying the overall system architecture while maintaining high reliability.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system allows dynamic adjustment of redundancy parameters such as the replication factor and erasure code strength (k-out-of-n configurations). This enables operators to tune the balance between reliability and complexity based on specific requirements, choosing simpler replication schemes for lower-risk applications and more sophisticated erasure codes for critical data.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If spread placement scheme is used to distribute files randomly across all drives, then storage utilization and flexibility are improved, but aggregate reliability decreases compared to partitioned placement

Engineering Contradiction:
Improveplacement flexibilityVSAvoidaggregate reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a hierarchical placement architecture that segments the storage system into rack-level partitions and drive-level distributions. Files are first assigned to specific racks based on redundancy requirements, then distributed across drives within those racks. This segmentation allows spread placement to be applied locally within racks while maintaining global reliability through rack-level isolation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different placement strategies are applied at different levels of the storage hierarchy. The patent uses partitioned placement at the rack level to ensure reliability isolation, while allowing spread placement at the drive level within each rack to maintain flexibility and utilization. This local differentiation of placement qualities optimizes both reliability and adaptability.

Inventive Principle:
Principle #3Local quality

4Measurement precision

If component dependencies such as host, rack, and data center failures are accounted for in reliability modeling, then prediction accuracy is improved, but computational complexity increases

Engineering Contradiction:
Improvereliability prediction accuracyVSAvoidmodeling complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The reliability modeling process is segmented into hierarchical levels corresponding to the physical architecture: drive-level failure models, host-level aggregation, rack-level dependency modeling, and data center-level analysis. This segmentation allows complex multi-level dependencies to be modeled systematically by combining simpler models at each level, reducing the overall computational complexity while maintaining accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediate aggregation layers in the reliability model that summarize the behavior of lower-level components before feeding into higher-level analyses. For example, individual drive failures are aggregated into host-level failure rates, which are then combined with rack-level dependencies. These intermediary layers simplify the computational burden by reducing the state space that needs to be analyzed at each level.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10002039B2Predicting the reliability of large scale storage systems
Publication Date: 2018.06.19 AT&T INTELLECTUAL PROPERTY I L P
  • US10002039B2 patent drawing
  • US10002039B2 patent drawing
  • US10002039B2 patent drawing

AI summary

An aspect includes identifying a set of components of a storage system and determining dependencies among constituent components in the set of components. At least one of the components' ability to function is dependent on at least one other of the components' ability to function. The set of components includes at least one data storage component and at least one computation component configured to operate within at least one datacenter. An aspect also includes identifying a size, strength, and storage placement scheme of the storage system; simulating operation of the storage system based on the identified size, strength, and storage placement scheme; and determining a mean time between loss event from the simulated operation. The mean time between loss event factors in the dependencies among the constituent components. An aspect further includes assessing reliability of the storage system as a function of the mean time between loss event.