Master Node Data Backup Coordination in Distributed Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed storage systems, data backup is challenging due to the lack of centralized control, leading to inefficient backup processes, prolonged backup times, and resource wastage, especially in large-scale environments.

Innovation Solution

A data backup method and system that employs a master cooperative service node to initiate and manage backup operations across storage nodes, utilizing a distributed file lock service node for contention control and policy dissemination, allowing for concurrent backup operations and efficient resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data backup is performed in a distributed storage system without centralized control, then each node can independently perform backup operations, but backup time becomes excessively long and storage resources are wasted due to redundant copies

Engineering Contradiction:
Improvebackup speedVSAvoidbackup time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent introduces a master cooperative service node as an intermediary that coordinates backup operations across all storage nodes. This mediator receives backup requests, determines which nodes need to perform backups based on data distribution and copy relationships, and orchestrates their concurrent execution. This resolves the contradiction by enabling coordinated parallel backup (improving speed) while avoiding redundant operations (reducing time loss) through centralized intelligence.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The backup operation is segmented into independent tasks assigned to different storage nodes based on their data subsets. Each node performs backup independently on its local data, allowing parallel execution. The master node segments the overall backup task by identifying which nodes need to participate, enabling concurrent backup operations that reduce total backup time while avoiding redundancy through intelligent task allocation.

Inventive Principle:
Principle #1Segmentation

2Productivity

If all storage nodes perform backup operations independently without coordination, then backup operations can be concurrent, but storage resources are wasted due to lack of control over repeated copies

Engineering Contradiction:
Improvebackup concurrencyVSAvoidstorage resource waste
Core Design Contradiction:
ProductivityVSLoss of substance

Solution Approach 1:

The master cooperative service node implements feedback mechanisms by monitoring data distribution information and copy relationships across storage nodes. Before initiating backups, the master node receives feedback about which data subsets are already backed up and which nodes hold copies. This feedback enables the master node to intelligently assign backup tasks only to nodes that need them, achieving concurrent backup operations while preventing storage resource waste through informed decision-making.

Inventive Principle:
Principle #23Feedback

3Loss of substance

If a centralized backup mechanism controls all backup operations, then resource allocation is efficient and redundancy is avoided, but the system complexity increases and backup control becomes more difficult

Engineering Contradiction:
Improvestorage resource efficiencyVSAvoidbackup mechanism complexity
Core Design Contradiction:
Loss of substanceVSDevice complexity

Solution Approach 1:

The patent extracts the complex coordination logic from individual storage nodes and concentrates it in a dedicated master cooperative service node. This separation allows storage nodes to remain simple and focused on their core backup functions, while the master node handles the complex tasks of coordinating backups, managing copies, and optimizing resource allocation. This extraction reduces overall system complexity by centralizing intelligence where it's most needed.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The master cooperative service node serves multiple functions: it coordinates backup operations, manages data distribution information, tracks copy relationships, and optimizes resource allocation. By consolidating these diverse functions in a single multi-functional node, the system avoids the complexity of having each node perform all these roles independently, while still achieving efficient centralized control over the distributed backup process.

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

4Reliability

If data backup is performed in a query or traversal manner by a client, then data can be obtained from the server side, but concurrent backup cannot be performed and backup time becomes excessively long for large data scales

Engineering Contradiction:
Improvedata backup reliabilityVSAvoidbackup efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically adapts the backup process by having the master cooperative service node determine in real-time which storage nodes need to perform backups based on current data distribution and copy status. This dynamic approach allows the system to optimize backup operations continuously, enabling concurrent execution across multiple nodes when appropriate while maintaining data reliability through coordinated control. The dynamic nature of the master node's decision-making enables both high reliability and improved efficiency simultaneously.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3185125B1Data backup method, system, node and computer storage media
Publication Date: 2019.04.03 ZTE CORP
  • EP3185125B1 patent drawingFigure 1
  • EP3185125B1 patent drawingFigure 2
  • EP3185125B1 patent drawingFigure 3

AI summary

Disclosed in embodiments of the present invention are a data backup method, system, node and a computer storage media. The data backup method comprises: after a cooperative service node is determined to be a master cooperative service node, the master cooperative service node acquires backup rules; once backup trigger conditions are satisfied, the master cooperative service node initiates backup operations according to the backup rules.