Multi-site File Replication Using Inode Bit Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current file replication technologies face challenges in efficiently managing multi-site replication across different protocols and backends, particularly in maintaining data accuracy and completeness across multiple remote sites, and in supporting both push and pull mechanisms for data replication.

Innovation Solution

A method for multi-site replication that captures IO operations at a gateway device, enqueues them onto queues associated with target sites, and independently manages replication using inode bits to track replication states, enabling seamless data replication across multiple cloud providers and POSIX compliant systems, with features like metering and invoicing for usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multi-site replication is implemented across different protocols and backends, then data redundancy and reliability are improved, but system complexity increases

Engineering Contradiction:
Improvedata redundancyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments replication management into independent per-site queues and per-site inode bit tracking, allowing each target site to be managed independently through its own queue and replication state bits, thereby reducing overall system complexity while maintaining multi-site redundancy

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The gateway device acts as an intermediary that captures IO operations and routes them to appropriate target sites through enrolled queues, managing the complexity of multi-protocol multi-backend replication centrally at the gateway while keeping individual site implementations simpler

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If replication state tracking is implemented for each target site, then data accuracy is improved, but computational overhead increases

Engineering Contradiction:
Improvedata accuracyVSAvoidcomputational overhead
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system divides replication state tracking into separate inode bits for each target site, allowing precise tracking of replication status for each site independently without requiring complex global state management, thus achieving accurate tracking with minimal computational overhead

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses inode bits as compact state parameters to track replication status, changing the representation of replication state from complex data structures to simple binary bit flags, thereby reducing computational overhead while maintaining precise tracking capability

Inventive Principle:
Principle #35Parameter changes

3Reliability

If multiple queues are maintained for different target sites, then replication completeness is improved, but memory usage increases

Engineering Contradiction:
Improvereplication completenessVSAvoidmemory usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system maintains separate queues for each target site to ensure complete replication tracking, with each queue containing only the subset of IO operations relevant to its target site, thereby reducing memory usage compared to maintaining all operations in every queue while preserving replication completeness

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11954073B2Multi-protocol multi-site replication
Publication Date: 2024.04.09 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11954073B2 patent drawing
  • US11954073B2 patent drawing
  • US11954073B2 patent drawing

AI summary

Disclosed are techniques for multi-protocol multi-site file replication, including a method comprising capturing, at a gateway device, IO operations performed on a filesystem, the filesystem having inode bits. The method may further comprise enqueuing the captured IO operations onto a plurality of queues, wherein each of the plurality of queues is associated with one of a plurality of target sites; and independently managing replication of the IO operations to the target sites using the inode bits.