Tiered Storage Policy Engine for SSD HDD Data Placement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage systems for network-attached storage (NAS) servers lack the ability to optimally allocate data across different types of persistent storage, such as SSD and HDD, leading to suboptimal performance and cost ratios due to limitations in data placement granularity and policy flexibility.

Innovation Solution

A system that allows for the mixing of SSD and HDD in the same file system, with policy mechanisms to control the placement of files at a fine granularity, enabling storage of data portions in the most suitable type of storage based on access patterns, thereby improving performance and cost efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data is stored in SSD for fast access, then read performance is improved, but cost increases

Engineering Contradiction:
Improveread performanceVSAvoidcost
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent segments files into multiple parts and stores different parts in different storage media. Specifically, it divides files into segments that can be stored in SSD, HDD, or cloud storage based on access frequency and importance, allowing the system to optimize between performance and cost by placing only critical data in expensive SSD while keeping less critical data in cheaper storage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different storage qualities to different parts of the same file based on their access patterns. Frequently accessed or critical portions of files are stored in high-performance SSD, while less frequently accessed portions are stored in cheaper HDD or cloud storage, thereby optimizing overall system performance without unnecessarily increasing cost for all data.

Inventive Principle:
Principle #3Local quality

2Quantity of substance

If data is stored in HDD for low cost, then cost is reduced, but write performance deteriorates

Engineering Contradiction:
ImprovecostVSAvoidwrite performance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The system segments write operations and file data to utilize appropriate storage media. Critical and frequently accessed data is written to SSD for high performance, while less critical data is written to HDD or cloud storage, allowing the system to maintain good write performance for important data while keeping overall storage costs low.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different write performance characteristics to different parts of the file system. Important directories and files receive high-performance SSD storage with fast write capabilities, while other data is stored in cheaper HDD or cloud storage with acceptable but slower write performance, thereby optimizing the balance between cost and productivity.

Inventive Principle:
Principle #3Local quality

3Speed

If entire volumes are migrated to SSD, then read performance is improved, but cost increases significantly

Engineering Contradiction:
Improveread performanceVSAvoidcost
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

Instead of migrating entire volumes to SSD, the patent segments volumes into smaller units that can be individually evaluated and placed in appropriate storage media based on access patterns. This allows only the necessary portions of data to be stored in expensive SSD, rather than the entire volume, thereby reducing cost while maintaining performance benefits for critical data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different storage qualities to different portions of the volume based on local access patterns rather than treating the entire volume uniformly. This allows high-performance SSD storage to be applied only to locally hot data while cooler data remains in cheaper storage, optimizing the balance between read performance and cost.

Inventive Principle:
Principle #3Local quality

4Productivity

If fine-grained data placement is implemented, then storage optimization is improved, but system complexity increases

Engineering Contradiction:
Improvestorage optimizationVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary storage management layer that handles the complexity of fine-grained data placement automatically. This intermediary layer includes components like the storage manager, policy engine, and data movement services that transparently manage data segmentation, placement, and migration between different storage media based on policies, thereby enabling storage optimization without requiring complex manual intervention.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service capabilities where the storage management infrastructure automatically monitors access patterns, evaluates data importance, and performs data placement and migration decisions without manual intervention. The policy-based automation and self-managing features reduce operational complexity while maintaining fine-grained storage optimization.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9342528B2Method and apparatus for tiered storage
Publication Date: 2016.05.17 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9342528B2 patent drawing
  • US9342528B2 patent drawing
  • US9342528B2 patent drawing

AI summary

A system for storing file data and directory data received over a network includes a network interface in communication with the network which receives NAS requests containing data to be written to files from the network. The system includes a first type of storage. The system includes a second type of storage different from the first type of storage. The system includes a policy specification n which specifies a first portion of one or more files' data which is less than all of the files' data is stored in the first type of storage and a second portion of the data which is less than all of the data of the files is stored in the second type of store. The system comprises a processing unit which executes the policy and causes the first portion to be stored in the first type of storage and a second portion to be stored in the second type of storage. A method for storing file data and directory data received over a network.