Metadata Synchronization via Cloud Intermediary for Data Protection Clusters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The networking infrastructure in certain geographic regions is less developed, leading to higher failure rates and longer synchronization times for data protection metadata, resulting in out-of-sync versions between centralized management systems and data management clusters, which can cause cluster management errors and failures.

Innovation Solution

Configuring data management clusters to export data protection metadata to a third-party server network with robust infrastructure, allowing the centralized management system to load this metadata for synchronized updates, leveraging the redundancy and high bandwidth of the cloud environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data protection metadata is synchronized over less developed networking infrastructure, then synchronization can be performed, but the failure rate increases and synchronization time increases

Engineering Contradiction:
Improvesynchronization reliabilityVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces a third-party server network as an intermediary between data management clusters and centralized management systems. This intermediary provides a robust communication channel that bypasses the limitations of less developed networking infrastructure, enabling reliable and fast metadata synchronization without direct peer-to-peer communication over problematic networks.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If data protection metadata is synchronized over less developed networking infrastructure, then synchronization can be performed, but the failure rate increases

Engineering Contradiction:
Improvesynchronization speedVSAvoidsynchronization reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The third-party server network acts as a mediator that provides both high speed and high reliability for metadata synchronization. By routing synchronization operations through this intermediary with robust infrastructure, the system achieves improved productivity (faster synchronization) while maintaining high reliability (lower failure rate).

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the communication dimension by introducing a new network path through a third-party server network. Instead of relying on the existing problematic network infrastructure, the system establishes a new communication dimension that offers superior performance characteristics for metadata transfer.

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

3Reliability

If data protection metadata is synchronized over less developed networking infrastructure, then synchronization can be performed, but out-of-sync versions occur between centralized management systems and data management clusters

Engineering Contradiction:
Improvemetadata version consistencyVSAvoidtime to achieve sync
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The third-party server network intermediary ensures metadata version consistency by providing a reliable and fast synchronization channel. This eliminates the out-of-sync version problems that occur over less developed infrastructure, while the high speed of the intermediary reduces the time required to achieve and maintain synchronization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250378191A1Incremental synchronization of metadata
Publication Date: 2025.12.11 RUBRIK INC
  • US20250378191A1 patent drawing
  • US20250378191A1 patent drawing
  • US20250378191A1 patent drawing

AI summary

Methods, systems, and devices for data management are described. Data management clusters may be configured to store metadata associated with providing data protection for a set of computing objects. A data management cluster may be triggered to export respective metadata to a cloud environment, where the respective metadata may be associated with providing data protection for one or more of the computing objects. Based on the export operation being triggered, the respective metadata may be downloaded from the cloud environment and written to a database that is configured to store a version of the metadata associated with providing the data protection for the set of computing objects. An interface for managing the operation of the data management clusters may be provided, where a content of the interface may reflect the version of the metadata stored at the database.