Phased Application Restoration for Containerized Disaster Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud orchestration platforms face challenges in efficiently managing application restoration processes, particularly in ensuring data integrity and minimizing downtime during disaster recovery, due to the lack of phased or continuous validation of resources in backup and restoration operations.

Innovation Solution

Implementing a multiphase restoration process that validates each phase of application resources before proceeding to the next, and a continuous restoration process that incrementally mirrors application data to maintain an up-to-date copy, allowing for selective and efficient resource management based on importance and dependencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional backup and restoration mechanisms are used in Kubernetes environments, then application data can be captured and stored for recovery, but the restoration process cannot be validated in phases leading to prolonged downtime and inability to meet RTO objectives

Engineering Contradiction:
Improvedata integrityVSAvoidrestoration downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The restoration process is divided into multiple phases where different sets of application resources are restored in sequence. Each phase restores a subset of resources (e.g., namespace A, then namespace B, then namespace C) allowing for incremental validation and reducing overall restoration downtime while maintaining data integrity through phase-by-phase verification

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary validation of restored resources in each phase before proceeding to the next phase. This preliminary action ensures data integrity is verified incrementally throughout the restoration process, preventing propagation of errors and enabling faster recovery by validating only the current phase rather than waiting for complete restoration

Inventive Principle:
Principle #10Preliminary action

2Reliability

If complete application mirroring is implemented across multiple locations, then fault tolerance and business continuity are enhanced, but the complexity of managing and validating all resources increases significantly

Engineering Contradiction:
Improvefault toleranceVSAvoidrestoration management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The application resources are segmented into multiple namespaces or resource groups that can be mirrored and restored independently. This segmentation reduces the complexity of managing complete application mirrors by allowing selective restoration of specific namespaces rather than requiring coordination of all resources simultaneously

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements partial mirroring where only critical namespaces or resource subsets are fully replicated across locations, rather than complete application mirroring. This partial action approach maintains sufficient fault tolerance for business continuity while reducing the complexity of managing and validating all application resources

Inventive Principle:
Principle #16Partial or excessive action

3Ease of manufacture

If all application resources are restored simultaneously in a single phase, then the restoration process is simpler to implement, but validation becomes difficult and downtime cannot be minimized

Engineering Contradiction:
Improverestoration implementation simplicityVSAvoidresource validation accuracy
Core Design Contradiction:
Ease of manufactureVSMeasurement precision

Solution Approach 1:

Resources are divided into discrete phases with clear boundaries and dependencies. Each phase contains a specific set of resources that can be restored and validated independently, maintaining implementation simplicity through structured segmentation while enabling precise validation of each phase's resources before proceeding to the next

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4636595A1Intelligent application restoration in containerized environments
Publication Date: 2025.10.22 NETAPP INC
  • EP4636595A1 patent drawingFigure 1A
  • EP4636595A1 patent drawingFigure 1B
  • EP4636595A1 patent drawingFigure 1C

AI summary

Systems, methods, and software are disclosed herein for phased-in restoration of an application hosted on a cloud orchestration platform in various implementations. In an implementation, a computing apparatus receives a configuration for a multiphase restoration process for restoring resources of an application to a destination platform, the restoration occurring in phases. To implement the multiphase restoration process, the computing apparatus captures a backup of application data of the application, then restores a phase including selected resources of the application to the destination platform based on the backup and according to the configuration. The computing apparatus validates the selected resources at the destination platform, then restores a next phase to the destination platform based on the backup and according to the configuration.