Storage Service Metadata Mobility via Device Relocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage systems face delays and overhead when moving storage services from one system to another, as they require a separate step to copy metadata, which is time-consuming and disrupts service continuity.

Innovation Solution

Storage service metadata is maintained on the same device as user data, allowing for seamless transfer and re-establishment of services on a new system without the need for separate metadata copying, enabling quick service restart.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If storage service metadata is stored separately from user data on a different storage system, then data security and service stability are improved, but service migration time and complexity increase significantly

Engineering Contradiction:
Improveservice stabilityVSAvoidservice migration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments storage service metadata from the main storage system by placing it on a separate movable storage device. This allows the metadata to be independently managed and transferred without moving the entire storage system, thereby reducing migration time while maintaining service stability through isolated metadata protection.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-configuring the movable storage device with necessary metadata before service migration is needed. This includes pre-establishing the metadata structure and relationships, so that when migration occurs, the new storage system can quickly adopt the pre-prepared metadata without time-consuming generation or copying processes.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If storage service metadata is copied from the original storage system to the new storage system, then service continuity is maintained, but the copying process is time-consuming and delays service resumption

Engineering Contradiction:
Improveservice continuityVSAvoidservice resumption speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent uses copying by placing metadata on a movable storage device that can be physically or logically moved between storage systems. This copying mechanism maintains service continuity as the metadata travels with the user data, while significantly improving service resumption speed compared to traditional network-based copying methods.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent merges metadata with user data by storing both on the same movable storage device. This combination ensures that metadata and data arrive together during migration, eliminating the need for separate copying operations and enabling faster service resumption on the new storage system.

Inventive Principle:
Principle #5Merging (Combining)

3Speed

If storage service metadata is maintained on the same device as user data, then service migration speed is improved, but device complexity and management overhead increase

Engineering Contradiction:
Improveservice migration speedVSAvoidstorage device complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent applies universality by designing the movable storage device to serve multiple functions: storing user data, storing metadata, and acting as a transport medium between storage systems. This multi-functionality improves service migration speed while managing device complexity through consolidated design rather than separate specialized components.

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

Data Source

PatentUS10148750B1Services mobility in storage systems
Publication Date: 2018.12.04 EMC IP HLDG CO LLC
  • US10148750B1 patent drawing
  • US10148750B1 patent drawing
  • US10148750B1 patent drawing

AI summary

While providing a storage service to a client system, a storage system maintains a complete set of storage service metadata for the service on the same storage device that stores the user data received from the client system. When an event is detected that requires the storage service to be moved to a new storage system, the storage service can be moved to a new storage system by moving the storage device containing both the user data and the storage service metadata to the new storage system. The new storage system detects the storage device that has been moved, and detects the storage service metadata and user data. The new storage system then uses the storage service metadata and user data from the storage device to immediately reestablish the storage service with the client system, without having to perform a separate step of copying the storage service metadata from the previous storage system.