Storage System Upgrade via Controller Role Transfer

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing storage systems face challenges in upgrading resources without losing valuable components, leading to inefficiencies and reduced processing power during system upgrades.

Innovation Solution

The system preserves original resources by transferring controller roles and establishing connections between new and existing system resources, allowing backend resources to remain online during upgrades, even when new resources have incompatible physical form factors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If system resources are upgraded by replacing existing components, then new resources with higher capacity can be added, but existing resources are lost and processing power is reduced

Engineering Contradiction:

Improvesystem resourcesVSAvoidprocessing power

Core Design Contradiction:

Quantity of substanceVSReliability

Solution Approach 1:

The system divides storage resources into different types (backend storage resources and frontend storage resources) with distinct roles. Backend resources provide persistent storage capacity while frontend resources provide compute and I/O functions. This segmentation allows independent replacement of backend storage without losing frontend processing capabilities, resolving the contradiction between adding storage capacity and maintaining processing power.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system introduces a storage controller as an intermediary component that manages both backend storage resources and frontend storage resources. The controller enables data migration between different storage resources and coordinates their operations, allowing the system to add new backend storage while maintaining frontend processing through the intermediary management layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Quantity of substance

If existing storage resources are replaced during upgrade, then new capacity is achieved, but system operation continuity is interrupted

Engineering Contradiction:

Improvestorage capacityVSAvoidsystem operation continuity

Core Design Contradiction:

Quantity of substanceVSDuration of action of stationary object

Solution Approach 1:

The system performs preliminary actions by first adding new backend storage resources to the pool before replacing existing ones. The storage controller pre-configures the new resources and establishes data migration paths, then gradually migrates data from old to new resources during operation, ensuring continuous system functionality throughout the upgrade process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous useful action by enabling concurrent operation of both old and new storage resources during the upgrade process. Data migration occurs in the background without interrupting read/write operations, and the storage controller dynamically routes requests to available resources, ensuring uninterrupted service while transitioning storage capacity.

Inventive Principle:

Principle #20Continuity of useful action

3Quantity of substance

If backend storage resources are replaced, then storage capacity is updated, but compute resources and I/O functions are lost

Engineering Contradiction:

Improvestorage capacityVSAvoidcompute power

Core Design Contradiction:

Quantity of substanceVSPower

Solution Approach 1:

The system segments storage functions into backend storage resources (providing capacity) and frontend storage resources (providing compute and I/O). This separation allows backend resources to be replaced for capacity upgrades while frontend resources maintain compute power and I/O functions, eliminating the trade-off between storage capacity and processing capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The storage controller serves multiple functions: managing backend storage capacity, coordinating frontend storage operations, migrating data between resources, and handling I/O requests. This multi-functionality allows the system to add backend storage capacity while the controller continues to provide compute and I/O management services through frontend resources.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If system components are upgraded with incompatible form factors, then newer technology is adopted, but physical integration becomes problematic

Engineering Contradiction:

Improvetechnology compatibilityVSAvoidphysical integration

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The storage controller acts as an intermediary that abstracts the physical differences between storage resources with incompatible form factors. It provides a unified interface for managing diverse storage devices, handling data migration between different physical formats, and coordinating operations regardless of the specific hardware implementation, thereby enabling technology upgrades without physical integration complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11836348B2Upgrade for system with differing capacities

Publication Date: 2023.12.05 PURE STORAGE INC

AI summary

In one implementation, a system resource is added to a storage system, for a resource-preserving upgrade. An upgrade component is coupled to the storage system as a temporary storage system shelf. Storage drives are moved from the storage system to the upgrade component. One or more storage controllers of the upgrade component are promoted to take over data services from the storage system.