Predictive Failure Model for Node Repair and Backup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computer systems often experience interruptions and data loss due to hardware or software failures, despite having sensors and antivirus software to detect errors, as preventive measures are typically taken after failures occur, leading to temporary disruptions.

Innovation Solution

A monitoring computing device collects node data from sensors to build failure models, predicts potential failures, and determines preventative repair or backup actions, such as migrating data or replacing hardware, to mitigate or avoid the consequences of node failures before they happen.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If sensors and antivirus software are used to detect errors, then detection capability is improved, but failures still occur and require reactive repair actions causing service interruption

Engineering Contradiction:
Improveerror detection capabilityVSAvoidservice continuity
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The system performs preliminary actions by predicting potential failures before they occur and executing preventative repair or backup actions in advance. The failure prediction model analyzes sensor data to identify nodes likely to fail, allowing the system to migrate data or replace hardware before actual failure occurs, thus maintaining service continuity while improving detection capability.

Inventive Principle:
Principle #10Preliminary action

2Ease of repair

If reactive repair actions are taken after failures occur, then repair actions can be performed, but processing power and time for recovery increase

Engineering Contradiction:
Improverepair action executionVSAvoidrecovery time
Core Design Contradiction:
Ease of repairVSLoss of time

Solution Approach 1:

Instead of reacting after failure, the system performs preliminary repair actions by predicting failures in advance and executing preventative measures. This shifts the timeline from post-failure repair to pre-failure prevention, significantly reducing recovery time and processing power requirements.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors sensor data from nodes and uses this feedback to train and update failure prediction models. The models learn from actual failure patterns and adjust their predictions, enabling more accurate and timely preventative actions that reduce recovery time and resource consumption.

Inventive Principle:
Principle #23Feedback

3Loss of information

If data backup is performed manually after failure, then data loss can be recovered, but downtime and data loss occur during the recovery process

Engineering Contradiction:
Improvedata recovery capabilityVSAvoiddowntime
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary backup actions by identifying nodes at risk of failure and proactively backing up their data before failure occurs. This continuous proactive backup approach eliminates the need for reactive post-failure backup operations, preventing data loss and minimizing downtime during recovery processes.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8140914B2Failure-model-driven repair and backup
Publication Date: 2012.03.20 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8140914B2 patent drawing
  • US8140914B2 patent drawing
  • US8140914B2 patent drawing

AI summary

A predictive failure model is used to generate a failure prediction associated with a node. A repair or backup action may also be determined to perform on the node based on the failure prediction.