From MySQL to GaussDB Distributed¶
Supported Source and Destination Databases¶
Source DB | Destination DB |
---|---|
|
|
Prerequisites¶
You have logged in to the DRS console.
For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.
Suggestions¶
Caution
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.
Start your synchronization task during off-peak hours. 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 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.
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.
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.
Precautions¶
Before creating a synchronization task, read the following notes:
Type | Restrictions |
---|---|
Database permissions |
|
Synchronization object |
|
Source database |
|
Destination database |
|
Precautions |
|
Procedure¶
This section uses real-time synchronization from MySQL to GaussDB distributed as an example to describe how to configure a real-time synchronization task.
On the Data Synchronization Management page, click Create Synchronization Task.
On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.
¶ Parameter
Description
Region
The region where the synchronization 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
!=<>'&"\
¶ Parameter
Description
Data Flow
Select To the cloud.
Source DB Engine
Select MySQL.
Destination DB Engine
Select GaussDB Distributed Edition.
Network Type
The Public network is used as an example. Available options: VPC, Public network and VPN or Direct Connect
Destination DB Instance
An available GaussDB distributed instance.
Synchronization Instance Subnet
Select the subnet where the synchronization instance is located. 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 ensure that there are available IP addresses. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.
Synchronization mode
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.
Tags
This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
Note
If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.
On the Configure Source and Destination Databases page, wait until the synchronization 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 synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.
¶ Parameter
Description
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 SSL is disabled, your data may be at risk.
Note
The username and password of the source database are encrypted and stored in DRS and will be cleared after the task is deleted.
¶ Parameter
Description
DB Instance Name
The GaussDB distributed instance selected during synchronization task creation. 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.
On the Set Synchronization Task page, select synchronization objects and click Next.
¶ Parameter
Description
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:
Ignore
The system will skip the conflicting data and continue the subsequent synchronization process.
Report error
The synchronization task will be stopped and fail.
Overwrite
Conflicting data will be overwritten.
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.
Synchronization Object
You can synchronize tables based on the service requirements.
If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.
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 the object name contains spaces, the spaces before and after the object name are not displayed. If there are multiple spaces between the object name and the object name, only one space is displayed.
The name of the selected synchronization object cannot contain spaces.
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.
If all check items are successful, click Next.
Note
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.
On the displayed page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.
¶ Parameter
Description
Started 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.
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.