Partial File System Instances for Bandwidth Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data replication methods in object-based data virtualization platforms are inefficient in terms of time, cost, and network bandwidth, as they often require replicating entire file system instances, which is unnecessary when only a subset of data is needed for processing or analysis.

Innovation Solution

Replicating a subset of objects from a source file system instance to form a partial file system instance on a target system, with unmaterialized objects being dynamically added as needed, and asynchronously updating the target system based on comparisons with the source system, reducing the need for full replication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If entire file system instances are replicated, then data completeness is ensured, but network bandwidth utilization increases and replication time extends

Engineering Contradiction:
Improvedata completenessVSAvoidnetwork bandwidth utilization
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and replicates only the necessary subset of objects from the source file system instance based on selection criteria (such as object types, size ranges, or specific identifiers) rather than replicating the entire file system. This extraction approach ensures that only relevant data is transmitted over the network, reducing bandwidth utilization while maintaining data completeness for the required subset.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the file system instance into individual objects that can be independently evaluated and selected for replication. By dividing the file system into discrete objects with unique identifiers, the system can apply selection criteria to specific segments (objects) rather than treating the entire file system as a single unit, enabling partial replication that conserves network bandwidth.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire file system instances are replicated, then data completeness is ensured, but replication time increases

Engineering Contradiction:
Improvedata completenessVSAvoidreplication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the necessary objects for replication based on predefined selection criteria, eliminating the need to copy unnecessary data. This extraction process significantly reduces the total volume of data that needs to be transmitted and processed, thereby reducing replication time while ensuring that all required objects are captured.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary identification and selection of objects that meet the replication criteria before initiating the actual replication process. By pre-filtering objects based on their identifiers, types, or other attributes, the system prepares a reduced set of objects for replication, avoiding the time waste of copying unnecessary data during the replication execution phase.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If entire file system instances are replicated, then data availability is improved, but storage utilization increases

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage utilization
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts and replicates only the essential objects from the source file system instance based on selection criteria, rather than copying the entire file system. This approach ensures that data availability is maintained for the required subset of objects while minimizing the storage space consumed at both the source and target systems.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by replicating only the necessary portion of the file system objects rather than the complete set. This partial replication strategy provides sufficient data availability for processing and analysis operations while avoiding the excessive storage utilization that would result from full file system replication.

Inventive Principle:
Principle #16Partial or excessive action

4Loss of energy

If selective object replication is implemented, then network bandwidth utilization is reduced, but system complexity increases

Engineering Contradiction:
Improvenetwork bandwidth utilizationVSAvoidsystem complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where objects contain unique identifiers that enable automatic identification and selection during the replication process. The selection criteria are applied automatically based on these identifiers, eliminating the need for complex manual selection processes or sophisticated decision-making algorithms, thus reducing system complexity while maintaining selective replication benefits.

Inventive Principle:
Principle #25Self-service

5Loss of time

If selective object replication is implemented, then replication time is reduced, but processing overhead increases

Engineering Contradiction:
Improvereplication timeVSAvoidprocessing overhead
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The patent uses self-service identification where each object carries a unique identifier that automatically enables its selection or exclusion based on predefined criteria. This approach minimizes processing overhead by avoiding complex evaluation logic during replication, as the unique identifiers facilitate quick matching and selection decisions, thereby reducing both processing time and computational energy consumption.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12093316B2Partial file system instances
Publication Date: 2024.09.17 HEWLETT PACKARD ENTERPRISE DEV LP
  • US12093316B2 patent drawing
  • US12093316B2 patent drawing
  • US12093316B2 patent drawing

AI summary

Example implementations relate to partial file system instances. In an example, a subset of objects of a source file system instance on a source system are replicated to a target system to form a partial file system instance on the target system comprised of the subset of objects. Each of the objects of the source file system instance is identified by a signature based on content of each of the objects and the objects exhibit a hierarchical relationship to a root object in the file system instance. An unmaterialized object is dynamically added to the partial file system instance by replicating the corresponding object from the source file system instance. The target system is asynchronously updated from the source file system instance based on a comparison of the partial file system instance to the source file system instance.