Metafile Replication via Differential Block Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file replication systems face inefficiencies when replicating metafiles between source and destination file systems, especially when they run different versions, as they struggle to handle format differences and require transferring entire blocks rather than just changed records.

Innovation Solution

The method involves subdividing metafiles into blocks, identifying and transferring only changed blocks, and using snapshotting to replicate metafiles incrementally by sending only the changes since the last update, allowing for efficient replication by filtering out unchanged blocks and using techniques like B+ trees to locate changed records.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If entire blocks are transferred during metafile replication, then data integrity is maintained, but replication efficiency deteriorates due to transferring unchanged blocks

Engineering Contradiction:
Improvedata integrityVSAvoidreplication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the metafile into discrete blocks and further segments blocks into records, enabling selective transfer of only changed portions rather than entire blocks. This segmentation allows the system to maintain data integrity for changed records while improving replication efficiency by excluding unchanged blocks from transfer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and identifies only the changed blocks and records between source and destination metafiles using differential techniques. By taking out only the necessary changed portions and transferring those selectively, the system achieves both data integrity for critical changes and improved replication efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If metafiles are replicated verbatim between different file system versions, then format compatibility is maintained, but adaptability deteriorates due to inability to handle format differences

Engineering Contradiction:
Improveformat compatibilityVSAvoidhandling format differences
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies different processing qualities to different parts of the metafile based on their format characteristics. By analyzing the structure of each block and record, the system can selectively apply format conversion only where needed while preserving the original format where applicable, thus maintaining compatibility while enabling adaptability to different file system versions.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent introduces a format translation layer that acts as an intermediary between source and destination file systems with different versions. This intermediary component translates and converts metafile formats during replication, allowing compatible data transfer between heterogeneous systems without requiring verbatim copying.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If only changed blocks are transferred, then replication efficiency improves, but complexity increases due to identification and filtering processes

Engineering Contradiction:
Improvereplication efficiencyVSAvoididentification and filtering processes
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by pre-indexing and pre-processing the metafile structure before replication. By establishing block and record boundaries in advance and preparing differential data structures, the system reduces the complexity of identification processes during actual replication, making the efficient selective transfer more manageable.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the destination system provides information about its expected metafile format and structure. This feedback allows the source system to adjust its differential identification and filtering processes accordingly, optimizing the balance between replication efficiency and processing complexity based on actual destination requirements.

Inventive Principle:
Principle #23Feedback

4Productivity

If snapshotting is used for incremental replication, then replication efficiency improves by sending only changes, but loss of information increases due to potential data loss during replication

Engineering Contradiction:
Improveincremental replication efficiencyVSAvoiddata loss during replication
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent applies beforehand cushioning by maintaining complete backup copies of both source and destination metafiles during the replication process. These backup cushions allow the system to roll back or recover information if data loss occurs during incremental replication, thus enabling efficient incremental transfers while protecting against information loss through pre-prepared recovery mechanisms.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS10242025B2Efficient differential techniques for metafiles
Publication Date: 2019.03.26 NETAPP INC
  • US10242025B2 patent drawing
  • US10242025B2 patent drawing
  • US10242025B2 patent drawing

AI summary

Exemplary embodiments provide methods, mediums, and systems for replicating metafiles between a source and a destination. The metafile may be subdivided into blocks. The contents of the metafile may be transferred by locating the blocks which are changed between the source version of the metafile and the destination version of the metafile. The changed blocks may be examined to retrieve the contents of the changed blocks. The records in the changed blocks may be evaluated to determine whether to create a corresponding record at the destination, delete a corresponding record at the destination, or update a corresponding record at the destination. Accordingly, the metafile may be replicated in a logical manner, by transferring only changed records rather than the entirety of a changed block. Moreover, the transfer is conducted efficiently because unchanged blocks are eliminated from consideration at the outset.