Pseudoname Mapping for Seamless Data Migration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Data migrations in computer systems often require applications to be taken offline, leading to limited time windows and significant challenges in planning and managing large-scale migrations with minimal disruption to data availability.

Innovation Solution

The method involves using pseudonames to enable data migration from a source logical volume to a target logical volume, ensuring data coherence and minimizing disruptions by mapping and unmapping pseudonames without altering the file system or application layers, allowing continuous access during the migration process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional data migration methods are used, then data can be migrated from source to target storage, but applications must be taken offline causing service interruption and limited time windows

Engineering Contradiction:

Improvedata availabilityVSAvoidmigration time window

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the data migration process into multiple independent phases: initial data copy, coherency verification, pseudoname remapping, and final switchover. This allows the migration to proceed while applications remain online, with the actual switch occurring only after verification succeeds.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by copying data to the target volume and verifying coherency before applications need to access the migrated data. The pseudoname remapping is prepared in advance but not activated until the final switch, ensuring data is ready before it's needed.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 3:

The patent introduces pseudonames as an intermediary layer between applications and physical storage volumes. This abstraction layer allows seamless remapping from source to target volumes without applications needing to know or care about the underlying storage changes, enabling continuous access during migration.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If data migration is performed with applications online, then service continuity is maintained, but data coherency and consistency become difficult to ensure

Engineering Contradiction:

Improveservice continuityVSAvoiddata coherency

Core Design Contradiction:

ProductivityVSManufacturing precision

Solution Approach 1:

The patent implements feedback mechanisms by verifying data coherency between source and target volumes before completing the migration. The system checks that data remains consistent and coherent throughout the migration process, and only proceeds with the final switch when verification succeeds.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent makes the migration process dynamic by allowing it to be paused, resumed, and verified at multiple stages. The pseudoname mapping can be changed dynamically after coherency is confirmed, and the process can adapt to ensure data integrity without forcing applications offline.

Inventive Principle:

Principle #15Dynamics

3Speed

If pseudoname remapping is performed directly without verification, then migration speed increases, but data integrity and coherency may be compromised

Engineering Contradiction:

Improvemigration speedVSAvoiddata integrity

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The patent performs preliminary data copying and coherency verification before the critical pseudoname remapping operation. This ensures that when the remapping does occur, the data is already verified and ready, maintaining both speed and integrity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The pseudoname abstraction layer serves as an intermediary that decouples the speed of data copying from the criticality of the final switch. Data can be copied quickly in the background while applications continue to access the source volume through the existing pseudoname mapping, until verification is complete.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Reliability

If complex migration procedures are used to ensure data coherency, then data integrity is maintained, but system complexity and operational difficulty increase

Engineering Contradiction:

Improvedata integrityVSAvoidmigration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal pseudoname mapping mechanism that handles multiple functions: application access abstraction, migration orchestration, coherency verification coordination, and seamless switchover. This single mechanism replaces multiple complex procedures that would otherwise be needed to achieve the same goals.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7904681B1Methods and systems for migrating data with minimal disruption

Publication Date: 2011.03.08 EMC IP HLDG CO LLC

AI summary

Methods and systems are disclosed that enable data migration from a source logical volume to a target logical volume in signal communication with the source logical volume with minimal disruption to the accessibility of that data. The coherency of data on the source logical volume and the target logical volume is confirmed. A first pseudoname is unmapped from a source logical volume identifier, and a second pseudoname is unmapped from a target logical volume identifier. A logical volume identifier includes information specific to the logical volume it identifies. The first pseudoname is then mapped to the target logical volume identifier.