Pool Spare Allocation in Storage Virtualization Subsystems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data storage virtualization subsystems lack flexibility in spare physical storage device (PSD) allocation, as spare PSDs can only be defined to support either a specific logical media unit (LMU) or the entire system, limiting their effectiveness in providing backup capabilities.

Innovation Solution

The implementation of a data storage virtualization subsystem that designates PSDs as pool spares, allowing for the creation of PSD pools with pool IDs, enabling flexible allocation of spare PSDs within these pools to support user data and redundant information, and utilizing a spare table to manage the allocation of pool spares and non-pool spares.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If spare PSDs are designated to support specific LMUs or the entire system, then backup capability is provided, but flexibility in spare PSD allocation is limited

Engineering Contradiction:
Improvebackup capabilityVSAvoidflexibility in spare PSD allocation
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The invention segments the system into multiple PSD pools, each with its own pool ID. Spare PSDs can be designated to support specific pools rather than being locked to individual LMUs, creating a hierarchical structure that provides both targeted backup and flexible reallocation across pools.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Spare PSDs are designed with multi-functionality, able to support multiple LMUs within a designated pool. A single spare PSD can serve as backup for any LMU in its assigned pool, making the spare resource universal within that pool's context rather than dedicated to a single LMU.

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

2Quantity of substance

If more PSDs are provided in the SVS, then storage capacity increases, but the possibility of encountering failed PSDs increases

Engineering Contradiction:
Improvestorage capacityVSAvoidfailure risk
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system performs preliminary actions by designating spare PSDs in advance and organizing them into pools. When a PSD failure occurs, the pre-configured pool spare mechanism enables immediate data rebuilding without requiring system-wide analysis or manual intervention to identify appropriate spare resources.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

PSD pools act as intermediaries between individual LMUs and spare PSDs. The pool structure mediates the relationship, allowing spare PSDs to be efficiently allocated to failed members based on pool membership rather than direct LMU-to-spare mapping, simplifying the failure recovery process.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If local spare PSDs are provided for specific LMUs, then dedicated backup is achieved, but spare PSD utilization efficiency decreases

Engineering Contradiction:
Improvededicated backupVSAvoidspare PSD utilization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The invention merges the concepts of local and global spares by creating pool-based spare designation. Multiple LMUs within a pool share common spare resources, combining the benefits of dedicated backup (within the pool context) with the efficiency of shared resources across multiple LMUs.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9110607B2Pool spares for data storage virtualization subsystem
Publication Date: 2015.08.18 INFORTREND TECH INC
  • US9110607B2 patent drawing
  • US9110607B2 patent drawing
  • US9110607B2 patent drawing

AI summary

A data storage virtualization subsystem (SVS) for providing storage to a host entity is disclosed. The SVS comprises a storage virtualization controller for connecting to the host entity, at least one physical storage device (PSD) pool, and at least one PSD is designated to be a pool spare PSD to the at least one PSD pool. The at least one PSD pool comprises at least one PSD to store user data or associated redundant information and is given a pool ID for identifying the PSD pool.