Disaster Recovery Policy Updates for Multi-Data-Center Failover

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Organizations face challenges in maintaining data integrity and availability across geographically distributed data centers, especially during disasters, requiring efficient and secure data synchronization with minimal latency and maximum availability.

Innovation Solution

Implementing automated disaster recovery operations with defined guidelines that utilize cloud systems and data centers to synchronize data across multiple locations, ensuring data integrity and availability through bidirectional or multidirectional architectures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If automated disaster recovery operations are implemented across geographically distributed data centers, then data availability and integrity are improved, but system complexity and coordination overhead increase

Engineering Contradiction:

Improvedata availabilityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system segments disaster recovery management into independent policy modules that can be configured, updated, and executed separately at different data centers. Each data center maintains local disaster recovery policies that can be independently managed, reducing overall system complexity while maintaining coordinated operation across multiple locations.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-configuring disaster recovery policies and guidelines before disasters occur. Policies are established in advance with defined procedures for data synchronization, failover, and recovery operations, eliminating the need for complex real-time decision-making during disaster events.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If frequent policy updates are implemented to adapt to changing disaster scenarios, then adaptability is improved, but system stability and operational consistency deteriorate

Engineering Contradiction:

Improvepolicy adaptabilityVSAvoidsystem stability

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The system implements dynamic policy management where disaster recovery policies can be updated and modified based on changing conditions. The system allows administrators to adjust policy parameters such as data synchronization frequency, failover thresholds, and recovery priorities without requiring complete policy reconfiguration, enabling adaptability while maintaining operational stability.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms that monitor disaster recovery operations and automatically adjust policy execution based on system state. When disasters are detected or conditions change, the system receives feedback from monitoring components and dynamically modifies policy application to maintain optimal performance while preserving system stability.

Inventive Principle:

Principle #23Feedback

3Reliability

If bidirectional or multidirectional data synchronization architectures are used, then data consistency across locations is improved, but network bandwidth consumption and latency increase

Engineering Contradiction:

Improvedata consistencyVSAvoidnetwork bandwidth

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system implements local quality by allowing different data centers to use different synchronization strategies based on their specific requirements and conditions. Primary data centers may use bidirectional synchronization for critical data, while secondary sites use unidirectional synchronization for less critical data, optimizing network bandwidth usage while maintaining data consistency where required.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system changes synchronization parameters dynamically based on network conditions, data criticality, and disaster recovery priorities. Policy updates can adjust synchronization frequency, data transfer volumes, and latency tolerances, allowing the system to maintain data consistency while adapting network resource consumption to current operational needs.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS12511602B2Method and system for disaster recovery policy management and updating

Publication Date: 2025.12.30 DELL PROD LP

AI summary

A method for managing policies for a disaster recovery of a data center includes receiving, at a cloud module, a first set of data that includes data center infrastructure information associated with the data center, a first prediction of resources, a list of assigned disaster recovery resources, and a status report of an application using the assigned disaster recovery resources; generating, by the cloud module and using the first set of data as training data, a learning model; generating a second prediction of resources using the learning model; and assigning, using the cloud module, disaster recovery resources to obtain assigned disaster recovery resources based on the second prediction, and the cloud module activates the assigned disaster recovery resources in response to determining that the data center has experienced a failure.