Local Protect Image Storage for Critical Instance Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computing installations face challenges in maintaining constant availability of critical components due to limited computational resources and heavy loads, especially in edge servers, which can lead to delays and failures during recovery processes.

Innovation Solution

The implementation of a local protect image system where critical application instances are instantiated from an executable image and stored on a storage device, allowing for rapid recovery without network delays, even in the absence of a network connection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If critical application instances are restored by retrieving executable images from remote image stores over the network, then the system can maintain centralized image management, but network delays and failures can occur during recovery processes

Engineering Contradiction:
Improveavailability of critical componentsVSAvoidrecovery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by creating and storing protective copies of executable images locally on the host computing device before failures occur. When a critical application instance fails, the system can immediately restore from the locally stored protective copy without needing to retrieve images from remote image stores, thus eliminating network delays during recovery while maintaining centralized image management capabilities.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If executable images are stored locally on host computing devices, then recovery can proceed without network delays, but computational resources and storage capacity are consumed

Engineering Contradiction:
Improverecovery capabilityVSAvoidstorage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by selectively storing protective copies of executable images only on host computing devices that run critical application instances, rather than universally on all devices. This targeted approach ensures that storage resources are consumed only where necessary for maintaining recovery capability of critical components, optimizing the balance between local recovery reliability and storage resource utilization.

Inventive Principle:
Principle #3Local quality

3Reliability

If protective copies are created for all application instances, then complete redundancy is achieved, but resource consumption increases significantly

Engineering Contradiction:
Improverecovery assuranceVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by creating protective copies only for critical application instances rather than all application instances. The system identifies and prioritizes critical components that require constant availability, applying the protective copying mechanism selectively to these specific instances. This partial approach provides sufficient recovery assurance for critical functions while avoiding the excessive resource consumption that would result from protecting all application instances.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20250298683A1Local Protect Image for Critical Applications
Publication Date: 2025.09.25 RAKUTEN SYMPHONY INC
  • US20250298683A1 patent drawing
  • US20250298683A1 patent drawing
  • US20250298683A1 patent drawing

AI summary

A critical executable image is used to instantiate an instance on a computing device. The executable image is further saved on the storage device. In response to a failure of the instance, the instance may be restored from the locally stored executable image. The executable image may be of a container and corresponding application image. The computing device may receive a specification, e.g., container specification, to instantiate the instance, the specification including an annotation instructing the computing device to locally store the executable image after instantiation.