Centralized Data Protection Policy Distribution Across Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional backup systems face challenges in managing complex data protection topologies with multiple nodes and policies, requiring manual setup of data archiving and storage policies, which is tedious and impractical due to the vast number of data types, regulatory requirements, and bandwidth limitations.

Innovation Solution

A data system that enables synchronized data protection operations across multiple nodes, allowing for efficient setup of data protection policies through a central command module, with nodes communicating sequence information to perform data protection operations such as backups, mirroring, and archiving in a synchronized manner.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual setup of data protection policies is used for each node, then policy customization is possible, but system complexity and setup time increase significantly

Engineering Contradiction:
Improvepolicy customizationVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the policy management functionality into a centralized command module that distributes policies to multiple nodes automatically. This combining of central化的 policy definition with distributed execution resolves the contradiction by providing both customization capability and reduced complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The sequence information acts as an intermediary mechanism that translates high-level policy definitions into node-specific execution instructions. This intermediary layer allows policy customization without requiring manual configuration at each node, thus reducing system complexity while maintaining adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual configuration of data archiving policies is performed, then compliance requirements can be met, but the process becomes tedious and impractical

Engineering Contradiction:
Improvecompliance assuranceVSAvoidconfiguration ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements self-service by automatically generating and distributing compliance policies to nodes based on central化的 definitions. The nodes autonomously execute their designated data protection operations without requiring manual intervention, thus ensuring compliance while greatly easing operation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The command module performs preliminary action by pre-configuring and distributing policy sequences to all nodes before execution begins. This advance preparation ensures compliance requirements are built into the system architecture rather than manually enforced, making the process both reliable and easy to operate.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If data protection operations are performed without synchronization, then operational speed is maintained, but data consistency across nodes deteriorates

Engineering Contradiction:
Improveoperation speedVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSStability of the object's composition

Solution Approach 1:

The patent implements feedback mechanisms where nodes report their operational status and data state back to the command module. This feedback loop enables the system to maintain synchronization and data consistency across distributed nodes while allowing parallel operations to proceed at high speed.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The data protection operations are segmented into discrete, independently executable tasks that can be performed in parallel across nodes. Each node executes its segmented portion of the workflow independently but contributes to the overall synchronized outcome, maintaining both speed and consistency.

Inventive Principle:
Principle #1Segmentation

4Device complexity

If centralized data storage is used, then backup management is simplified, but bandwidth restrictions limit client access speed

Engineering Contradiction:
Improvemanagement complexityVSAvoidaccess speed
Core Design Contradiction:
Device complexityVSSpeed

Solution Approach 1:

The patent transitions from a single centralized storage dimension to a distributed multi-dimensional storage architecture. Data is replicated across multiple nodes in the network, allowing clients to access data from geographically and network-wise distributed locations, thus maintaining management simplicity while dramatically improving access speed through parallel pathways.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11030056B2Data system for managing synchronized data protection operations at nodes of the data system, source node and destination node, and computer program product for use in such data system
Publication Date: 2021.06.08 HITACHI VANTARA LLC
  • US11030056B2 patent drawing
  • US11030056B2 patent drawing
  • US11030056B2 patent drawing

AI summary

The present application relates to a data system for managing synchronized data protection operations at plural nodes of the data system, the data system including at least a first node and a second node, wherein the first node is communicably connected to the second node and is configured to operate on the basis of first sequence information, the first node being configured to perform a first data protection operation and to transmit a synchronization notification to the second node on the basis of respective instructions included in the first sequence information, and wherein the second node is configured to receive the synchronization notification from the first node and to operate on the basis of second sequence information, the second node being configured to perform a second data protection operation upon receipt of the synchronization notification on the basis of a respective instruction included in the second sequence information.