Snapshot-Based Data Format Conversion via Patch File Simulation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management systems face inefficiencies when transferring data between different file formats, particularly during archival processes, as they often require local conversion of data formats, which consumes significant input/output resources and increases the overall transfer time.

Innovation Solution

A data management system that simulates the conversion of data into a different format without actually reading or writing the data blocks, generating a patch file image with simulation information to facilitate the transfer in the new format, reducing the need for explicit format conversion and minimizing I/O operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data format conversion is performed locally during file transfer, then data can be transferred between different formats, but input/output resources are consumed significantly and transfer time increases

Engineering Contradiction:
Improvedata format compatibilityVSAvoiddata transfer efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by creating snapshots of the source file system state before transfer begins. These snapshots capture the data in its original format without requiring conversion during the actual transfer process, thereby preparing everything in advance to avoid I/O consumption during transfer.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention creates a copy of the source file system state through snapshots that can be transferred independently. Instead of converting data formats during transfer, the system copies the original data with format information preserved, allowing the destination to handle format adaptation without impacting transfer performance.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If explicit data format conversion is performed during transfer, then data can be transferred between different formats, but the overall transfer time increases

Engineering Contradiction:
Improveformat conversion capabilityVSAvoidtransfer time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by creating snapshots of the source file system state before transfer begins. These snapshots capture the data in its original format without requiring conversion during the actual transfer process, thereby preparing everything in advance to avoid time loss during transfer.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The snapshot mechanism acts as an intermediary that decouples the source and destination file systems. The snapshot captures the source state and transfers it to the destination without requiring real-time format conversion, thereby eliminating the time penalty associated with explicit conversion operations during the critical transfer window.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If data is read and written during format conversion, then conversion accuracy is maintained, but I/O operations increase significantly

Engineering Contradiction:
Improveconversion accuracyVSAvoidI/O operation volume
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The system creates accurate copies of the source file system state through snapshots without requiring read/write operations during transfer. The snapshot mechanism preserves data integrity and format information through copying rather than conversion, thereby maintaining precision while dramatically reducing I/O operation volume.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The invention extracts the format conversion requirement from the transfer process itself. By capturing the source state in a snapshot with all format information preserved, the system removes the need for read/write operations that would otherwise be required for conversion, thereby separating accuracy preservation from I/O consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20240086361A1Online data format conversion
Publication Date: 2024.03.14 RUBRIK INC
  • US20240086361A1 patent drawing
  • US20240086361A1 patent drawing
  • US20240086361A1 patent drawing

AI summary

In some examples, a data management system generates snapshots in a distributed file system based on a protocol or a user triggered event, The data management system identifies a snappable file in a distributed file system and a first data block in the snappable file, the first data block including data and attribute data. The system scans an index file to access the attribute data of the first data block and initiates construction of a patch file based on the accessed attribute data. The system repeats the scanning of the index file to access attribute data of at least a further second data block, the second data block including data and attribute data, and completes construction of the patch file based on the accessed attribute data of the first and second data blocks. The system generates conversion simulation information by collecting attribute data for all the data blocks of the constructed patch file, and writes the simulation information to a patch file image.