Intelligent File System Restoration Using Checksum Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for restoring file system data on a host often result in redundant data copying from backup storage to the host, wasting time, storage space, network bandwidth, and computing resources.

Innovation Solution

A method that uses a data protection agent to identify restoration events, obtain backup metadata and current file system metadata, and perform intelligent restoration by identifying matching and non-matching files and portions, thereby minimizing redundant data copying.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional restoration methods are used to restore file system data from backup storage, then data protection and recovery are achieved, but redundant data copying occurs which wastes time, storage space, network bandwidth, and computing resources

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

Solution Approach 1:

The system performs preliminary actions by generating and storing checksums for all files during the backup process. When restoration is needed, these pre-computed checksums are immediately available for comparison with current file checksums, enabling rapid identification of matching files without redundant copying. This preliminary preparation resolves the contradiction by maintaining data protection while dramatically reducing restoration time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system extracts only the essential verification information (checksums) from the backup data and stores it separately in metadata. During restoration, these extracted checksums are used to identify which files actually need to be restored, allowing the system to skip copying files that are already present and unchanged. This extraction approach maintains reliability while eliminating redundant data copying and reducing restoration time.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If traditional restoration methods are used to restore file system data from backup storage, then data protection and recovery are achieved, but redundant data copying occurs which wastes time, storage space, network bandwidth, and computing resources

Engineering Contradiction:
Improvedata protectionVSAvoidrestoration efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by generating and storing checksums for all files during the backup process. When restoration is needed, these pre-computed checksums are immediately available for comparison with current file checksums, enabling rapid identification of matching files without redundant copying. This preliminary preparation resolves the contradiction by maintaining data protection while dramatically reducing restoration time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system extracts only the essential verification information (checksums) from the backup data and stores it separately in metadata. During restoration, these extracted checksums are used to identify which files actually need to be restored, allowing the system to skip copying files that are already present and unchanged. This extraction approach maintains reliability while eliminating redundant data copying and reducing restoration time.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If traditional restoration methods are used to restore file system data from backup storage, then complete data recovery is achieved, but excessive storage space and network bandwidth are consumed due to redundant data copying

Engineering Contradiction:
Improvedata recoveryVSAvoidstorage space and network bandwidth
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The system extracts only the essential verification information (checksums) from the backup data and stores it separately in metadata. During restoration, these extracted checksums are used to identify which files actually need to be restored, allowing the system to skip copying files that are already present and unchanged. This extraction approach maintains reliability while eliminating redundant data copying and reducing restoration time.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies local quality by treating each file individually during restoration - comparing its checksum against the current file system to determine whether it needs to be copied. This localized verification approach ensures that only specific files requiring restoration are transferred, rather than copying entire data sets. This maintains complete data recovery capability while minimizing storage space and network bandwidth consumption.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12204419B1Intelligent restoration of file systems using destination aware restorations
Publication Date: 2025.01.21 DELL PROD LP
  • US12204419B1 patent drawing
  • US12204419B1 patent drawing
  • US12204419B1 patent drawing

AI summary

Techniques described herein relate to a method for performing restorations of file system data on a host. The method may include identifying a restoration event associated with a file system of a host; obtaining backup metadata associated with a backup of the file system and obtaining current file system metadata associated with the file system; identifying non-matching files and matching files using the backup metadata and the current file system metadata; storing local copies of the matching files on the host; identifying, based on the current file system metadata and the backup metadata, matching portions, non-matching portions, and completely unique files; storing local copies of the matching portions of the non-matching files on the host to restore the matching portions of the non-matching files; and restoring the completely unique files of the non-matching files and the non-matching portions of the non-matching files from a backup storage.