Incremental Backup Bridge Device Using Record File Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional storage systems face performance degradation due to the time-consuming process of scanning all files during incremental backups, especially when dealing with large numbers of files, leading to overall system inefficiency.

Innovation Solution

A method and bridge device that manage incremental backups by determining the existence of a record file, comparing file attributes, and preventing unnecessary backups based on comparison results, thereby reducing the number of comparison operations and enhancing backup speed without introducing side effects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the conventional storage system scans all files in the target device to compare with files in the source device, then the backup completeness is ensured, but the backup speed and system performance are degraded

Engineering Contradiction:
Improvebackup completenessVSAvoidbackup speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by creating and maintaining a record file that stores file information (such as file names, sizes, or checksums) before the actual backup process. During incremental backup, the system compares only the current file list against this pre-existing record file to determine which files have changed, rather than scanning and comparing all files in the target device. This preliminary preparation enables fast identification of changed files while ensuring backup completeness.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the conventional storage system scans all files during incremental backup, then all changed files are detected, but the time consumption increases significantly

Engineering Contradiction:
Improvefile change detection accuracyVSAvoidbackup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system extracts only the necessary file identification information (such as file names, sizes, or checksums) from the source device and stores it in a record file. During incremental backup, only this extracted information is compared against the current state, rather than scanning and comparing all file contents in the target device. This extraction approach ensures accurate detection of changed files while dramatically reducing the time required for comparison operations.

Inventive Principle:
Principle #2Taking out (Extraction)

3Measurement precision

If the storage system compares all files to ensure accurate change detection, then the backup accuracy is maintained, but the computational resources are excessively consumed

Engineering Contradiction:
Improvefile change detection precisionVSAvoidcomputational resource consumption
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs partial comparison by only comparing the essential file identification information stored in the record file against the current file list, rather than performing exhaustive comparison of all files. This partial action approach maintains sufficient precision for detecting changed files (by comparing key attributes like names, sizes, or checksums) while avoiding the excessive computational resources that would be required for complete file content comparison.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11243844B2Method for enhancing speed of incremental backup, bridge device, and storage system
Publication Date: 2022.02.08 JMICRON
  • US11243844B2 patent drawing
  • US11243844B2 patent drawing
  • US11243844B2 patent drawing

AI summary

A method for enhancing speed of incremental backup, a bridge device, and a storage system are provided. The method includes: regarding a predetermined location within the storage system, determining whether a record file exists; in response to the record file existing, determining whether any file needing to be compared exists; in response to said any file needing to be compared existing, comparing said any file needing to be compared with content of the record file to generate at least one comparison result, wherein said at least one comparison result indicates whether a set of attributes of said any file needing to be compared completely exist in the record file; according to said at least one comparison result, determining whether any difference is found; and in response to said any difference being not found, preventing triggering any backup from a source storage device to a target storage device.