Storage Identifier Mapping for Seamless Data Migration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional data migration approaches are inefficient and complex, requiring data to be written to both source and destination storage resources during migration, resulting in double network transfers and extensive reconfiguration, especially when handling write requests and managing identifiers.

Innovation Solution

A method and system where the destination storage resource is assigned the same identifier as the source storage resource, allowing direct migration with reduced network transfers and automatic host connection to the destination, eliminating the need for reconfiguration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional data migration approach is used with different identifiers for source and destination storage resources, then data can be migrated between storage resources, but management complexity increases and network traffic doubles

Engineering Contradiction:

Improvedata migration efficiencyVSAvoidmanagement complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent merges the identifier spaces of source and destination storage resources by assigning the destination the same identifier as the source. This eliminates the need for separate identifier management and reduces network traffic by allowing direct migration without double transfers, thereby resolving the contradiction between migration capability and management complexity

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

Instead of using different identifiers for source and destination as in traditional approaches, the patent inverts the conventional wisdom by assigning identical identifiers. This inversion simplifies the migration process and reduces network traffic while maintaining data integrity, directly addressing the management complexity issue

Inventive Principle:

Principle #13The other way round (Inversion)

2Reliability

If data is written to both source and destination storage resources during migration, then data integrity is maintained, but network traffic increases and migration time increases

Engineering Contradiction:

Improvedata integrityVSAvoidmigration time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-establishing the destination storage resource with the same identifier as the source before migration begins. This allows the migration process to proceed directly without requiring simultaneous writes to both locations, reducing migration time while maintaining data integrity through the identifier mapping mechanism

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses a copying mechanism where the destination storage resource is created as a copy of the source with the same identifier. This allows data to be migrated efficiently without requiring dual writes during the migration process, reducing both network traffic and migration time while preserving data integrity

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If destination storage resource is assigned a new identifier different from source, then storage resources can be distinguished, but host reconfiguration is required and network reconfiguration is needed

Engineering Contradiction:

Improvestorage resource distinguishabilityVSAvoidhost reconfiguration requirement

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent merges the identifier assignment for source and destination storage resources, assigning the same identifier to both. This eliminates the need for host reconfiguration and network reconfiguration while maintaining distinguishability through the migration context and identifier mapping mechanism, directly resolving the ease of operation issue

Inventive Principle:

Principle #5Merging (Combining)

4Productivity

If traditional migration approach with separate identifiers is used, then data can be migrated, but network traffic doubles and migration bandwidth is reduced

Engineering Contradiction:

Improvedata migration capabilityVSAvoidnetwork traffic

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The patent merges the network transfer paths by using identical identifiers for source and destination storage resources. This allows data to be transferred only once during migration rather than requiring double transfers, thereby reducing network traffic and improving migration bandwidth efficiency while maintaining full data migration capability

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS8539180B2System and method for migration of data

Publication Date: 2013.09.17 DELL PROD LP

AI summary

Systems and methods for data migration are disclosed. A method may include allocating a destination storage resource to receive migration data. The method may also include assigning the destination storage resource a first identifier value equal to an identifier value associated with a source storage resource. The method may additionally include assigning the source storage resource a second identifier value different than the first identifier value. The method may further include migrating data from the source storage resource to the destination storage resource.