Health-Based Backup Creation for Computing Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data backup methods create snapshots or backups regardless of a computing system's health, leading to potential performance or stability issues upon restoration and excessive storage usage due to unwieldy backup data.

Innovation Solution

A method that evaluates a computing system's health based on performance and stability metrics, determines if the current state is healthier than prior states, and creates a backup or snapshot only when the system is in a healthy state, storing health information as metadata, and manages backups by deleting less relevant snapshots to maintain storage quotas.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional backup software creates snapshots or backups regardless of system health state, then backup availability is improved, but restoration reliability deteriorates due to potential performance or stability issues

Engineering Contradiction:
Improverestoration reliabilityVSAvoidbackup creation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system continuously monitors system health through performance metrics (CPU usage, memory usage, disk usage) and stability metrics (system errors, application errors, service errors) to determine whether to create backups. This feedback mechanism ensures that backups are only created when the system is in a healthy state, improving restoration reliability while maintaining efficient backup operations.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs health evaluations before creating backups to ensure the system is in an appropriate state. By conducting preliminary health checks and only initiating backup creation when health metrics indicate a healthy system state, the system prevents creation of potentially problematic backups while maintaining overall backup availability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If conventional backup software creates snapshots continuously, then backup coverage is improved, but storage space consumption increases to unwieldy levels

Engineering Contradiction:
Improvebackup coverageVSAvoidstorage space consumption
Core Design Contradiction:
ReliabilityVSVolume of stationary object

Solution Approach 1:

Instead of creating backups continuously regardless of system state, the system applies partial action by creating backups only when health metrics indicate the system is in a healthy state. This selective backup approach maintains adequate backup coverage for restoration needs while significantly reducing storage space consumption by avoiding redundant backups of unhealthy system states.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system changes the parameter of backup creation frequency based on system health status. By dynamically adjusting whether to create backups based on real-time health metric thresholds, the system optimizes the balance between backup coverage and storage space consumption, preventing unwieldy storage growth while maintaining necessary backup availability.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the system monitors and evaluates health metrics continuously, then backup quality is improved, but system resource consumption increases

Engineering Contradiction:
Improvebackup qualityVSAvoidsystem resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies partial monitoring by evaluating health metrics only at appropriate intervals and only when necessary to determine backup creation eligibility. This selective monitoring approach ensures high backup quality through comprehensive health assessment when needed, while reducing system resource consumption by avoiding continuous intensive monitoring operations.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8949187B1Systems and methods for creating and managing backups based on health information
Publication Date: 2015.02.03 CA TECH INC
  • US8949187B1 patent drawing
  • US8949187B1 patent drawing
  • US8949187B1 patent drawing

AI summary

A computer-implemented method may include performing an evaluation of the computing system's health. The computer-implemented method may also include comparing results of the evaluation with the results of at least one prior evaluation of the computing system's health and then determining, based on the comparison, that a current state of health of the computing system is healthier than at least one prior state of health of the computing system. In addition, the computer-implemented method may include creating a backup of the computing system. A computer-implemented method for managing backups of a computing system based on health information is also disclosed. Corresponding systems and computer-readable media are also disclosed.