Containerized Application Restoration With Phased Resource 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 minimal data loss and downtime during disaster recovery, with current methods lacking flexibility and resource optimization.

Innovation Solution

Implementing a multiphase and continuous restoration process for applications hosted on cloud orchestration platforms, which involves phased validation and incremental restoration of application resources, allowing for selective and efficient backup and recovery based on resource importance and dependency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional backup and restoration methods are used in cloud orchestration platforms, then application data can be restored after failure, but the restoration process consumes excessive resources and takes too much time

Engineering Contradiction:
Improveapplication restoration capabilityVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the application restoration process into multiple phases: capturing backup data, identifying and prioritizing critical resources, restoring only essential resources first, and then progressively restoring remaining resources. This phased approach divides the monolithic restoration task into manageable stages, enabling faster initial service recovery while maintaining reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-identifying and prioritizing critical resources before the actual restoration begins. The system analyzes resource dependencies and business impact in advance, creating a restoration priority queue. When failure occurs, this pre-prepared priority information enables immediate restoration of most critical resources without time-consuming analysis during the emergency recovery process.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If complete application data is restored, then data integrity is maintained, but resource consumption during restoration increases significantly

Engineering Contradiction:
Improvedata integrityVSAvoidrestoration resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts and identifies only the critical subset of resources that are essential for application functionality from the complete backup data. By using resource priority identification mechanisms, the system separates vital resources from non-essential ones, restoring only the necessary portion first. This extraction approach maintains data integrity for critical components while significantly reducing the amount of data that needs to be restored, thereby lowering resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by restoring only the essential portion of application data rather than the complete dataset. The system determines the minimum viable set of resources needed for application operation and restores that subset first, accepting that non-critical resources will be restored later. This partial restoration strategy achieves functional recovery with reduced resource expenditure.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If all application resources are restored simultaneously, then recovery is comprehensive, but the complexity of managing the restoration process increases

Engineering Contradiction:
Improvecomprehensive recoveryVSAvoidrestoration process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the restoration process into distinct phases with clear boundaries: resource identification and prioritization, critical resource restoration, validation, and remaining resource restoration. Each phase has specific objectives and completion criteria, transforming a complex monolithic process into a series of manageable, sequential tasks. This segmentation reduces process complexity while ensuring comprehensive recovery through systematic progression.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic adaptability into the restoration process by allowing the system to adjust restoration priorities based on real-time conditions and resource dependencies. The phased approach enables dynamic decision-making at each stage, where the system can validate critical resources before proceeding to less critical ones, adapting to actual system state rather than following a rigid predetermined sequence.

Inventive Principle:
Principle #15Dynamics

4Productivity

If critical resources are restored first, then service recovery is faster, but risk of incomplete restoration increases

Engineering Contradiction:
Improveservice recovery speedVSAvoidrestoration completeness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms at each phase of the restoration process. After restoring critical resources, the system validates their proper functioning and checks for any dependencies that require additional resources. This feedback loop ensures that the partial restoration of critical resources does not compromise overall restoration completeness, as the system continuously monitors and adjusts the restoration process based on validation results.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250328428A1Intelligent Application Restoration In Containerized Environments
Publication Date: 2025.10.23 NETAPP INC
  • US20250328428A1 patent drawing
  • US20250328428A1 patent drawing
  • US20250328428A1 patent drawing

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.