Asynchronous Replication Manifest Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Asynchronous replication in server and network storage systems faces challenges in ensuring data consistency and integrity, particularly in cases where the primary site fails before data is written to the secondary site, leading to potential data loss due to the lag in updating the remote storage.

Innovation Solution

The system performs Asynchronous Replication Correctness Validation by generating a manifest of client data, taking snapshots, and synchronizing datasets, using event-driven mechanisms and distributed metadata stores to ensure data accuracy and efficiency in backup and replication processes, and employs Locally Distributed Change Detection to minimize network bandwidth usage and optimize data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If asynchronous replication is used to increase performance, then write speed is improved, but data integrity is worsened due to potential data loss at remote storage

Engineering Contradiction:
Improvewrite speedVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system generates a manifest file that describes the dataset before replication occurs. This manifest serves as a preliminary record of data state, enabling validation of replication correctness without blocking the write operation, thus maintaining performance while enabling integrity verification

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the manifest is transferred to remote storage and used to validate that replicated data matches the source. This feedback loop allows the system to detect and correct replication errors while maintaining asynchronous performance characteristics

Inventive Principle:
Principle #23Feedback

2Reliability

If complete validation of replicated data is performed, then data integrity is improved, but system complexity is worsened due to additional validation steps

Engineering Contradiction:
Improvedata integrityVSAvoidvalidation process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of validating every byte of replicated data, the system creates a simplified copy of the data state in the form of a manifest file. This manifest contains essential metadata and checksums that can be validated much more efficiently than complete data verification, reducing complexity while maintaining integrity assurance

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system extracts only the critical validation information from the complete dataset and places it in the manifest file. This extraction approach allows validation to focus on essential integrity checks rather than processing the entire dataset, simplifying the validation process

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If manifest validation is performed to ensure data correctness, then data loss is reduced, but network bandwidth usage is worsened due to manifest transfer

Engineering Contradiction:
Improvedata correctnessVSAvoidnetwork bandwidth
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system extracts only the essential validation information from the complete dataset and places it in the manifest file. This extraction approach allows validation to focus on essential integrity checks rather than processing the entire dataset, simplifying the validation process

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The manifest file format is optimized to contain only the minimum necessary information for validation (metadata, checksums, file listings) rather than complete data copies. This parameter optimization significantly reduces the network bandwidth required for manifest transfer while maintaining validation effectiveness

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9448893B1Asynchronous replication correctness validation
Publication Date: 2016.09.20 ARCSERVE LLC
  • US9448893B1 patent drawing
  • US9448893B1 patent drawing
  • US9448893B1 patent drawing

AI summary

A method for backing up a client data set on a computer by generating a manifest of the client data set and storing the manifest on a remote server along with a server data set corresponding to the client data set; taking a snapshot of the server manifest and data set; and comparing the manifest to the remote server data set and synchronizing the client dataset if a difference is detected.