Data Storage Manager Policy-Based Placement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage management systems face challenges in efficiently managing data storage across multiple storage mechanisms with varying characteristics, such as communication latency, throughput, and availability, which can impact data retrieval times and access patterns for software programs.

Innovation Solution

A data storage manager system that employs defined data storage management policies to strategically store and retrieve data across local and remote storage mechanisms, including non-volatile devices, distributed file systems, and online storage services, optimizing data placement based on access patterns, priority, and storage characteristics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is stored on remote storage mechanisms, then storage capacity is increased, but data retrieval time increases due to communication latency

Engineering Contradiction:
Improvestorage capacityVSAvoiddata retrieval time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The system performs preliminary actions by preloading frequently accessed data from remote storage to local storage mechanisms before they are actually needed. This anticipatory approach reduces the communication latency experienced during actual data retrieval operations, as the data is already available locally when needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements local quality by creating different storage environments for different data types. Frequently accessed data is stored locally with fast access characteristics, while less frequently accessed data remains in remote storage. This differential approach optimizes retrieval time for critical data while maintaining overall storage capacity.

Inventive Principle:
Principle #3Local quality

2Loss of time

If data is preloaded locally, then data retrieval time is reduced, but local storage capacity is consumed

Engineering Contradiction:
Improvedata retrieval timeVSAvoidlocal storage capacity
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The system applies partial action by selectively preloading only the most frequently accessed data to local storage, rather than loading all data. This selective approach ensures that local storage capacity is utilized efficiently for high-priority data while maintaining adequate space for other operations.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system dynamically changes parameters such as preload thresholds, storage capacity allocations, and data priority classifications based on observed access patterns. This allows the system to adapt to changing data usage requirements and optimize the balance between local storage usage and retrieval performance.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If multiple storage mechanisms are used, then storage flexibility is improved, but system complexity increases

Engineering Contradiction:
Improvestorage flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements a unified storage management interface that provides universal access to multiple storage mechanisms. This abstraction layer allows different storage types (local, remote, cloud) to be managed through a single system, providing storage flexibility while hiding the underlying complexity from application programs.

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

Solution Approach 2:

The system introduces an intermediary storage management layer that mediates between application programs and multiple storage mechanisms. This intermediary handles the complexity of coordinating data placement, retrieval, and migration across different storage types, while presenting a simplified interface to applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9984079B1Managing data storage using storage policy specifications
Publication Date: 2018.05.29 AMAZON TECH INC
  • US9984079B1 patent drawing
  • US9984079B1 patent drawing
  • US9984079B1 patent drawing

AI summary

Techniques are described for managing data storage using defined data storage management policies. In some situations, data storage may be managed using multiple supported storage mechanisms, such as different storage mechanisms of different types and/or in different locations. As one example, the described techniques may be performed to manage data that is available to a software program executing on a computer system, such as by caching a subset of the available data on one or more storage mechanisms to enhance later retrieval times of that data subset by the software program. In this example, the multiple supported storage mechanisms may include one or more storage mechanisms local to the computer system and one or more storage mechanisms remote from the computer system, and a defined data storage management policy for the software program may define particular types of data to store on particular storage mechanisms in particular manners.