Database Backup Automation via Change Thresholds

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database backup methods often result in unnecessary resource consumption and increased restore times due to manual scheduling of differential and full backups, which can lead to a long chain of backups and inefficient use of computing resources.

Innovation Solution

Implementing a smart backup system that uses SQL queries to determine when to perform differential or full backups based on the extent of changes in the database, triggering backups only when specific threshold values are met, thereby reducing unnecessary backups and automating the process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If differential backup is scheduled to occur every 24 hours manually, then backup frequency is maintained, but unnecessary backups are created when database changes are minimal

Engineering Contradiction:
Improvebackup frequencyVSAvoidcomputing storage resources
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system changes the parameter of backup triggering from fixed time intervals to dynamic thresholds based on database change metrics. It monitors database change parameters (number of changed rows, percentage of changed data) and adjusts backup execution accordingly, performing backups only when change parameters exceed predefined thresholds, thus avoiding unnecessary backups while maintaining adequate backup frequency

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring database change metrics and using this information to dynamically adjust backup decisions. The monitoring component tracks database changes and provides feedback to the backup decision logic, which then determines whether to trigger a backup based on whether the monitored changes meet the threshold criteria, creating a closed-loop control system

Inventive Principle:
Principle #23Feedback

2Reliability

If differential backup is performed when database changes are large, then data protection is maintained, but restore time increases due to large backup size

Engineering Contradiction:
Improvedata protectionVSAvoidrestore time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system applies partial action by performing differential backups only when the degree of database change falls within an optimal range. When changes are small to moderate, differential backup provides adequate protection with minimal restore time impact. When changes become excessively large, the system switches to full backup strategy, recognizing that differential backup would no longer be efficient. This selective application of backup types optimizes the balance between data protection and restore time

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If manual monitoring of database changes is implemented, then backup decisions are accurate, but operational complexity increases for database administrators

Engineering Contradiction:
Improvechange detection accuracyVSAvoidmonitoring system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system implements self-service by enabling the database backup system to automatically monitor its own state and make backup decisions without external intervention. The monitoring component continuously tracks database changes, and the decision logic automatically determines when to trigger backups based on predefined thresholds, eliminating the need for manual Database Administrator intervention while maintaining accurate change detection

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system achieves multi-functionality by integrating multiple functions into a unified automated backup management platform. The same system that performs backups also monitors database changes, evaluates change metrics, makes backup decisions, and manages backup execution. This consolidation reduces operational complexity by eliminating the need for separate manual monitoring processes while maintaining precise change detection capabilities

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Reliability

If a long chain of differential backups is created, then data protection coverage is comprehensive, but maintenance difficulty increases during restore operations

Engineering Contradiction:
Improvedata protection coverageVSAvoidrestore operation maintenance
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system applies preliminary action by establishing predetermined thresholds and decision rules before backup operations begin. These predefined criteria for when to trigger differential versus full backups are set in advance, allowing the system to automatically make optimal backup decisions without requiring post-hoc analysis or manual chain management. This preliminary configuration prevents the formation of excessively long backup chains by proactively switching to full backups when appropriate

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11604703B2Systems and methods for performing backups of a server database
Publication Date: 2023.03.14 EMC IP HLDG CO LLC
  • US11604703B2 patent drawing
  • US11604703B2 patent drawing
  • US11604703B2 patent drawing

AI summary

Systems and methods for performing differential and full data protection operations. Parameters that define minimum, interval, and maximum values are provided to an agent. These values relate to changes in the data or in a database. The agent monitors the database and backups are triggered in accordance with these values. A differential backup is not performed until the minimum value is reached and differential backups are performed only after subsequent intervals are reached. A full backup is performed once the maximum value is reached.