Cluster Replica Exchange for Multi-Cluster Failover Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computing environments face challenges in efficiently managing and recovering multi-cluster operations, particularly in scenarios involving limited computational resources and dynamic scaling needs, where redundancy and failover mechanisms are inadequate.

Innovation Solution

A system and method for generating a cluster exchange object that includes identifiers and configuration data, allowing a secondary cluster to replicate and instantiate components of a primary cluster, ensuring redundancy and enabling seamless failover by transmitting snapshot objects to maintain data consistency across clusters.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cluster replication is implemented to improve reliability and enable failover, then redundancy and fault tolerance are improved, but system complexity and resource consumption increase

Engineering Contradiction:
Improvecluster reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a replica cluster that copies the configuration and state of the primary cluster. The replica cluster maintains identifiers and segments of data from the primary cluster, enabling failover capability without requiring complete system duplication. This selective copying approach improves reliability while controlling complexity.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent segments the cluster state into identifiers and data segments that can be independently transmitted and managed. The replica cluster receives and reconstructs these segmented components to form a functional replica, reducing the complexity of full cluster replication while maintaining reliability.

Inventive Principle:
Principle #1Segmentation

2Reliability

If full cluster replication is performed to ensure complete redundancy, then failover capability is improved, but performance impact on primary cluster and resource usage increase

Engineering Contradiction:
Improvefailover capabilityVSAvoidprimary cluster performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts only the essential components needed for replication - identifiers and data segments - from the primary cluster rather than copying the entire cluster state. This extraction approach enables failover capability while minimizing the performance impact on the primary cluster by reducing the amount of data that needs to be transmitted and processed.

Inventive Principle:
Principle #2Taking out (Extraction)

3Loss of time

If cluster recovery mechanisms are enhanced to reduce downtime, then service continuity is improved, but computational resources and time for recovery processes increase

Engineering Contradiction:
Improverecovery downtimeVSAvoidcomputational resources
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The patent performs preliminary actions by maintaining a replica cluster that is pre-configured with identifiers and data segments before failure occurs. When the primary cluster fails, the replica can immediately take over, reducing recovery downtime. The computational resources are invested in advance during normal operation rather than during the critical recovery period.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12632338B2Multi-cluster recovery
Publication Date: 2026.05.19 RAKUTEN SYMPHONY INC
  • US12632338B2 patent drawing
  • US12632338B2 patent drawing
  • US12632338B2 patent drawing

AI summary

A first cluster creates a cluster exchange object including identifiers of components of the first cluster and segments of data of the first cluster along with configuration data, such as access points and credentials. The first cluster transmits the object to a second cluster that instantiates copies of the components and retrieves the segments from the first cluster to become a replica of the second cluster. The second cluster may then commence execution upon failure of the primary cluster and restore the primary cluster. The primary cluster may send snapshot objects to the second cluster to communicate changes to the primary cluster and the snapshot objects may also be used to restore the primary cluster following failure. The components of a cluster may be represented in a directory structure and data describing a component may be retrieved in response to user interactions with a representation of the directory structure.