From MySQL to MySQL
Supported Source and Destination Databases
Source DB |
Destination DB |
---|---|
|
|
Suggestions
- When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
- To keep data consistency before and after the synchronization, ensure that no data is written to the destination database during the synchronization.
- The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
- You are advised to start your synchronization task during off-peak hours by setting Start Time to Start at a specified time. A less active database is easier to synchronize successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the synchronization. If you have to synchronize data during peak hours, you can select Yes for Flow Control to adjust the synchronization speed.
- If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full synchronization, and two to four CPUs are occupied.
- To ensure data consistency, tables to be synchronized without a primary key may be locked for 3s.
- The data being synchronized 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%.
- When 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 How Does DRS Affect the Source and Destination Databases?
- Data-level comparison
To obtain accurate comparison results, compare data 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.
- If you create a many-to-one synchronization task, refer to Constraints and Operation Suggestions on Many-to-One Scenario.
- For many-to-one synchronization tasks that involve the synchronization of the same table, DDL operations cannot be performed. Otherwise, all synchronization tasks fail.
Precautions
Before creating a synchronization task, read the following notes:
- You are advised to create an independent database account for DRS task connection to prevent task failures caused by database account password modification.
- After changing the account passwords for the source and destination databases, modify the connection information of the DRS task by referring to Modifying Connection Information to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
Type |
Restrictions |
---|---|
Database permissions |
|
Synchronization object |
|
Source database |
|
Destination database |
|
Precautions |
|
Procedure
This section uses synchronization from RDS for MySQL to MySQL as an example to describe how to use DRS to create a real-time synchronization task.
- On the Data Synchronization Management page, click Create Synchronization Task.
- On the Create Synchronization Instance page, select a region and project, specify the task name, description, and the synchronization instance details, and click Create Now.
- Task information description
Figure 1 Synchronization task information
Table 3 Task information Parameter
Description
Region
The region where the replication instance is deployed. You can change the region.
Project
The project corresponds to the current region and can be changed.
Task Name
The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).
Description
The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\
- Synchronization instance details
Figure 2 Synchronization instance details
Table 4 Synchronization instance settings Parameter
Description
Data Flow
Select Out of the cloud. The source database is a database on the current cloud.
Source DB Engine
Select MySQL.
Destination DB Engine
Select MySQL.
Network Type
Public network is used as an example. Available options: Public network, VPC, VPN or Direct Connect
- VPC is suitable for data synchronization between cloud databases of the same account in the same region and VPC.
- Public network is suitable for data synchronization from on-premises or external cloud databases to the destination databases bound with an EIP.
- VPN or Direct Connect is suitable for data synchronization from on-premises databases to cloud databases, between databases of different accounts in the same region on the cloud, or between databases across regions on the cloud using a VPN, Direct Connect, Cloud Connect, VPCEP, or a VPC peering connection.
Source DB Instance
The RDS for MySQL instance you created.
Synchronization Instance Subnet
Select the subnet where the synchronization instance is located. You can also click View Subnets 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 synchronization instance is successfully created, only subnets with DHCP enabled are displayed.
Security Group
Select a security group. You can use security group rules to allow or deny access to the instance.
Synchronization Mode
The synchronization mode supported by a DRS task. Full+Incremental is used as an example. For details about the underlying working principles for full or incremental synchronization, see Product Architecture and Function Principles.
- Full+Incremental
This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.
NOTE:If you select Full+Incremental, data generated during the full synchronization will be continuously synchronized to the destination database, and the source remains accessible.
- Incremental
Through log parsing, incremental data generated on the source database is synchronized to the destination database.
Specify EIP
This parameter is available when you select Public network for Network Type. Select an EIP to be bound to the DRS instance. DRS will automatically bind the specified EIP to the DRS instance and unbind the EIP after the task is complete.
For details about the data transfer fee generated using a public network, see EIP Price Calculator.
- Task type
Figure 3 Task type
Table 5 Task type information Parameter
Description
Specifications
DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.
NOTE:DRS allows you to upgrade specifications only for single-AZ synchronization tasks. Task specifications cannot be downgraded. For details, see Changing Specifications.
AZ
Select the AZ where you want to create the DRS task. Selecting the one housing the source or destination database can provide better performance.
- Enterprise Project and Tags
Figure 4 Enterprise projects and tags
Table 6 Enterprise Project and Tags Parameter
Description
Enterprise Project
An enterprise project you would like to use to centrally manage your cloud resources and members. Select an enterprise project from the drop-down list. The default project is default.
For more information about enterprise project, see Enterprise Management User Guide.
To customize an enterprise project, click Enterprise in the upper right corner of the console. The Enterprise Project Management Service page is displayed. For details, see Creating an Enterprise Project in Enterprise Management User Guide.
Tags
- Tags a task. This configuration is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
- If your organization has configured tag policies for DRS, add tags to tasks based on the policies. If a tag does not comply with the policies, task creation may fail. Contact your organization administrator to learn more about tag policies.
- After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically stops.
- Task information description
- After the synchronization instance is created, on the Configure Source and Destination Databases page, specify source and destination database information. Then, click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.
In different data flow scenarios, the source and destination database settings are different. Specify the required parameters based on the GUI.
- Source database information
Figure 5 Source database information
Table 7 Source database settings Parameter
Description
DB Instance Name
The RDS DB instance selected during synchronization task creation. This parameter cannot be changed.
Database Username
The username for accessing the source database.
Database Password
The password for the database username.
SSL Connection
If SSL connection is required, enable SSL on the source database, ensure that related parameters have been correctly configured, and upload an SSL certificate.
NOTE:- The maximum size of a single certificate file that can be uploaded is 500 KB.
- If SSL is disabled, your data may be at risk.
The username and password of the source database are encrypted and stored in the database and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.
- Destination database information
Figure 6 Destination database information
Table 8 Destination database settings Parameter
Description
IP Address or Domain Name
The IP address or domain name of the destination database.
Port
The port of the destination database. Range: 1 - 65535
Database Username
The username for accessing the destination 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 SSL is disabled, your data may be at risk.
The IP address, port, username, and password of the destination database are encrypted and stored in the database and the synchronization instance, and will be cleared after the task is deleted.
- Source database information
- On the Set Synchronization Task page, select the conflict policy and synchronization objects, and then click Next.
Figure 7 Synchronization mode
Table 9 Synchronization mode and object Parameter
Description
Flow Control
You can choose whether to control the flow. Flow Control takes effect in the full phase only.
- Yes
You can customize the maximum synchronization speed. During the full synchronization, the synchronization speed of each task (or each subtask in multi-task mode) does not exceed the value of this parameter.
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 Always. 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 synchronization 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:
- The flow control mode takes effect only in the full synchronization phase.
- You can also change the flow control mode after creating a task. For details, see Modifying the Flow Control Mode.
Incremental Conflict Policy
The conflict policy refers to the conflict handling policy during incremental synchronization. By default, conflicts in the full synchronization phase are ignored. Select any of the following conflict policies:
Filter DROP DATABASE
During real-time synchronization, executing DDL operations on the source database may affect the synchronization performance. To reduce the risk of synchronization failure, DRS allows you to filter out DDL operations. Currently, only the delete operations on databases can be filtered by default.
- If you select Yes, the database deletion operation performed on the source database is not synchronized during data synchronization.
- If you select No, related operations are synchronized to the destination database during data synchronization.
Synchronize
Normal indexes and incremental DDLs can be synchronized. You can determine whether to synchronize normal indexes and DDLs based on service requirements.
Create Indexes Along With Table Structure
Indicates whether to create indexes along with the table structure in the full synchronization phase.
- Yes: Indexes are migrated when the table structure is migrated in the full synchronization phase.
- No: Indexes are migrated separately after data synchronization.
Synchronize DML
Select the DML operations to be synchronized. By default, all DML operations are selected.
If you do not select Delete, DELETE statements in the incremental data of the source database will not be synchronized, which may cause a data inconsistency. As a result, there may be a data conflict or the task may fail.
Start Point
This option is available if you select Incremental in 2. The logs of the source database are obtained from the position after the start point during an incremental synchronization.
Run show master status to obtain the start point of the source database and set File, Position, and Executed_Gtid_Set as prompted.
Data Synchronization Topology
This parameter is available when Incremental DDLs is selected for Synchronize. Data synchronization supports multiple synchronization topologies. You can plan your synchronization instances based on service requirements. For details, see Data Synchronization Topologies.
Synchronize DDLs
This parameter is available when Incremental DDLs is selected for Synchronize. Select DDL type for incremental synchronization. You can select Default or Custom based on your service requirements.
- Default
- During database-level synchronization, all DDL operations in the binlog related to database objects, except DDL related to permissions, are synchronized to the destination. Common DDL statements are CREATE_TABLE and RENAME_TABLE.
- During table-level synchronization, only DDL operations in the binlog related to the selected tables are synchronized. Common DDL statements are ADD_COLUMN, MODIFY_COLUMN, and ALTER_COLUMN.
- Custom: You can select the DDL type to be synchronized as required. The DDL types supported by different data flow types are displayed on the GUI.
If Incremental DDLs is selected for Synchronize, but no DDL type is selected for Custom, DDLs will not be synchronized by default.
NOTE:- Only whitelisted users can synchronize incremental DDL operations. You need to submit a service ticket to apply for this function. In the upper right corner of the management console, choose Service Tickets > Create Service Ticket to submit a service ticket.
- One-to-one and one-to-many scenarios: If the DDL usage of the source and destination databases must be consistent, high-risk DDLs must be synchronized. If you do not want a high-risk DDL to be performed in the destination, deselect the high-risk DDL to protect destination data. However, this may cause the synchronization to fail. However, filtering DDL may cause synchronization to fail, for example, column deletion.
- Many-to-one scenarios: Synchronize only the Add Column operation, or tasks may fail or data may be inconsistent due to changes in destination tables.
Online DDL
If table-level synchronization is selected, you can choose whether to synchronize Online DDL. By default, Online DDL is not synchronized.
- Yes: Table-level synchronization supports Online DDL synchronization. You can select three Online DDL tools including PT-OCS, GH-OST, and DMS. The regular expressions can be configured for shadow tables and useless tables in PT-OSC and GH-OST. (Default values are provided. You are advised not to change the regular expressions unless otherwise specified.)
Figure 9 Online DDL
- No: Table-level synchronization does not support Online DDL synchronization.
Synchronization Object
The left pane displays the source database objects, and the right pane displays the selected objects. You can select Tables, Import object file, or Databases for Synchronization Object as required.
- If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one in the right pane. For details, see Changing Object Names (Mapping Object Names).
- If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.
- In the many-to-one scenario, if you want to change the saved database mapping name during table-level synchronization, you need to expand the database.
- For details about how to import an object file, see Importing Synchronization Objects.
NOTE:- To quickly select the desired database objects, you can use the search function.
- If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
- If an object name contains spaces, 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 name of the selected synchronization object cannot contain spaces.
- Yes
- On the Process Data page, set the filtering rules for data processing.
- If data processing is not required, click Next.
- If data processing is required, select Data filtering, Additional Columns, or Processing Columns. For details about how to configure related rules, see Processing Data.
Figure 10 Processing Data
- On the Check Task page, check the synchronization 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 Solutions to Failed Check Items in Data Replication Service User Guide.
- If all check items are successful, 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.
- If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
- On the displayed page, specify Start Time, Send Notifications, SMN Topic, Delay Threshold (s), and Stop Abnormal Tasks After, confirm that the configured information is correct, select the check box before the agreement, and click Submit to submit the task.
Figure 11 Task startup settings
Table 10 Task startup settings Parameter
Description
Start Time
Set Start Time to Start upon task creation or Start at a specified time based on site requirements.
NOTE:After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.
Send Notifications
This parameter is optional. After enabled, select a SMN topic. If the status, latency metric, or data of the migration task is abnormal, DRS will send you a notification.
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.
Delay Threshold (s)
During an incremental synchronization, 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:- If the delay threshold is set to 0, no notifications will be sent to the recipient.
- In the early stages of an incremental synchronization, the synchronization delay is long because a large quantity of data is awaiting synchronization. In this case, no notifications will be sent.
- Before setting the delay threshold, enable Send Notifications.
Data Exception Notification
This parameter is optional. After enabled, DRS will send a notification if the task data is abnormal.
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:- You can set this parameter only for pay-per-use tasks.
- 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, you can view and manage it on the Data Synchronization 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.
- By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you configure the task again, DRS applies for resources for the task again. In this case, the IP address of the DRS instance changes.
- For a public network task, DRS needs to delete background resources after you stop the task. The EIP bound to the task cannot be restored to the Unbound state until background resources are deleted.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot