Object File System for Hybrid Storage Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Hybrid storage systems combining primary storage and cloud computing face compatibility issues, leading to loss of robust functionality provided by primary storage systems when integrated with cloud computing environments, resulting in cost inefficiencies and scalability limitations.

Innovation Solution

An object file system is implemented within an object store that enables efficient storage and management of snapshots, allowing for cost-effective long-term storage of infrequently accessed data, while maintaining data integrity and compatibility through a snapshot file system tree structure and metadata normalization, using cloud block numbers for deduplication and compression, and a mapping metafile for data sharing and garbage collection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If hybrid storage systems combine primary storage and cloud computing, then cost savings and scalability are achieved, but robust functionality provided by primary storage systems is lost

Engineering Contradiction:
Improvestorage costVSAvoidfunctionality compatibility
Core Design Contradiction:
Loss of energyVSAdaptability or versatility

Solution Approach 1:

The patent introduces an object file system as an intermediary layer between primary storage systems and cloud computing environments. This intermediary translates and adapts data structures, metadata formats, and access protocols, enabling seamless integration while preserving the robust functionality of primary storage systems and the cost-effectiveness of cloud storage. The object file system acts as a mediator that reconciles the incompatibilities between these two storage paradigms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If primary storage systems provide robust functionality, then data management features are improved, but storage cost increases

Engineering Contradiction:
Improvedata management functionalityVSAvoidstorage cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the storage system into distinct functional layers: the object file system layer that provides robust data management functionality, and the underlying storage layer (which can be cloud-based) that provides cost-effective storage. By segmenting the system this way, the expensive robust functionality is isolated to the software layer, while the storage layer can use cost-effective cloud infrastructure.

Inventive Principle:
Principle #1Segmentation

3Quantity of substance

If cloud computing storage is used for scalability, then storage capacity is improved, but compatibility with primary storage features is lost

Engineering Contradiction:
Improvestorage capacityVSAvoidprimary storage feature compatibility
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The object file system is designed as a universal interface that can work with multiple types of underlying storage systems (cloud storage, local storage, hybrid configurations). It provides multi-functionality by supporting various primary storage features (snapshots, deduplication, compression, encryption) while adapting to different storage backends, thus maintaining feature compatibility across diverse storage environments.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12174789B2Sibling object generation for storing results of operations performed upon base objects
Publication Date: 2024.12.24 NETAPP INC
  • US12174789B2 patent drawing
  • US12174789B2 patent drawing
  • US12174789B2 patent drawing

AI summary

Techniques are provided for on-demand creation and/or utilization of containers and/or serverless threads for hosting data connector components. The data connector components can be used to perform integrity checking, anomaly detection, and file system metadata analysis associated with objects stored within an object store. The data connector components may be configured to execute machine learning functionality to perform operations and tasks. The data connector components can perform full scans or incremental scans. The data connector components may be stateless, and thus may be offlined, upgraded, onlined, and/or have tasks transferred between data connector components. Results of operations performed by the data connector components upon base objects may be stored within sibling objects.