Backup Copy Validation Workflow Using Checksum Comparison

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current backup and recovery processes are inefficient, leading to lengthy backup windows, high resource consumption, and the risk of data corruption, particularly due to the inability of backup proxies to perform incremental backups and validate data integrity in real-time.

Innovation Solution

The implementation of a system that embeds a bitmap into snapshots to track changes, allowing backup proxies to conduct differential backups and validate data integrity by comparing checksums, thereby reducing backup times and ensuring data accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If backup proxies conduct full backups, then data integrity is ensured, but backup window times increase and resource consumption increases

Engineering Contradiction:

Improvedata integrityVSAvoidbackup window time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by embedding bitmaps into snapshots during the backup process, which track changed blocks. This allows the backup proxy to later conduct differential backups by comparing bitmaps, significantly reducing backup window times while maintaining data integrity through checksum validation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by validating backup data integrity through checksum comparisons during the backup process. This real-time validation provides feedback on data accuracy, allowing the system to ensure integrity without requiring lengthy post-backup verification processes.

Inventive Principle:

Principle #23Feedback

2Loss of time

If incremental backups are used, then backup window times are reduced, but data corruption errors may go undetected until restoration

Engineering Contradiction:

Improvebackup window timeVSAvoiddata corruption detection

Core Design Contradiction:

Loss of timeVSReliability

Solution Approach 1:

The system implements continuous feedback through real-time checksum validation during incremental backup operations. By comparing checksums of source and destination data blocks, the system immediately detects data corruption errors, providing feedback that allows for prompt error correction before restoration is attempted.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary validation actions by computing and comparing checksums during the backup process itself, rather than waiting until restoration time. This preliminary detection of data integrity issues allows for immediate corrective action, preventing corrupted data from being restored.

Inventive Principle:

Principle #10Preliminary action

3Productivity

If backup proxies are used, then production server load is reduced, but the ability to perform incremental backups is lost

Engineering Contradiction:

Improveproduction server availabilityVSAvoidbackup process complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary mechanism by embedding bitmaps into snapshots that are transferred to the backup proxy. This intermediary structure enables the proxy to perform differential backups without needing direct access to production I/O paths, maintaining production server availability while restoring incremental backup capability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-processing data during the initial backup to embed bitmaps into snapshots. This preliminary structuring of backup data allows the backup proxy to efficiently conduct subsequent differential backups by comparing bitmaps, reducing the complexity of the backup process while maintaining productivity benefits.

Inventive Principle:

Principle #10Preliminary action

4Reliability

If comprehensive data validation is performed, then data integrity is ensured, but computing resources and time are consumed

Engineering Contradiction:

Improvedata integrityVSAvoidcomputing resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies partial validation by focusing checksum comparisons on critical data blocks and using bitmap differences to identify which blocks require validation. This partial action approach ensures data integrity for the most important changes while consuming fewer computing resources compared to validating every single block.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system implements efficient feedback mechanisms by using checksum validation only where needed, based on bitmap comparisons. This targeted feedback approach ensures data integrity for changed blocks while minimizing unnecessary computing resource consumption on unchanged data.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS11880283B2Backup copy validation as a workflow

Publication Date: 2024.01.23 DELL PROD LP

AI summary

A configuration file having options for validating backups is received. A request is issued to a copy service to take a snapshot of a volume to be backed up. A determination is made from the configuration file that a backup of the volume is to be validated. A script including code for generating first checksums of data captured by the snapshot is invoked. A backup copy of the volume is created using the snapshot. The backup copy is mounted. The mounted backup copy is read and second checksums of data that has been backed up are generated. The script is allowed to compare the first and second checksums. If any of the first and second checksums do not match, the backup copy is failed.