Automated Disaster Recovery Service Failover Coordination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current disaster recovery solutions for computing resource service providers are complex and difficult to manage, as they require manual data duplication across multiple data regions to ensure redundancy, leading to potential downtime and data loss due to natural disasters or other failures.

Innovation Solution

A disaster recovery service that coordinates failover from one data region to another, utilizing a graphical user interface and API calls to specify recovery point objective (RPO) and recovery time objective (RTO) periods, replicating and maintaining resources with dependencies, and testing failover scenarios to ensure minimal downtime and data availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual data duplication is used across multiple data regions, then data redundancy is improved, but device complexity and ease of operation deteriorate

Engineering Contradiction:
Improvedata redundancyVSAvoidfailover plan complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables automated failover where the disaster recovery service automatically detects failures, selects appropriate data regions, and executes failover without manual intervention. This self-service mechanism maintains data redundancy while eliminating the complexity of manual failover management.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-configures failover plans and maintains standby data regions in advance. When a failure occurs, the pre-prepared resources and automated protocols enable immediate failover, reducing both the complexity of manual planning and the time required for recovery.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual data duplication is used across multiple data regions, then data redundancy is improved, but loss of time increases

Engineering Contradiction:
Improvedata redundancyVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The automated disaster recovery service continuously monitors data region health and automatically triggers failover upon detecting failures. This eliminates the time delay associated with manual detection and response, maintaining data redundancy while minimizing downtime.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Standby data regions and failover protocols are pre-configured and ready in advance. When failures occur, the system can immediately activate pre-prepared resources without waiting for manual intervention, thus maintaining redundancy while reducing downtime.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If automated failover coordination is implemented, then loss of time is reduced, but device complexity increases

Engineering Contradiction:
ImprovedowntimeVSAvoidservice coordination complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The disaster recovery service is designed as a universal platform that can coordinate failover across multiple data regions and service types through standardized protocols. This multi-functionality enables automated failover without requiring separate complex systems for each scenario, thus reducing downtime while managing complexity through standardization.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Reliability

If resources are replicated to alternative data regions, then reliability is improved, but loss of substance increases

Engineering Contradiction:
Improvedata availabilityVSAvoiddata duplication overhead
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The system replicates data selectively to specific alternative data regions based on failure scenarios and service requirements. Rather than duplicating all data everywhere, it maintains appropriate redundancy locally in target regions, improving data availability while minimizing unnecessary duplication overhead.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11126513B2Disaster recovery service
Publication Date: 2021.09.21 AMAZON TECH INC
  • US11126513B2 patent drawing
  • US11126513B2 patent drawing
  • US11126513B2 patent drawing

AI summary

A customer may use a disaster recovery service to generate a disaster recovery scenario in order to make certain resources available to the customer in the event of a data region failure. The customer may specify a recovery point objective, a recovery time objective and a recovery data region for the scenario. Accordingly, the disaster recovery service may coordinate with one or more other services provided by the computing resource service provider to reproduce the customer resources and other resources necessary to support the customer resources. These reproduced resources may be transferred to the recovery data region based at least in part on the parameters specified by the customer. In the event of a data region failure, the disaster recovery service may update the domain name system to resolve any customer requests for the customer resources to the recovery data region.