From MySQL Schema and Logic Table to DDM

Supported Source and Destination Databases

Prerequisites

• You have logged in to the DRS console.
• Your account balance is greater than or equal to $0 USD.
• For details about the DB types and versions supported by real-time migration, see Supported Databases.
• If a subaccount is used to create a DRS task, ensure that an agency has been added. To create an agency, see Agency Management.

Suggestions

• When a task is being started or in the full migration phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
• To maintain data consistency before and after the migration, do not write data to the source and destination databases in the full migration mode. In the full+incremental migration mode, you can continue the migration while data is still being written to the source database.

• The success of database migration depends on environment and manual operations. To ensure a smooth migration, perform a migration trial before you start the migration to help you detect and resolve problems in advance.
• Start your migration task during off-peak hours. A less active database is easier to migrate successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the migration.
  • If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full migration, and two to four CPUs are occupied.
  • The data being migrated may be locked by other transactions for a long period of time, resulting in read timeout.
  • Due to the inherent characteristics of MySQL, in certain scenarios the performance may be negatively affected. For example, if the CPU resources are insufficient and the storage engine is TokuDB, the read speed on tables may be decreased by 10%.
  • If DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
  • If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.
  • For more information about the impact of DRS on databases, see What Is the Impact of DRS on Source and Destination Databases?
• Data-Level Comparison

  To obtain accurate comparison results, start data comparison at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

Precautions

Before creating a migration task, read the following notes:

Procedure

This section describes how to configure a task for migration from MySQL schema and logic table to DDM over a public network.

1. On the Online Migration Management page, click Create Migration Task.
2. On the Create Replication Instance page, specify task name, description, and the replication instance details, and click Next.
   Figure 1 Migration task information
   

   Table 3 Task information

   Parameter	Description
   Region	The region where the replication instance is deployed. You can change the region. To reduce latency and improve access speed, select the region closest to your services.
   Task Name	The task name consists of 4 to 50 characters, starts with a letter, and can contain only letters (case-insensitive), digits, hyphens (-), and underscores (_).
   Description	The description can contain up to 256 characters and cannot contain special characters !=<>&'\"

   Figure 2 Replication instance information
   

   Table 4 Replication instance settings

   Parameter	Description
   Data Flow	Select To the cloud. The destination database must be a database on the current cloud.
   Source DB Engine	Select MySQL sharding.
   Destination DB Engine	Select DDM.
   Network Type	The public network is used as an example. Available options: VPC, VPN or Direct Connect, and Public network. By default, the value is Public network. VPC is suitable for migrations of cloud databases. Public network is suitable for migrations from on-premises or external cloud databases to the destination databases bound with an EIP. VPN is suitable for migrations from on-premises databases to cloud databases or between cloud databases across regions. Direct Connect is suitable for migrations from on-premises databases to cloud databases or between cloud databases across regions.
   Destination DB Instance	Select the DB instance you have created.
   Replication Instance Subnet	The subnet where the replication instance resides. You can also click View Subnet to go to the network console to view the subnet where the instance resides. By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides, and there are available IP addresses for the subnet. To ensure that the replication instance is successfully created, only subnets with DHCP enabled are displayed.
   Migration Type	Full: This migration type is suitable for scenarios where service interruption is acceptable. All objects in non-system databases are migrated to the destination database at one time, including tables, views, stored procedures, and triggers. NOTE: If you are performing a full migration, do not perform operations on the source database. Otherwise, data generated in the source database during the migration will not be synchronized to the destination database. Full+Incremental: This migration type allows you to migrate data without interrupting services. After a full migration initializes the destination database, an incremental migration initiates and parses logs to ensure data consistency between the source and destination databases. NOTE: If you select Full+Incremental, data generated during the full migration will be continuously synchronized to the destination database, and the source remains accessible.
   Source DB Instance Quantity	The default minimum number of source DB instances is 2 and the maximum number is 16. You can set this parameter based on the number of source database shards.
   Enterprise Project	If the DB instance has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list. You can also go to the ProjectMan console to create a project. For details about how to create a project, see the ProjectMan User Guide.
   Tags	This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 10 tags. After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.

3. On the Configure Source and Destination Databases page, wait until the replication instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the replication instance. After the connection tests are successful, select the check box before the agreement and click Next.
   • Source database information
     Figure 3 Source database information
     

     Table 5 Source database information

     Parameter	Description
     Middleware IP Address or Domain Name	The IP address or domain name of the source database.
     Port	The port of the source database. Range: 1 – 65535
     Middleware Username	The username for accessing the source database.
     Middleware Password	The password for the database username.
     SSL Connection	SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate. NOTE: The maximum size of a single certificate file that can be uploaded is 500 KB. If the SSL certificate is not used, your data may be at risk.
     Sharded Database	The sharded database details.

     

     The IP address, domain name, username, and password of the source database are encrypted and stored in DRS, and will be cleared after the task is deleted.

   • Destination database configuration
     Figure 4 Destination database information
     

     Table 6 Destination database settings

     Parameter	Description
     DB Instance Name	The DB instance you selected when creating the migration task. This parameter cannot be changed.
     Database Username	The username for accessing the destination database.
     Database Password	The database username and password are encrypted and stored in the system and will be cleared after the task is deleted.

     

     The username and password of the destination databases are encrypted and stored in DRS, and will be cleared after the task is deleted.

4. On the Set Task page, select migration objects and click Next.
   Figure 5 Migration object
   

   Table 7 Migrate Object

   Parameter	Description
   Migrate Object	After the objects are migrated to the destination database, the object names will remain the same as those in the source database and cannot be modified. NOTE: Structures that are not created in the destination database are not migrated by default.

5. On the Check Task page, check the migration task.
   • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.

     For details about how to handle check failures, see Checking Whether the Source Database Is Connected in Data Replication Service User Guide.

     Figure 6 Pre-check
     
   • If the check is complete and the check success rate is 100%, click Next.
     

     You can proceed to the next step only when all checks are successful. If any alarms are generated, view and confirm the alarm details first before proceeding to the next step.

6. On the displayed page, specify Start Time, Send Notification, SMN Topic, Synchronization Delay Threshold, and Stop Abnormal Tasks After and confirm that the configured information is correct and click Submit to submit the task.
   Figure 7 Task startup settings
   

   Table 8 Task startup settings

   Parameter	Description
   Started Time	Set Start Time to Start upon task creation or Start at a specified time based on site requirements. The Start at a specified time option is recommended. NOTE: The migration task may affect the performance of the source and destination databases. You are advised to start the task in off-peak hours and reserve two to three days for data verification.
   Send Notifications	SMN topic. This parameter is optional. If an exception occurs during migration, the system will send a notification to the specified recipients.
   SMN Topic	This parameter is available only after you enable Send Notifications and create a topic on the SMN console and add a subscriber. For details, see Simple Message Notification User Guide.
   Synchronization Delay Threshold	During an incremental migration, a synchronization delay indicates a time difference (in seconds) of synchronization between the source and destination database. If the synchronization delay exceeds the threshold you specify, DRS will send alarms to the specified recipients. The value ranges from 0 to 3,600. To avoid repeated alarms caused by the fluctuation of delay, an alarm is sent only after the delay has exceeded the threshold for six minutes. NOTE: In the early stages of an incremental migration, there is more delay because more data is waiting to be synchronized. In this situation, no notifications will be sent. Before setting the delay threshold, enable Send Notification. If the delay threshold is set to 0, no notifications will be sent to the recipient.
   Stop Abnormal Tasks After	Number of days after which an abnormal task is automatically stopped. The value must range from 14 to 100. The default value is 14. NOTE: Tasks in the abnormal state are still charged. If tasks remain in the abnormal state for a long time, they cannot be resumed. Abnormal tasks run longer than the period you set (unit: day) will automatically stop to avoid unnecessary fees.

7. After the task is submitted, view and manage it on the Online Migration Management page.
   • You can view the task status. For more information about task status, see Task Statuses.
   • You can click in the upper right corner to view the latest task status.