File Server Data Management via Access Frequency Classification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing cloud storage systems face issues with access speed and inefficient utilization of storage capacity, as files are stored locally until specific conditions are met, leading to storage capacity constraints and suboptimal use of remote servers.

Innovation Solution

A system is implemented where frequently networked data is automatically stored locally, reducing network communication and optimizing the use of both on-premises and cloud systems by determining storage based on data attributes and client terminal access patterns, with the file server managing data storage and transmission to an archive server via a network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If files are stored in the local file server until specific conditions are satisfied, then access speed is maintained, but storage capacity in the local file server is depleted and remote file server utilization is inefficient

Engineering Contradiction:
Improveaccess speedVSAvoidstorage capacity
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The system performs preliminary classification of files based on access frequency attributes before storage decisions are made. Files are pre-categorized as frequent or infrequent access files, allowing the system to proactively allocate them to appropriate storage locations (local or remote) before storage capacity becomes critical, thus maintaining access speed while optimizing storage utilization

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The storage system is segmented into two distinct layers: local file server for frequent access files and remote file server for infrequent access files. This segmentation allows each layer to be optimized independently - local storage provides high-speed access for active files while remote storage provides abundant capacity for archival files, resolving the contradiction between access speed and storage capacity

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If files are migrated to remote file server, then storage capacity in local file server is preserved, but access speed decreases due to network communication

Engineering Contradiction:
Improvestorage capacityVSAvoidaccess speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

Different quality of service is provided based on file characteristics: frequent access files are maintained in local storage with high-speed access properties, while infrequent access files are stored in remote storage with adequate capacity properties. This local quality differentiation ensures that files requiring fast access remain locally available while less critical files can be remotely stored without impacting overall system performance

Inventive Principle:
Principle #3Local quality

3Quantity of substance

If cloud system is used for storage, then storage capacity is increased, but access speed becomes lower due to network dependency

Engineering Contradiction:
Improvestorage capacityVSAvoidaccess speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The system dynamically determines file storage location based on access frequency attributes and usage patterns. Files are not statically assigned to cloud storage but are dynamically evaluated and placed in either local or remote storage based on current and predicted access needs, allowing the system to adaptively balance between storage capacity utilization and access speed requirements

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10970250B2System, data management method, and file server
Publication Date: 2021.04.06 HITACHI VANTARA LTD
  • US10970250B2 patent drawing
  • US10970250B2 patent drawing
  • US10970250B2 patent drawing

AI summary

A system, comprising: a file server coupled to a plurality of client terminals; and an archive server coupled to the file server via a network. The file server is configured to: provide an area for storing data recognizable by each of the plurality of client terminals; determine whether to store first data into the first storage device based on an attribute of a first storage area in a case where an addition request for storing the first data into the first storage area is received from a client terminal; and transmit the addition request to the archive server. The archive server is configured to store the first data into the second storage device in a case where the addition request is received.