Container Disaster Recovery via Cloud Mapping and Volume Sync

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current disaster recovery solutions for mission-critical containerized applications in hybrid cloud deployments are costly due to the use of dedicated data centers for replication, and there is a need for a cost-effective method to maintain high availability and recover data seamlessly.

Innovation Solution

A processor-based disaster recovery manager generates mapping information in a public cloud, synchronizes volume data from a private cloud, and deploys containers in the public cloud during failures, allowing for cost-effective backup and recovery by utilizing on-demand public cloud services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dedicated data centers are used for replication in hybrid cloud deployments, then disaster recovery reliability is improved, but operational and maintenance costs increase

Engineering Contradiction:

Improvedisaster recovery reliabilityVSAvoidoperational and maintenance costs

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent uses container images as lightweight copies of applications instead of replicating entire data centers. Container images capture only the essential application code and dependencies, enabling disaster recovery without the overhead of full data center replication while maintaining reliability

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent employs ephemeral containers in the public cloud for disaster recovery purposes. These containers are created on-demand when failure is detected and can be terminated when no longer needed, reducing operational costs compared to maintaining permanent dedicated disaster recovery data centers

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

2Reliability

If dedicated disaster recovery solutions are implemented, then data availability during failures is improved, but device complexity and infrastructure requirements increase

Engineering Contradiction:

Improvedata availabilityVSAvoidinfrastructure complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The private cloud data center serves multiple functions: it acts as both the primary operational environment for containerized applications and the source for generating container images used in disaster recovery. This multi-functionality eliminates the need for separate dedicated disaster recovery infrastructure

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Container images serve as intermediaries between the private cloud data center and public cloud disaster recovery environment. These images encapsulate application state and can be rapidly deployed in the public cloud, simplifying the disaster recovery infrastructure compared to direct data center replication

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10489255B2Disaster recovery of containers

Publication Date: 2019.11.26 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

In one example, mapping information corresponding to a container running on a private data center may be generated in a public cloud by a processor-based disaster recovery manager. Further, volume data associated with the container may be synchronized to the public cloud based on the mapping information by the disaster recovery manager. Furthermore, a failure of the container running on the private data center may be determined by the disaster recovery manager. In response to the failure of the container running on the private data center, the container may be deployed in the public cloud using the synchronized volume data and the mapping information by the disaster recovery manager.