Backup Validation Tool Journal Replay Data Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backup applications often fail to accurately backup data due to corrupt algorithms, unsupported file systems, incorrect configurations, or faulty patches, leading to potential data loss and costly restoration issues.

Innovation Solution

A validation tool is introduced to validate backup applications by replaying journal logs and comparing source and target data, identifying discrepancies and generating alerts to ensure accurate backups through a modular framework with a rule engine, data I/O generation engine, journal interpreter, journal replay engine, and comparison module.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a backup application is used to backup data, then data can be restored in case of data loss, but the backup application may be corrupt, unsupported, or misconfigured leading to incorrect backups

Engineering Contradiction:
Improvebackup accuracyVSAvoidvalidation framework complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The validation framework performs preliminary validation of the backup application before actual backups are executed. It generates test data, replays journal logs, and compares source and target data to detect issues in advance, preventing incorrect backups from occurring in the first place.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The validation framework acts as an intermediary between the backup application and the backup target. It inserts a journal interpreter and comparison module into the backup process to independently verify that data is being backed up correctly without interfering with the normal backup operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If validation tests are performed on backup applications, then backup accuracy can be ensured, but additional time and resources are required for validation processes

Engineering Contradiction:
Improvebackup verificationVSAvoidvalidation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The validation framework performs partial validation by focusing on critical aspects of the backup process. It generates a subset of test data and replays only the necessary journal log entries to verify backup accuracy, rather than validating every single data element, thus reducing validation time while maintaining reliability.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The validation framework performs validation in advance before actual backups are needed. By detecting and reporting issues with the backup application beforehand, it prevents time loss during actual backup operations or restoration scenarios, making the time investment worthwhile.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If journal logs are replayed and data comparison is performed, then data integrity can be verified, but the validation process becomes more complex

Engineering Contradiction:
Improvedata integrity verificationVSAvoidvalidation process complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The validation framework segments the validation process into distinct modular components: a data I/O generation engine that creates test data, a journal interpreter that reads and parses journal logs, and a comparison module that compares source and target data. This segmentation makes the complex validation process more manageable and maintainable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The validation framework creates a copy of the journal log and replays it through the journal interpreter to generate expected output data. This copied and replayed data is then compared with actual backup data to verify integrity, allowing verification without directly modifying the original backup process.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9804957B1Block tracking data validation backup model
Publication Date: 2017.10.31 EMC IP HLDG CO LLC
  • US9804957B1 patent drawing
  • US9804957B1 patent drawing
  • US9804957B1 patent drawing

AI summary

A user's selection of a validation test for a backup application is received. First test data responsive to the validation test is generated on a source disk. The backup application is allowed to record in a journal an event corresponding to the generation of the first test data. The journal is replayed on a destination disk to generate second test data according to the recorded event. The second test data is compared against the first test data to determine whether the backup application passed or failed the validation test.