Sequential Data Volume Replication via Write Session Identifier Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data replication methods often require copying the entire data set when only a portion of the original data set is modified, leading to inefficiencies as they cannot determine which specific portions differ between the original and copied data sets.

Innovation Solution

A data replication system that uses write session identifiers to compare and identify mismatches between corresponding data blocks in the original and copied sequential data volumes, replicating only the specific data blocks and subsequent blocks with mismatched identifiers, thereby updating the copied volume efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire data set is copied to ensure completeness, then data reliability is improved, but data transfer time and bandwidth consumption increase

Engineering Contradiction:
Improvedata completenessVSAvoiddata transfer time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The data set is divided into individual data blocks, each with its own write session identifier. Instead of copying the entire data set, the system identifies and copies only the specific data blocks that have changed, based on comparing their write session identifiers between the original and copied volumes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses write session identifiers as feedback signals to determine which data blocks have been modified. By comparing the write session identifiers of corresponding data blocks in the original and copied volumes, the system identifies changes and targets only those blocks for replication, avoiding unnecessary copying of unchanged data.

Inventive Principle:
Principle #23Feedback

2Reliability

If the entire data set is copied to ensure completeness, then data reliability is improved, but bandwidth consumption increases

Engineering Contradiction:
Improvedata completenessVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The data set is segmented into discrete data blocks with associated write session identifiers. This segmentation enables the system to copy only the modified blocks rather than the entire data set, significantly reducing bandwidth consumption while maintaining data completeness for changed portions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts only the necessary data blocks for replication by identifying them through write session identifier comparison. This extraction approach removes unnecessary data transfer by copying only the minimal set of blocks that contain actual changes, optimizing bandwidth utilization.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If write session identifiers are compared to identify changes, then data transfer efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvereplication efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system creates a simplified copy of the data block metadata (write session identifiers) to enable comparison without copying the actual data. This allows the system to identify changes efficiently by comparing only the identifiers, reducing the complexity of change detection while maintaining high replication efficiency.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10963483B2Sequential storage volume replication based on comparison of write session identifiers
Publication Date: 2021.03.30 ORACLE INT CORP
  • US10963483B2 patent drawing
  • US10963483B2 patent drawing
  • US10963483B2 patent drawing

AI summary

Described herein are systems and methods for replicating an original sequential data volume to a copied sequential data volume. The two sequential data volumes comprise corresponding data blocks with associated write session identifiers. The write session identifiers may correspond to an applicable write operation. When the original sequential data volume is modified, the copied sequential data volume may also be modified for consistency. The write session identifiers of the two data volumes may be sequentially compared to find a mismatch at a modified data block. The data blocks of the copied sequential data volume are replaced, beginning with the modified data block. Instead of replicating the entire original sequential data volume, the modified data block and any subsequent data blocks are replicated in the copied sequential data volume.