Protection Sets for Archival Storage MTDL

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Redundant Array of Independent Nodes (RAIN) storage systems face challenges in achieving a high mean time to data loss (MTDL) due to the random distribution of data across nodes, which can lead to data loss when multiple nodes within a cluster fail unexpectedly.

Innovation Solution

Implementing a data protection management system that organizes nodes into protection sets, ensuring all copies of a data object are stored within the same protection set, thereby reducing the likelihood of data loss by containing failures within a specific set rather than across the cluster.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is randomly distributed across nodes in a RAIN storage system, then storage capacity and scalability are improved, but mean time to data loss (MTDL) deteriorates due to potential simultaneous node failures

Engineering Contradiction:
Improvemean time to data lossVSAvoiddata distribution complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments nodes into distinct protection sets, where each set contains a specific number of nodes (e.g., 3 nodes for DPL=2). This segmentation ensures that data copies are confined within protected groups, so that failures in one protection set do not affect data availability in other sets. The segmentation directly addresses the MTDL problem by creating isolated failure domains.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary organization of nodes into protection sets before data storage operations. The protection manager pre-establishes which nodes belong together in protection sets and maintains this structure dynamically. This preliminary action ensures that when data is stored, copies are automatically placed within the same protection set, preventing data loss even if multiple nodes fail simultaneously across different sets.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If copies of data objects are distributed across the entire cluster, then storage efficiency is improved, but data loss risk increases when multiple nodes fail

Engineering Contradiction:
Improvedata availabilityVSAvoiddata loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system applies local quality by ensuring that all copies of a given data object are stored within the same protection set, rather than distributing them randomly across the entire cluster. This local concentration of copies within a defined group (protection set) ensures that as long as the protection set remains intact, data availability is maintained. The local quality principle directly prevents data loss by keeping replicas together in protected groups.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements beforehand cushioning by creating protection sets that act as buffers against node failures. Each protection set is designed to tolerate a certain number of failures (DPL-1) without losing data. This cushioning effect is established in advance through the protection set structure, so when failures occur, the data remains protected within the set boundaries.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Reliability

If nodes are organized into protection sets with constrained copy distribution, then mean time to data loss is improved, but system management complexity increases

Engineering Contradiction:
Improvemean time to data lossVSAvoiddata management ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The protection manager implements self-service by automatically managing protection set formation, node membership, and data copy placement. When nodes are added or removed from the cluster, the protection manager dynamically reconfigures protection sets and redistributes data copies without manual intervention. This self-service capability maintains high MTDL through proper protection set organization while keeping operations simple through automation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback mechanisms where the protection manager continuously monitors node status, failure conditions, and protection set integrity. When failures are detected, the system provides feedback to trigger automatic recovery actions, such as redistributing data copies to maintain the required protection level. This feedback loop ensures reliable data protection while automating management tasks.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9672372B2Method for improving mean time to data loss (MTDL) in a fixed content distributed data storage
Publication Date: 2017.06.06 HITACHI VANTARA LLC
  • US9672372B2 patent drawing
  • US9672372B2 patent drawing
  • US9672372B2 patent drawing

AI summary

An archival storage cluster of preferably symmetric nodes includes a data protection management system that periodically organizes the then-available nodes into one or more protection sets, with each set comprising a set of n nodes, where “n” refers to a configurable “data protection level” (DPL). At the time of its creation, a given protection set is closed in the sense that each then available node is a member of one, and only one, protection set. When an object is to be stored within the archive, the data protection management system stores the object in a given node of a given protection set and then constrains the distribution of copies of that object to other nodes within the given protection set. As a consequence, all DPL copies of an object are all stored within the same protection set, and only that protection set. This scheme significantly improves MTDL for the cluster as a whole, as the data can only be lost if multiple failures occur within nodes of a given protection set. This is far more unlikely than failures occurring across any random distribution of nodes within the cluster.