Data Connector for Object-Store Snapshot Access in Hybrid Backup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Primary storage systems provide robust data storage and management features but are costly and less scalable compared to cloud computing storage, and their functionality is not compatible with cloud computing environments, leading to loss of essential features when hybrid solutions are used.

Innovation Solution

An object file system is employed to store and manage data in a structured format within an object store, enabling snapshot representation, version neutrality, and deduplication, with a data connector component providing on-demand access and browsing capabilities for backup data, preserving storage efficiency and reducing costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If primary storage systems are used to provide robust data storage and management features, then data management functionality is improved, but storage cost increases and scalability decreases

Engineering Contradiction:
Improvedata management functionalityVSAvoidscalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments storage functionality into two parts: primary storage systems provide robust data management features (deduplication, encryption, snapshot management), while cloud computing environments provide scalable storage capacity. The data mover component bridges these segments, enabling hybrid operation that combines the advantages of both approaches.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal data management architecture that works across both primary storage systems and cloud computing environments. The object file system and data connector component provide multi-functional capabilities that enable the same system to operate effectively in hybrid cloud-primary storage configurations, maintaining robust functionality while achieving scalability.

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

2Reliability

If primary storage systems are used to provide robust data storage features, then data management capability is improved, but storage cost increases

Engineering Contradiction:
Improvedata storage capabilityVSAvoidstorage cost
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system applies local quality by placing different types of data in different storage locations based on their requirements. Frequently accessed data and data requiring robust management features are kept in primary storage systems, while archival data and data requiring large capacity are stored in cloud computing environments. The data connector component enables on-demand access to data in cloud storage, providing robust functionality only where needed.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If hybrid storage solutions are used to achieve cost savings and scalability, then storage efficiency is improved, but robust functionality is lost due to incompatibility

Engineering Contradiction:
Improvestorage efficiencyVSAvoidfunctionality compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The data connector component serves as an intermediary between cloud computing storage and primary storage systems. It translates data requests from various protocols (NFS, SMB, iSCSI, FC) into operations that can be executed on cloud-stored objects, enabling hybrid storage solutions to maintain robust functionality despite the incompatibility between different storage environments.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12608283B2Data connector component for implementing data requests
Publication Date: 2026.04.21 NETAPP INC
  • US12608283B2 patent drawing
  • US12608283B2 patent drawing
  • US12608283B2 patent drawing

AI summary

Techniques are provided for implementing data requests associated with objects of an object store. A data connector component may be instantiated as a container for processing data requests associated with backup data stored within objects of an object store. The data connector component may evaluate the object store to identify snapshots stored as the backup data within the objects of the object store according to an object format. The data connector component may provide a client device with access to backup data of the snapshots.