Creating a Migration Task_Data Replication Service

Process

A complete real-time migration consists of creating a migration task, tracking task progress, analyzing migration logs, and comparing data consistency. By comparing multiple items and data, you can determine the proper time for service migration to minimize the service downtime.

A complete migration involves the following procedures.

Figure 1 Migration process

Step 1: Create a migration task. Select the source and destination databases as required and create a migration task.
Step 2: Check the migration progress. During migration, you can view the migration progress.
Step 3: View migration logs. Migration logs contain alarms, errors, and prompt information. You can analyze system problems based on such information.
Step 4: Compare migration items. You can compare objects and data to be migrated to ensure data consistency.

This section uses the migration from MySQL to RDS MySQL as an example to describe how to configure a migration task over a VPC network on the DRS console.

A VPC network is suitable for migrations of cloud databases.

You can create a migration task that will walk you through each step of the process. After a migration task is created, you can manage it on the DRS console.

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.

Procedure

On the Online Migration Management page, click Create Migration Task.

On the Create Replication Instance page, select a region, configure task details, description, and the replication instance, and click Next.

Figure 2 Migration task information

**Table 1** 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 3 Replication instance information

**Table 2** Replication instance settings
Parameter	Description
Data Flow	Select To the cloud. The destination DB is on the current cloud.
Source DB Engine	Select MySQL.
Destination DB Engine	Select MySQL.
Network Type	Select VPC. 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. For details about networks, see Preparations.
Destination DB Instance	The RDS DB instance you 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.
Destination Database Access	Read-only During migration, the destination database is read-only. After the migration is complete, it restores to the read/write status. This option ensures the integrity and success rate of data migration. Read/Write During the migration, the destination database can be queried or modified. Data being migrated may be modified when operations are performed or applications are connected. It should be noted that background processes can often generate or modify data, which may result in data conflicts, task faults, and upload failures. Do not select this option if you do not fully understand the risks. Set the destination database to Read/Write only when you need to modify other data in the database during the migration. The task cannot be modified after being created.
Migration Type	Full: This migration type is suitable for scenarios where service interruption is acceptable. All objects and data in non-system databases are migrated to the destination database at one time. The objects include tables, views, and stored procedures. 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.
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.

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.

The source database can be an ECS database or an RDS instance. Configure parameters based on different scenarios.

Scenario 1: Databases on an ECS - source database configuration

Figure 4 Self-build on ECS - source database information

**Table 3** Self-build on ECS - source database information
Parameter	Description
Source Database Type	Select Self-built on ECS.
VPC	A dedicated virtual network in which the source database is located. It isolates networks for different services. You can select an existing VPC or create a VPC.
Subnet	A subnet provides dedicated network resources that are isolated from other networks, improving network security. The subnet must be in the AZ where the source database resides. You need to enable DHCP for creating the source database subnet.
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
Database Username	The username for accessing the source database.
Database 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.

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.

Scenario 2: RDS DB instance - source database configuration

Figure 5 RDS DB instance - source database information

**Table 4** RDS DB instance - source database information
Parameter	Description
Source Database Type	Select RDS DB Instance.
DB Instance Name	Select the RDS DB instance to be migrated as the source DB instance.
Database Username	The username for accessing the source database.
Database Password	The password for the database username.

Destination database configuration

Figure 6 Destination database information

**Table 5** Destination database settings
Parameter	Description
DB Instance Name	The RDS DB instance selected during migration task creation. This parameter cannot be changed.
Database Username	The username for accessing the destination database.
Database Password	The password for the database username.
Migrate Definer to User	Yes The Definers of all source database objects will be migrated to the user. Other users do not have permissions for database objects unless these users are authorized. For details about authorization, see How Do I Maintain the Original Service User Permission System After Definer Is Forcibly Converted During MySQL Migration? No The Definers of all source database objects will not be changed. You need to migrate all accounts and permissions of the source database in the next step.

The database username and password are encrypted and stored in the system and will be cleared after the task is deleted.

On the Set Task page, select the accounts and objects to be migrated, and click Next.

Figure 7 Migration type

**Table 6** Migration types and objects
Parameter	Description
Flow Control	You can choose whether to control the flow. Yes You can customize the maximum migration speed. In addition, you can set the time range based on your service requirements. The traffic rate setting usually includes setting of a rate limiting time period and a traffic rate value. Flow can be controlled all day or during specific time ranges. The default value is All day. A maximum of three time ranges can be set, and they cannot overlap. The flow rate must be set based on the service scenario and cannot exceed 9,999 MB/s. Figure 8 Flow control No The migration speed is not limited and the outbound bandwidth of the source database is maximally used, which will increase the read burden on the source database. For example, if the outbound bandwidth of the source database is 100 MB/s and 80% bandwidth is used, the I/O consumption on the source database is 80 MB/s. NOTE: Flow control mode takes effect only during a full migration. You can also change the flow control mode after creating a task. For details, see Modifying the Flow Control Mode.
Take Snapshot	If you perform a full migration, you can take a snapshot for your databases. No This option applies to exports for which no data is written to the source database. If data is modified during a full migration, the exported data is point in time inconsistent. The stability and performance of a migration without a snapshot taken is better than that of a migration with a snapshot taken. Yes A snapshot with consistent data at the point in time is generated during service running. Data changes during migration are not shown in the exported data. NOTE: Snapshot reads use MySQL backup lock to lock global tables and automatically unlock them within 3s after consistent reads are enabled. To prevent full migration failures, take a snapshot when the source database is idle and does not perform DML or DDL operations during snapshot migration. Only MySQL full migration tasks support the snapshot mode. To use this function, you can submit a whitelist application. Do not perform DDL operations during migration in snapshot mode. Otherwise, full migration will fail.
Migrate Account	During a database migration, accounts need to be migrated separately. There are accounts that can be migrated completely, accounts whose permissions need to be reduced, and accounts that cannot be migrated. You can choose whether to migrate the accounts based on service requirements. If you select Yes, you can select the accounts to be migrated as required. Yes If you need to migrate accounts, see Migrating Accounts. No During migration, accounts, permissions, and passwords are not migrated.
Filter DROP DATABASE	To reduce the risks involved in data migration, DDL operations can be filtered out. You can choose not to synchronize certain DDL operations. If you select Yes, any database deletion operations performed on the source database are not migrated during data migration. If you select No, related operations are migrated to the destination database during data migration.
Migrate Object	You can choose to migrate all objects, tables, or databases based on your service requirements. All: All objects in the source database are migrated to the destination database. After the migration, the object names will remain the same as those in the source database and cannot be modified. Tables: The selected table-level objects will be migrated. Databases: The selected database-level objects will be migrated. If the source database is changed, click in the upper right corner before selecting migration objects to ensure that the objects to be selected are from the changed source database. NOTE: If you choose not to migrate all of the databases, the migration may fail because the objects, such as stored procedures and views, in the databases to be migrated may have dependencies on other objects that are not migrated. To prevent migration failure, migrate all of the databases. When you select an object, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed. The search function can help you quickly select the required database objects.

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 9 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 there are any items that require confirmation, view and confirm the details first before proceeding to the next step.
Compare source and destination parameters.
By comparing common and performance parameters for the source databases against those of the destination databases, you can help ensure that services will not change after a migration is completed. You can determine whether to use this function based on service requirements. It mainly ensures that services are not affected after a migration is completed.
- This process is optional, so you can click Next to skip the comparison.
- Compare common parameters:
  If the common parameter values in the comparison results are inconsistent, click Save Change to change the destination database values to be the same as those of the source database.
  
  Figure 10 Modifying common parameters
  
  Performance parameter values in both the source and destination databases can be the same or different.
  - If you need to change the performance parameter values that are consistent in the comparison results to different values, locate the target parameter, enter values in the Change To column, and click Save Change in the upper left corner.
  - If you want to make the performance parameter values of the source and destination database be the same:
    1. Click Use Source Database Value.
      DRS automatically makes the destination database values the same as those of the source database.
      
      Figure 11 One-click modification
      
      You can also manually enter parameter values.
    2. Click Save Change to save your changes.
      The system changes the parameter values based on your settings for the destination database values. After the modification, the list is updated automatically.
      
      Figure 12 Performance parameters
      
      Some parameters in the destination database require a restart before the changes can take effect. The system will display these as being inconsistent. In addition, restart the destination database before the migration task is started or after the migration task is completed. To minimize the impact of this restart on your services, it is recommended that you schedule a specific time to restart the destination database after the migration is complete.
      
      For details about how to set parameters during a comparison, see Parameters for Comparison.
    3. Click Next.

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 13 Task startup settings

**Table 7** 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.

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.

Creating a Migration Task

Process

Prerequisites

Procedure

Feedback

Was this page helpful?