Pull Data Replication via Snapshot Inversion and Protocol Bridging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data replication between different storage systems is complicated by the need for one system to act as an initiator, which requires additional intelligence and processing power, and is further hindered by the use of different protocols between vendors, making automated or semi-automated batch replication difficult or impossible.

Innovation Solution

A remote batch data replication service using asynchronous replication through snapshots, where the local data storage system operates as a target, allowing data to be pulled from the source system, and a heterogeneous communication protocol enables data replication between systems from different vendors by using a common protocol to advertise and discover replication capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If the source data storage system acts as an initiator to move data to the recipient system, then data replication can be performed, but the source system requires additional intelligence and processing power making it more complex

Engineering Contradiction:
Improvedata replication capabilityVSAvoidsource system complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

Instead of having the source system act as an initiator to push data to the recipient, the patent inverts the approach by having the recipient system act as the initiator that pulls data from the source. The recipient system sends commands to the source system to create snapshots and transfer data, thereby eliminating the need for the source system to have initiator functions and reducing its complexity.

Inventive Principle:
Principle #13The other way round (Inversion)

2Adaptability or versatility

If different vendors use different protocols to control their data storage systems, then each vendor can optimize their system, but automated or semi-automated batch replication between different vendors becomes difficult or impossible

Engineering Contradiction:
Improvevendor-specific optimizationVSAvoidcross-vendor replication automation
Core Design Contradiction:
Adaptability or versatilityVSExtent of automation

Solution Approach 1:

The patent introduces a common protocol that acts as an intermediary between different vendor-specific protocols. The recipient system uses this common protocol to communicate with the source system, enabling automated batch replication between heterogeneous systems. The common protocol translates and coordinates commands between systems that originally speak different vendor-specific languages.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Extent of automation

If the source data storage system is enhanced to include initiator functions and remote replication functions, then data replication can be performed, but the system complexity and processing requirements increase

Engineering Contradiction:
Improveremote replication capabilityVSAvoidprocessing power requirement
Core Design Contradiction:
Extent of automationVSPower

Solution Approach 1:

The patent eliminates the need for the source system to have initiator functions by inverting the replication architecture. The recipient system assumes the initiator role and sends commands to the source system to create snapshots and transfer data. This approach reduces the processing power requirements of the source system while maintaining automated replication capability.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS8990153B2Pull data replication model
Publication Date: 2015.03.24 SEAGATE CLOUD SYSTEMS INC
  • US8990153B2 patent drawing
  • US8990153B2 patent drawing
  • US8990153B2 patent drawing

AI summary

A data storage system, device, and method are provided for replicating data between different data storage systems or appliances. More specifically, the present invention affords communications between heterogeneous data storage systems that potential employ different communication protocols. A bridging communication protocol is utilized by one or both storage systems in order to accommodate different communication protocols. Alternatively, a storage appliance connecting the data storage systems may employ the bridging communication protocol.