Program Recovery Using Storage Compatibility Checks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing program recovery methods face issues with compatibility between storage arrangements of data in recovery copies and current program versions, leading to faulty operations and prolonged downtime due to the need for applying update patches.

Innovation Solution

A selective restoration engine dynamically selects program recovery techniques based on compatibility checks of storage arrangements and estimated patch application times to avoid incompatible recoveries, opting for partial or full recovery as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full program recovery is performed using a recovery copy, then program availability is restored, but compatibility issues between storage arrangements and current program versions cause faulty operations

Engineering Contradiction:

Improveprogram operation reliabilityVSAvoidstorage arrangement compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs a compatibility check between the storage arrangement in the recovery copy and the current program version before executing the full recovery. This preliminary action identifies incompatible storage arrangements (such as older file system versions or database formats) and prevents faulty operations by avoiding recovery with incompatible configurations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The recovery process is made dynamic by selecting different recovery strategies based on compatibility assessment. When incompatibility is detected, the system dynamically adjusts the recovery approach - either performing a partial recovery of only compatible components, upgrading the storage arrangement to match the current program version, or combining full recovery with subsequent patch application to ensure compatibility.

Inventive Principle:

Principle #15Dynamics

2Reliability

If update patches are applied after program recovery, then program functionality is improved, but downtime is prolonged

Engineering Contradiction:

Improveprogram functionalityVSAvoidprogram downtime

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs a preliminary assessment of whether update patches are needed after recovery by comparing the recovered program version with the current required version. This allows the system to avoid unnecessary patch application and reduce downtime. When patches are required, the system prepares the recovery process to minimize interruption time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Instead of always applying full update patches after recovery, the system uses partial action by selectively applying only the necessary patches based on the compatibility check results. If the storage arrangement is incompatible, the system may perform a partial recovery of only the program components that are compatible, avoiding the need for extensive patching and reducing overall downtime.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS12481566B2Program recovery

Publication Date: 2025.11.25 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

In some examples, a system receives a request to recover a program. The system accesses metadata associated with a recovery copy of information for the program, and determines, based on the metadata, a compatibility of a storage arrangement of data in the recovery copy with the program. The system determines whether to fully recover the program using the recovery copy or to partially recover the program based on the determined compatibility.