Automated File-Based Storage Hardware Addition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data storage system upgrades from block-based to unified storage systems are cumbersome, requiring manual intervention, physical media handling, and allocation of disk space, which is time-consuming and error-prone, and necessitate a system manufacturer's representative, leading to increased costs and reduced LUN availability.

Innovation Solution

The automated addition of file-based storage hardware to a block-based storage system, where the file-based storage hardware detects attachment and installs operation instructions without user intervention, using bootable bit images and predefined logical units, eliminating the need for manual disk space allocation and reducing reliance on physical media and manufacturer representatives.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual installation procedures are used for adding file-based storage hardware to a block-based storage system, then the installation can be completed with existing conventional methods, but the process is time-consuming, error-prone, and requires manufacturer representative involvement

Engineering Contradiction:
Improveinstallation automationVSAvoidinstallation complexity
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The file-based storage hardware automatically detects its attachment to the block-based storage system and autonomously installs operation instructions without requiring user intervention or manufacturer representative involvement. The system performs self-configuration by detecting the electrical coupling and automatically proceeding with installation procedures.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The block-based storage system pre-defines a set of logical units (LUs) specifically for file-based storage hardware before the hardware is even connected. This preliminary allocation eliminates the need for manual disk space allocation during installation, allowing the file-based hardware to immediately access predefined LUs upon connection.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If manual disk space allocation is performed during installation, then disk space can be assigned to file-based storage hardware, but the process is time-consuming and reduces LUN availability for other uses

Engineering Contradiction:
Improveinstallation speedVSAvoidinstallation time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The block-based storage system pre-defines a set of logical units (LUs) specifically for file-based storage hardware before the hardware is even connected. This preliminary allocation eliminates the need for manual disk space allocation during installation, allowing the file-based hardware to immediately access predefined LUs upon connection.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If physical media and manual configuration steps are used, then installation can proceed with conventional methods, but the process requires user intervention and is prone to errors

Engineering Contradiction:
Improveinstallation reliabilityVSAvoidinstallation procedure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The file-based storage hardware automatically detects its attachment to the block-based storage system and autonomously installs operation instructions without requiring user intervention or manufacturer representative involvement. The system performs self-configuration by detecting the electrical coupling and automatically proceeding with installation procedures.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent extracts the installation procedure from manual user execution and transfers it to automated execution by the system itself. The complex configuration steps, initiator record associations, and operation instruction installations are all performed automatically by the system without requiring user presence or physical media handling.

Inventive Principle:
Principle #2Taking out (Extraction)

4Ease of manufacture

If manufacturer representative involvement is required for system upgrade, then proper installation can be ensured, but costs increase and deployment time extends

Engineering Contradiction:
Improvesystem deployment easeVSAvoiddeployment time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The file-based storage hardware automatically detects its attachment to the block-based storage system and autonomously installs operation instructions without requiring user intervention or manufacturer representative involvement. The system performs self-configuration by detecting the electrical coupling and automatically proceeding with installation procedures.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8700832B1Automated addition of file based hardware and file based access services in a data storage system
Publication Date: 2014.04.15 EMC IP HLDG CO LLC
  • US8700832B1 patent drawing
  • US8700832B1 patent drawing
  • US8700832B1 patent drawing

AI summary

A method for adding file based storage hardware to a block based storage system includes detecting, by the file based storage hardware, an electrical coupling between the file based storage hardware and the block based storage system, the block based storage system having a set of logical units (LUs) predefined as file based storage hardware specific LUs. The method includes forwarding, by the file based storage hardware, an initiator record to the block based storage system, the initiator record configured to control access by the file based storage hardware to data stored by the block based storage system and the initiator record having a file based storage hardware specific identifier. The method includes, following the block based storage system associating the initiator record having the file based storage hardware specific identifier with the predefined file based storage hardware specific LUs, establishing a communication path with the block based storage system.