Block-Level Data Replication for Linux and UNIX Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data replication methods, such as volume-level snapshots, are not suitable for operating systems like UNIX and Linux, and can be slow and data-traffic intensive, leading to increased processing burden and network traffic, especially when only specific files need to be replicated or restored.

Innovation Solution

Implementing a data block-level replication mechanism that uses a cryptography algorithm to generate representative data blocks, which are smaller in size and can be compared and sent between servers, reducing data traffic and enabling efficient replication across various operating systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If volume-level snapshots are used for data replication, then data backup and recovery can be achieved, but the replication process becomes slow and data-traffic intensive

Engineering Contradiction:
Improvedata backup and recoveryVSAvoidreplication speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the volume-level snapshot into block-level granularity, allowing only modified blocks to be replicated rather than the entire volume. This segmentation enables selective replication of changed data only, significantly reducing data traffic and improving replication speed while maintaining backup reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and identifies only the modified data blocks between two snapshots using file system metadata and change tracking mechanisms. By taking out only the necessary changed blocks for replication rather than the entire volume, the system reduces network bandwidth consumption and processing requirements while preserving recovery capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If volume-level snapshots are used, then data replication can be performed, but processing burden and network traffic increase significantly

Engineering Contradiction:
Improvedata replicationVSAvoidprocessing burden and network traffic
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system segments data replication at the block level rather than volume level, enabling processing and network transmission to focus only on modified blocks. This reduces the processing burden on replication servers and decreases network traffic by excluding unchanged data from replication operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements partial replication by transferring only the necessary modified blocks rather than the complete volume. This partial action approach reduces energy consumption and network bandwidth usage while maintaining sufficient data for recovery purposes.

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If file-by-file or directory-by-directory comparison is performed, then specific modified files can be identified, but the replication process becomes very slow

Engineering Contradiction:
Improveidentification of modified filesVSAvoidreplication speed
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent segments the file system into blocks and maintains metadata about block changes between snapshots. This allows efficient identification of modified blocks without performing slow file-by-file comparisons, as the metadata already tracks which blocks have changed, enabling rapid replication of only those blocks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary tracking of block changes between snapshots by maintaining file system metadata that records modifications. This preliminary action enables rapid identification of modified blocks during replication without requiring slow real-time file-by-file comparison, thus improving replication speed while maintaining precision.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8924354B2Block level data replication
Publication Date: 2014.12.30 CA TECH INC
  • US8924354B2 patent drawing
  • US8924354B2 patent drawing
  • US8924354B2 patent drawing

AI summary

Systems and methods for replicating data from a production server to a backup server include identifying one or more data blocks of a file that were modified after a first time instant and before a second time instant. The file may be associated with a protected directory of the production server. An representative data block (e.g., including a hash value) for at least one of the identified data blocks may be computed using a cryptography algorithm, e.g., MD5 or SHA-1. The computed cryptographic data block representing the identified data block may then be sent for replication to the backup server. An operation performed between the first time instant and the second time instant on one or more files of the protected directory may be recorded, and sent to the backup server.