Metadata Packet Replication for Storage High Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data replication methods in storage area networks (SANs) incur substantial memory utilization and data transmission bandwidth overhead by replicating entire data streams, which can disrupt high availability during replicator failures.

Innovation Solution

Replicating metadata instead of data, allowing for efficient memory use and reduced bandwidth requirements, with replicators using queues to store data and metadata until it is persisted at a target site, enabling continuous data protection without compromising high availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If entire data streams are replicated across multiple replicators, then high availability is provided, but memory utilization and data transmission bandwidth overhead increase substantially

Engineering Contradiction:
Improvehigh availabilityVSAvoidmemory utilization
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential metadata from the data stream for replication, rather than replicating entire data streams. Metadata packets contain LUN identifiers and region information that identify which data blocks need to be replicated, allowing the system to replicate only necessary data portions while significantly reducing memory utilization overhead.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the data replication process into two distinct packet types: metadata packets (containing LUN and region identifiers) and data packets (containing actual data blocks). This segmentation allows replicators to handle metadata and data separately, optimizing memory usage by storing only metadata in queues while data flows through the replication pipeline.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire data streams are replicated across multiple replicators, then high availability is provided, but data transmission bandwidth overhead increases substantially

Engineering Contradiction:
Improvehigh availabilityVSAvoiddata transmission bandwidth
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and transmits only metadata packets (containing LUN and region identifiers) separately from data packets. This extraction reduces data transmission bandwidth overhead because metadata packets are significantly smaller than full data streams, while still providing the information needed for high availability replication.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

By segmenting transmission into metadata packets and data packets, the system can optimize bandwidth usage. Metadata packets are transmitted to multiple replicators to establish replication paths, while actual data transmission occurs only through the primary replicator, reducing overall bandwidth consumption compared to replicating entire data streams to all replicators.

Inventive Principle:
Principle #1Segmentation

3Quantity of substance

If metadata is replicated instead of data, then memory and bandwidth requirements are reduced, but system complexity increases

Engineering Contradiction:
Improvememory requirementsVSAvoidsystem complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent creates a universal metadata packet format that serves multiple functions: identifying data blocks, tracking replication status, enabling failover, and managing queue operations. This multi-functional metadata structure reduces overall system complexity by consolidating multiple control functions into a single standardized packet type that works across all replicators.

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

Solution Approach 2:

The metadata packet acts as an intermediary between the data stream and the replication management system. It carries essential information (LUN, region identifiers) that mediates the replication process, allowing replicators to make decisions about data replication without directly processing entire data streams, thus simplifying the control logic while maintaining reduced memory requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If replicators use queues to store data and metadata, then continuous data protection is enabled, but memory utilization increases

Engineering Contradiction:
Improvecontinuous data protectionVSAvoidmemory utilization
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments queue storage requirements by placing only metadata packets in replicator queues, while data packets flow through the replication pipeline without being queued at intermediate replicators. This segmentation dramatically reduces memory utilization in queues while maintaining continuous data protection capabilities, as the metadata queue enables failover without requiring storage of entire data streams.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10848554B2Memory efficient asynchronous high availability replication
Publication Date: 2020.11.24 ORACLE INT CORP
  • US10848554B2 patent drawing
  • US10848554B2 patent drawing
  • US10848554B2 patent drawing

AI summary

A method for data replication may include obtaining data, generating a data packet including the data and a logical unit number (LUN) corresponding to a logical unit of a storage array, generating a metadata packet including the LUN and metadata that identifies a region of the logical unit, transmitting the data packet and the metadata packet to a first replicator, transmitting the metadata packet to a second replicator, and transmitting the data packet to a target site.