Decentralized Data Protection Using Local Metadata Caches

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing decentralized data protection systems in multi-cloud environments face challenges such as costly data migration, excessive node communication, and limited feature integration due to reliance on distributed hash tables, which hinder efficient data protection and management across dynamic cloud platforms.

Innovation Solution

Implementing a decentralized data protection system that uses local metadata in each node to store and manage data protection policies, metadata, and protected data, allowing nodes to communicate directly and reduce reliance on distributed hash tables for data placement and health checks, while integrating advanced features like RAID and data archiving.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If decentralized data protection systems rely on distributed hash tables for data placement and node communication, then data can be stored across multiple nodes, but data migration costs increase and node communication becomes excessive

Engineering Contradiction:
Improvedata protectionVSAvoiddata migration costs
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary actions by maintaining local metadata caches that store data placement information, node status, and protection policies in advance. This allows nodes to make local decisions about data protection without frequent queries to the distributed hash table, reducing unnecessary data migration and node communication while maintaining reliable data protection across the decentralized network

Inventive Principle:
Principle #10Preliminary action

2Reliability

If decentralized data protection systems rely on distributed hash tables for data placement and health checks, then data can be distributed across nodes, but node communication overhead increases

Engineering Contradiction:
Improvedata protectionVSAvoidnode communication
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system applies local quality by enabling each node to maintain local metadata caches with data placement information and node status. This allows nodes to perform health checks and data protection operations using local information rather than continuously communicating with all other nodes via the distributed hash table, reducing communication overhead while maintaining reliable decentralized data protection

Inventive Principle:
Principle #3Local quality

3Reliability

If decentralized data protection systems use distributed hash tables, then data can be stored across multiple nodes, but advanced features like RAID and data archiving are limited

Engineering Contradiction:
Improvedata protectionVSAvoidfeature integration
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system implements universality by designing a metadata cache structure that can accommodate multiple data protection features including RAID configurations, data archiving policies, and replication strategies. The local metadata caches store comprehensive information about data placement, node status, and protection policies, enabling nodes to implement advanced features like RAID and data archiving within the decentralized environment without being limited by the basic distributed hash table functionality

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11010265B2Decentralized data protection system using local metadata
Publication Date: 2021.05.18 EMC IP HLDG CO LLC
  • US11010265B2 patent drawing
  • US11010265B2 patent drawing
  • US11010265B2 patent drawing

AI summary

In a decentralized system of nodes configured to provide data protection functionality, wherein at least a subset of the nodes store and share data using content-addresses managed via a distributed hash table in each of the subset of nodes, a given one of the subset of nodes locally stores: a data protection policy to be implemented by the given node; data protected on the given node; and metadata comprising information indicating placement of a given data set on one or more other ones of the subset of nodes. The given node accesses the locally stored metadata to manage protection of the given data set on the one or more other ones of the subset of nodes.