Predictive Restore Package Preparation for Data Failure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional backup and restore technologies are inefficient in restoring computing systems due to the significant time required to develop and apply restore packages, which temporarily impairs business operations during system failures.

Innovation Solution

Implementing a system that monitors computing systems for potential data failures, predicts the scope of the failure, and prepares restore packages proactively before a user request, allowing for immediate restoration upon detection of a failure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional backup and restore technologies are used to restore computing systems, then the system can be restored to a previous computing state, but a significant amount of time is required to develop the restore package and perform the restoration, temporarily impairing business operations

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

Solution Approach 1:

The system performs preliminary actions by proactively monitoring computing systems for evidence of potential data failures and preparing restore packages before actual failures occur. When evidence of potential failure is detected, the system predictively prepares the restore package in advance, so that when a restore request is subsequently received, the package is already ready for immediate deployment, eliminating the time-consuming package creation step

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring computing systems for evidence of potential data failures and using this information to trigger predictive restore package preparation. The monitoring feedback loop enables the system to detect early signs of failure and initiate restore package creation proactively, rather than waiting for complete system failure

Inventive Principle:
Principle #23Feedback

2Productivity

If restore packages are prepared in advance predictively, then restoration time is reduced and business operations can continue, but the system requires continuous monitoring and analysis of computing system data to detect potential failures

Engineering Contradiction:
Improvebusiness operation continuityVSAvoidmonitoring and prediction system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system applies self-service by enabling computing systems to monitor themselves for potential failures and automatically triggering restore package preparation without requiring external intervention. The monitoring system continuously self-assesses the health of computing systems and autonomously initiates predictive restore operations when evidence of potential failure is detected

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs partial action by monitoring for specific evidence of potential data failures rather than continuously analyzing all system data. The monitoring focuses on key indicators that suggest impending failure, preparing restore packages only when relevant evidence is detected, rather than maintaining constant readiness for all possible failure modes

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9465710B1Systems and methods for predictively preparing restore packages
Publication Date: 2016.10.11 COHESITY INC
  • US9465710B1 patent drawing
  • US9465710B1 patent drawing
  • US9465710B1 patent drawing

AI summary

A computer-implemented method for predictively preparing restore packages may include (1) monitoring a computing system for evidence of potential data failures within the computing system, (2) detecting evidence that indicates a potential data failure within the computing system while monitoring the computing system, (3) predicting a scope of the potential data failure based at least in part on the evidence that indicates the potential data failure, and then (4) preparing a restore package configured to restore at least a portion of data implicated by the predicted scope of the potential data failure prior to detecting a request to initiate a restore operation in connection with the potential data failure. Various other methods, systems, and computer-readable media are also disclosed.