Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ DataArts Studio/ User Guide/ DataArts Migration (Real-Time Jobs)/ Tutorials/ Migrating a DRS Task to DataArts Migration

Migrating a DRS Task to DataArts Migration

Updated on 2025-01-21 GMT+08:00

This section describes how to migrate a Data Replication Service (DRS) task to DataArts Migration.

Prerequisites

  • A real-time synchronization task has been created in DRS. For details, see What Is DRS?
  • A real-time data integration environment has been prepared based on Check Before Use.

Preparations

  • Assess required DataArts Migration resources.

    Assess the DataArts Migration resources required to run the DRS task. If resources are insufficient, purchase a new resource group.

    Consider the following factors during the assessment:

    • Check the number of tables in the DRS task.

      Click the DRS task name to view its details. Choose Synchronization Mapping and view the number of tables. A job in DataArts Migration provides an optimal performance when the number of tables in the job is less than 50.

      Figure 1 Checking the number of tables in a DRS task
    • View the maximum amount data that can be synchronized concurrently.

      Go to the DRS task monitoring page and view the monitoring metrics, mainly the Rows Written into Destination Database per Second metric. In addition, check whether the DRS task has a latency.

      A job with 8 CUs in DataArts Migration can synchronize 8,000 records per second. You are advised to configure an independent job for a table with a large amount of data.

      Figure 2 Viewing monitoring metrics
      Figure 3 Viewing metric details
    • Create jobs based on the customer's requirements.
  • Enable network communications.

    Enable communications between the migration resource group and the data source. In the basic information of the DRS task, view the data source configuration. Enable the communications by following corresponding instructions

    Figure 4 Viewing the data source configuration

Creating and Starting a Migration Job

  1. Create a job.

    Create a migration job based on the prepared job splitting solution. Do not start the job.

  2. Obtain the DRS security location.

    Migration jobs need to be started based on the DRS synchronization location to ensure that data transmission is not interrupted and that no data is missing.

    Contact DRS O&M personnel to obtain the security location (a binlog file name) for DRS task synchronization. Contact MySQL database O&M personnel to query the timestamp of the synchronized DRS binlog based on the security location and start the migration job based on the timestamp.

  3. Before starting a migration job, suspend the DRS job to avoid write conflicts.

    Start the migration job based on the obtained security location. You can set the start time of the migration job to a time earlier (30 minutes recommended) than the security location to avoid data loss.

    For example, if the obtained DRS security location timestamp is 2024-11-29 12:00:00, you can set the time for starting the migration job to 2024-11-29 11:30:00.

    Figure 5 Setting the time for starting the migration job

    After the migration job is started and is running stably, you can stop the DRS task.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback