Replicated Test Metadata File for Data Integrity Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In information processing systems, data integrity tests face inaccuracies due to test metadata files not being fully reflected in point-in-time (PIT) replicas, leading to potential inconsistencies in data integrity test results.

Innovation Solution

Incorporating the test metadata file into a replication consistency group as part of the replication process ensures consistency between the test metadata file and the PIT replica, thereby providing more accurate data integrity test results by storing the test metadata file within the logical storage volumes for which the PIT replica is generated.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the test metadata file is generated separately from the replication process, then the data integrity test can be performed, but inconsistencies arise between the test metadata file and the PIT replica

Engineering Contradiction:
Improvedata integrity test accuracyVSAvoidconsistency between test metadata file and PIT replica
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent merges the test metadata file generation process with the PIT replica generation process by incorporating the test metadata file into the replication consistency group. This ensures that both the test metadata file and the PIT replica are generated from the same source data simultaneously, eliminating inconsistencies between them while maintaining reliable data integrity testing.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If the test metadata file is incorporated into the replication consistency group, then consistency between the test metadata file and PIT replica is ensured, but the complexity of the replication process increases

Engineering Contradiction:
Improveconsistency between test metadata file and PIT replicaVSAvoidreplication process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies multi-functionality by using the existing replication consistency group mechanism for dual purposes: both for generating production PIT replicas and for generating test metadata files. This approach ensures consistency between the two while avoiding the need to create a separate, dedicated system for test metadata generation, thereby limiting the increase in complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If the test metadata file is stored in the logical storage volumes, then consistency is maintained with the PIT replica, but additional storage space is required

Engineering Contradiction:
Improveconsistency between test metadata file and PIT replicaVSAvoidstorage space for test metadata file
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts the test metadata file from being a separate external file and incorporates it as part of the logical storage volume structure within the replication consistency group. This integration ensures that the test metadata file is automatically included in PIT replica generation while utilizing existing storage infrastructure, thereby managing storage space requirements efficiently.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10592159B2Processing device configured for data integrity testing utilizing replicated test metadata file
Publication Date: 2020.03.17 EMC IP HLDG CO LLC
  • US10592159B2 patent drawing
  • US10592159B2 patent drawing
  • US10592159B2 patent drawing

AI summary

An apparatus in one embodiment comprises at least one processing device comprising a processor coupled to a memory. The processing device is configured to schedule generation of a point-in-time replica of one or more logical storage volumes of a storage system, to generate a test metadata file for a data integrity test to be performed utilizing the point-in-time replica, and to store the test metadata file in at least one of the one or more logical storage volumes for which the point-in-time replica is to be generated. The point-in-time replica may comprise a snapshot of a replication consistency group comprising the one or more logical storage volumes of the storage system. Scheduling the generation of the point-in-time replica of the one or more logical storage volumes of the storage system illustratively comprises initiating an asynchronous replication process for a replication consistency group comprising the one or more logical storage volumes of the storage system.