Policy-Based Data Management for Distributed Storage Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current distributed storage systems face resource saturation, lack of operation prioritization, inability to store data across multiple platforms, and inefficient storage options that do not account for varying file requirements, leading to suboptimal performance and unnecessary costs.

Innovation Solution

A policy-based data management system that allows clients operating on different platforms to prioritize files and store them in storage pools based on attributes and policies, using metadata servers to assign service classes and storage pools dynamically, ensuring optimal resource allocation and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If distributed storage systems store more data simultaneously, then storage capacity increases, but resource saturation occurs leading to performance degradation

Engineering Contradiction:
Improvestorage capacityVSAvoidoperation performance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The system segments storage resources into multiple storage pools with different performance characteristics (high-performance, standard-performance, low-performance). By dividing the storage system into heterogeneous pools rather than treating all storage as uniform, the system can allocate appropriate resources to different operations, preventing resource saturation from degrading overall performance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different storage pools are assigned different quality levels based on their performance characteristics. High-performance storage pools handle critical operations requiring fast access, while lower-performance pools handle less time-sensitive operations. This local differentiation of quality allows the system to maintain high productivity for important operations while maximizing total storage capacity utilization.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If storage systems handle multiple operations simultaneously, then operational versatility increases, but resource contention occurs causing performance degradation

Engineering Contradiction:
Improveoperational versatilityVSAvoidoperation performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system dynamically allocates storage resources based on operational priorities and current system state. Metadata servers can adjust which storage pools serve which operations in real-time, allowing the system to adapt resource distribution as operational patterns change. This dynamic allocation prevents resource contention from permanently degrading performance of critical operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Metadata servers act as intermediaries between clients and storage pools, intelligently routing operations to appropriate storage resources. This intermediary layer prevents direct resource contention by coordinating access and selecting optimal storage pools based on operation characteristics, thereby maintaining high productivity across multiple simultaneous operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If storage systems allocate resources to high-resource operations, then operational capacity increases, but critical operations experience delays

Engineering Contradiction:
Improveoperational capacityVSAvoidoperation delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary classification of operations and data into service classes based on priority and resource requirements. By pre-categorizing operations before execution, the system can proactively allocate appropriate storage pools and resources, ensuring that critical operations are reserved sufficient capacity in advance and cannot be delayed by high-resource operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the parameter of resource allocation by introducing service class distinctions that modify how resources are distributed. Different service classes receive different levels of resource allocation and priority treatment, transforming the uniform resource allocation model into a differentiated one that protects critical operations from delays while still allowing high-resource operations to execute.

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If distributed storage systems support multiple platforms, then system adaptability increases, but complexity of data management increases

Engineering Contradiction:
Improveplatform compatibilityVSAvoiddata management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The metadata server implements a universal interface that handles multiple platform protocols and data formats through a single centralized management point. This universal layer translates between different platform-specific requirements and the underlying storage system, allowing multi-platform support without proportionally increasing management complexity across the entire distributed system.

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

Data Source

PatentUS8671132B2System, method, and apparatus for policy-based data management
Publication Date: 2014.03.11 DAEDALUS BLUE LLC
  • US8671132B2 patent drawing
  • US8671132B2 patent drawing
  • US8671132B2 patent drawing

AI summary

A policy-based data management system, method, and apparatus are disclosed. The system, method, and apparatus are configured to operate over a distributed storage system such as a storage area network (SAN). Files to be stored on the network are each assigned a service class and a storage pool based on the application of policies to file attributes such as file name, type, user, etc. The service class and storage pool designations are stored as metadata. Files may be retrieved using the metadata to identify the storage pool where the file is stored, and the service class listed within the metadata may be used to control the manner in which the file is handled. A metadata server may be utilized to provide the appropriate service class of files in response to requests from remote clients that may be of different computing platforms.