Unified Data Migration Framework for Scalable Storage Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data migration solutions are limited to specific application scenarios, data formats, and hardware configurations, making them unsuitable for large-scale data centers and cloud computing environments, where they face challenges in universality, scalability, and management complexity.

Innovation Solution

A unified and scalable data migration framework with a centralized control plane and pluggable data plane that supports various data formats and migration modes, using a description file to register and select executing units based on user requests, and encapsulating data migration technologies into containers for flexibility and scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing data migration solutions are used, then data migration can be performed in specific scenarios, but universality and adaptability are poor

Engineering Contradiction:
Improveadaptability to different data formats and scenariosVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal data migration system that supports multiple data formats (files, file systems, magnetic discs, databases, virtual machines, containers) and migration modes (synchronization, asynchronization, layering, data streams) through a unified architecture. The system uses standardized description files and a common control plane to handle diverse migration scenarios, eliminating the need for separate solutions for each data type or scenario.

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

Solution Approach 2:

The system segments data migration functionality into independent executing units, each capable of handling specific migration tasks. These units are registered with the control plane and can be dynamically selected and combined based on migration requirements. The segmentation allows the system to maintain simplicity while providing comprehensive functionality through modular composition.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If close-coupling architecture is adopted, then implementation is straightforward, but universality and extensibility are poor

Engineering Contradiction:
Improveextensibility to new scenariosVSAvoidease of implementation
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system employs a dynamic architecture where the control plane can dynamically select, instantiate, and manage executing units based on migration requests. The system adapts to different scenarios by dynamically composing appropriate combinations of executing units rather than requiring static, scenario-specific configurations. This dynamic approach enables easy extension to new scenarios while maintaining operational simplicity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The control plane acts as an intermediary between users and executing units, abstracting the complexity of migration implementation. Users submit migration requests through the control plane, which then automatically selects and coordinates the appropriate executing units. This intermediary layer shields users from implementation details while enabling flexible and extensible system behavior.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If hardware-specific solutions are used, then performance can be optimized, but scalability and fast extension are difficult

Engineering Contradiction:
Improvedata migration performanceVSAvoidscalability to large-scale environments
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system uses containerization to create portable, standardized execution environments that can be replicated and distributed across multiple hardware platforms. Executing units are packaged in containers that encapsulate all necessary dependencies and configurations, allowing them to be copied and deployed to different hardware systems without modification. This enables performance optimization on specific hardware while maintaining scalability across large-scale environments.

Inventive Principle:
Principle #26Copying

4Extent of automation

If manual configuration is used, then control is precise, but management complexity increases in large-scale environments

Engineering Contradiction:
Improveautomatic resource selection and scalingVSAvoidmanagement complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system implements self-service automation where the control plane automatically selects appropriate executing units, allocates resources, and manages migration tasks based on user requests and system state. The system autonomously handles resource selection, scaling, and coordination without requiring manual configuration or intervention. This automation reduces management complexity while maintaining precise control over migration operations, especially in large-scale environments where manual management would be impractical.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10678464B2Methods and apparatuses for data migration of a storage device
Publication Date: 2020.06.09 EMC IP HLDG CO LLC
  • US10678464B2 patent drawing
  • US10678464B2 patent drawing
  • US10678464B2 patent drawing

AI summary

Embodiments of the present disclosure provide methods and apparatuses for data migration of storage devices including registering at least one executing unit for data migration, each of the at least one executing unit corresponding to description file; extracting and storing information contained in the description file corresponding to each of the at least one executing unit; receiving a data migration request from a user; in response to the data migration request from the user, selecting an executing unit for data migration of the user at least based on part of the stored information contained in the description file; and scheduling an instance of the selected executing unit to execute data migration of the user. The methods or apparatuses according to embodiments of the present disclosure can implement, in a uniform and scalable manner, data migration for various formats, various performance requirements, and application scenarios.