Cache File Validation via Segmentation and Checksums

Solution Overview

Problem

Conventional data backup systems face significant performance and efficiency issues when cache files become corrupted, leading to full data backups that are ten times longer and severely impact user experience due to increased network traffic and server workload.

Innovation Solution

A method and device for validating cache files by segmenting a reference cache file into multiple segments, generating and storing reference check information, and using this information to validate the cache file, allowing identification of corrupted segments and utilizing uncorrupted segments to reduce the need for full data backups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the cache file is used to reduce network traffic and server workload, then backup efficiency is improved, but if the cache file is corrupted, the entire backup process must be restarted causing severe performance degradation

Engineering Contradiction:

Improvebackup efficiencyVSAvoidcache file reliability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The cache file is divided into multiple segments, each with its own checksum. This allows the system to identify and work with only the uncorrupted segments rather than the entire cache file, resolving the contradiction by maintaining reliability through error detection while preserving productivity by utilizing valid segments.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system changes the parameter of cache file validation from an all-or-nothing approach to a segment-level approach. By computing and verifying checksums for individual segments, the system can dynamically determine which portions of the cache file are valid, thus maintaining both reliability and productivity.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If the cache file is validated segment by segment, then the impact of corruption is localized, but the complexity of the validation process increases

Engineering Contradiction:

Improvecache file validation accuracyVSAvoidvalidation process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The cache file is divided into multiple segments, each with its own checksum. This allows the system to identify and work with only the uncorrupted segments rather than the entire cache file, resolving the contradiction by maintaining reliability through error detection while preserving productivity by utilizing valid segments.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system changes the parameter of cache file validation from an all-or-nothing approach to a segment-level approach. By computing and verifying checksums for individual segments, the system can dynamically determine which portions of the cache file are valid, thus maintaining both reliability and productivity.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If a full data backup is performed when cache file corruption is detected, then data integrity is ensured, but the backup time increases ten times

Engineering Contradiction:

Improvedata integrityVSAvoidbackup time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The cache file is divided into multiple segments, each with its own checksum. This allows the system to identify and work with only the uncorrupted segments rather than the entire cache file, resolving the contradiction by maintaining reliability through error detection while preserving productivity by utilizing valid segments.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of performing a complete full backup when any corruption is detected, the system performs a partial backup only for the corrupted segments. This principle allows the system to maintain data integrity for the entire file while minimizing the time loss by only re-backing up the necessary portions.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS10776271B2Method, device and computer program product for validating cache file

Publication Date: 2020.09.15 EMC IP HLDG CO LLC

AI summary

Embodiments of the present disclosure provide a method, device and computer program product for validating a cache file. In an embodiment, a reference cache file associated with the backed up data is divided into a plurality of reference segments. Reference check information is generated for the respective reference segments of the plurality of reference segments, and the generated reference check information is stored. In response to the initiating of a backup job, the stored reference check information is used to validate the cache file.