Data Center Fault Tolerance Validation via Resource Graph Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The process of building fault-tolerant data centers is complex and error-prone, often requiring manual coordination and multiple iterations to achieve the desired configuration, which increases the time and cost of deployment.

Innovation Solution

A data center fault tolerance determination system that receives configuration information, constructs a resource graph representing infrastructure resources and their connections, and analyzes this graph to determine if the data center meets specified fault tolerance levels and fault domains, providing notifications on the fault tolerance status of each resource.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual coordination and control tasks are used to build a data center, then flexibility and adaptability are maintained, but the process becomes error-prone and time-consuming

Engineering Contradiction:
Improvefault toleranceVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces manual coordination and control tasks with an automated system that uses configuration information to construct resource graphs and determine fault tolerance. The system automatically analyzes connectivity between infrastructure resources and validates fault domain separation, eliminating the need for manual verification while reducing deployment time and errors.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service by automatically validating fault tolerance configurations without requiring manual intervention. The automated determination system processes configuration information, constructs resource graphs, and independently verifies whether fault tolerance requirements are met, allowing the system to validate itself rather than requiring human operators to manually check each connection.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If manual coordination between various teams is used, then configuration flexibility is maintained, but the process becomes complex and error-prone

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidcoordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent replaces complex manual coordination between various teams with an automated system that processes configuration information and constructs resource graphs. The system automatically analyzes connectivity and validates fault domain separation, eliminating the need for manual coordination while maintaining configuration flexibility through automated interpretation of configuration files.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system introduces an intermediary automated validation layer between configuration definition and deployment. This intermediary system receives configuration information, constructs resource graphs, and validates fault tolerance requirements, serving as a mediator that ensures correctness without requiring direct manual coordination between multiple teams.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If multiple iterations are performed to achieve desired configuration, then configuration accuracy is improved, but deployment time increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoiddeployment efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent applies preliminary action by automatically validating fault tolerance configurations during the deployment process itself, rather than requiring multiple iterations of manual checking. The system performs the validation upfront by constructing resource graphs and analyzing connectivity to ensure fault domain separation is correct before deployment completes, eliminating the need for iterative corrections.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system replaces multiple manual iteration cycles with a single automated validation process. The automated determination system processes configuration information, constructs resource graphs, and immediately determines whether fault tolerance requirements are met, providing configuration accuracy without the time cost of multiple manual iterations.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20250123914A1Techniques for performing fault tolerance validation for a data center
Publication Date: 2025.04.17 ORACLE INT CORP
  • US20250123914A1 patent drawing
  • US20250123914A1 patent drawing
  • US20250123914A1 patent drawing

AI summary

Techniques are described for deploying a fault tolerant data center by determining that the physical infrastructure deployment of the data center meets the fault tolerance levels and the fault domains specified for the data center. Techniques are described for obtaining configuration information related to various infrastructure resources deployed in a data center. A resource graph for the data center is generated based on the configuration information. The resource graph represents a logical representation of a set of vertices representing the physical and logical resources used to power a data center and a set of edges that connect the set of vertices. The resource graph is used to determine if a set of infrastructure nodes deployed in the data center meet the fault tolerance levels and fault domains specified for the data center. Results indicative of whether a deployed data center is fault tolerant are then transmitted to a user.