File Metadata and Version Indexing Across Storage Sources

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing and identifying unstructured data across various storage environments, such as NAS, SAN, on-premise storage, and cloud storage, is difficult due to the diverse file types and attributes, making it challenging to locate and manage unstructured data effectively.

Innovation Solution

A scalable and cost-optimized file metadata service that catalogs metadata using a file index and version index, allowing for horizontal scaling and partitioning based on demand, with live partitions stored in performant storage and older partitions archived in cheaper storage, enabling efficient file management and retrieval across diverse data sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a centralized metadata management system is used to catalog all files across multiple storage sources, then file location and management efficiency is improved, but system complexity and scalability requirements increase

Engineering Contradiction:
Improvefile location efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The metadata management system is divided into multiple independent metadata stores, each responsible for specific storage sources (e.g., NAS metadata store, SAN metadata store, cloud storage metadata store). This segmentation allows the system to manage diverse storage environments without creating a single complex centralized system, while still enabling efficient file location across all sources through coordinated queries between the metadata stores.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If metadata from multiple storage sources is aggregated in a single database, then unified file management is achieved, but storage costs and performance degrade due to data volume

Engineering Contradiction:
Improveunified file managementVSAvoiddata volume
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

Instead of aggregating all metadata in a single database, the system creates separate metadata stores for different storage sources. Each metadata store maintains only the metadata relevant to its specific storage source, reducing the data volume in each individual store while still providing unified management capability through the coordinated architecture of multiple stores.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces a coordination layer that mediates between the multiple metadata stores and client applications. This intermediary layer handles the complexity of querying and coordinating metadata across different storage sources, providing unified file management functionality without requiring client applications to directly manage the complexity of multiple data volumes.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If all file metadata is stored in high-performance storage, then access speed is maximized, but storage costs increase significantly

Engineering Contradiction:
Improvemetadata access speedVSAvoidstorage cost
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

Different metadata stores can be configured with different storage performance characteristics appropriate to their specific functions. For example, frequently accessed metadata from critical storage sources can be stored in high-performance storage, while less frequently accessed metadata from other sources can be stored in cost-effective storage options. This local quality approach optimizes both access speed and storage cost by matching storage performance to actual usage patterns.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12437005B2File metadata service
Publication Date: 2025.10.07 NETAPP INC
  • US12437005B2 patent drawing
  • US12437005B2 patent drawing
  • US12437005B2 patent drawing

AI summary

Techniques are provided for a maintaining and utilizing a file index and a file version index. Metadata may be evaluated to identify constant attributes and modifiable attributes of files. A file index of a file catalog may be populated with the constant attributes. A file version index of the file catalog may be populated with the modifiable attributes as file versions of the files. In response to receiving a request for a file, the file index and the file version index are evaluated to identify a location of the file within a data source. Access to the file at the location within the data source is provided.