Event-Driven Backup System for Real-Time Data Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional backup systems face issues with data recovery during system failures, as they typically back up data at fixed intervals, leading to time gaps where changes are not captured, and incremental backups require additional resources and time for data restore, resulting in performance delays.

Innovation Solution

A real-time backup system comprising a service client, metadata server, backup client, operational storage, and backup storage, where data changes are immediately updated and backed up, allowing for real-time metadata synchronization and efficient data restoration without performance delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If traditional fixed interval backup is used, then storage and network consumption are reduced, but data recovery completeness deteriorates due to time gaps between backups

Engineering Contradiction:
Improvestorage consumptionVSAvoiddata recovery completeness
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The backup system transitions from static fixed-interval backup to dynamic event-driven backup. The backup client dynamically responds to data change events by initiating incremental backups only when changes occur, rather than following a predetermined schedule. This dynamic approach ensures complete data recovery capability while optimizing storage usage by backing up only changed data.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements self-service backup triggering through event monitoring. The backup client autonomously detects data changes through file system event notifications and automatically initiates backup operations without external intervention. This self-service mechanism ensures no data loss while minimizing unnecessary backup operations that would consume storage resources.

Inventive Principle:
Principle #25Self-service

2Loss of energy

If incremental backup with change detection is used, then storage consumption is reduced, but computing resources increase due to additional comparisons and calculations

Engineering Contradiction:
Improvestorage consumptionVSAvoidcomputing resources
Core Design Contradiction:
Loss of energyVSUse of energy by moving object

Solution Approach 1:

The system introduces an event notification mechanism as an intermediary between data modification and backup operations. File system events act as mediators that automatically detect and report data changes to the backup client, eliminating the need for complex comparison and calculation algorithms. This intermediary approach reduces computing resource consumption while enabling efficient incremental backup identification.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If metadata is restored first for faster restore, then restore speed is improved, but storage access performance deteriorates due to asynchronous data transfer time

Engineering Contradiction:
Improverestore speedVSAvoidstorage access performance recovery time
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The system performs preliminary actions during the backup phase by organizing and pre-positioning backup data in an optimized structure. Metadata and corresponding data blocks are prepared and staged in advance during incremental backup operations, so that during restore operations, both metadata and data can be retrieved simultaneously without asynchronous delays, achieving fast restore while maintaining storage access performance.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9720779B2Backup system and backup method thereof
Publication Date: 2017.08.01 INSTITUTE FOR INFORMATION INDUSTRY
  • US9720779B2 patent drawing
  • US9720779B2 patent drawing
  • US9720779B2 patent drawing

AI summary

A backup system and a backup method thereof are provided. The backup system includes an operational storage, a backup storage, a service client, a metadata server and a backup client. The service client accesses the operational storage according to an operational storage layout metadata and makes a data change to the operational storage to transmit a metadata update request. The metadata server receives the metadata update request from the service client, updates a local operational storage layout metadata in response to the data change according to the metadata update request, acknowledges the metadata update request and instructs the backup client to back up the data change of the operational storage to the backup storage according to the metadata update request.