From GaussDB Distributed to MySQL¶
Supported Source and Destination Databases¶
Source DB | Destination DB |
---|---|
|
|
Supported Synchronization Objects¶
Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.
Type | Synchronization Scope |
---|---|
Synchronization scope |
|
Database User Permission Requirements¶
Before you start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.
Type | Incremental |
---|---|
Source database user | The user must have the sysadmin role or the following minimum permissions:
|
Destination database user | Required permissions: INSERT, DELETE, UPDATE, SELECT, and SHOW DATABASES |
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.
The data being synchronized may be locked by other transactions for a long period of time, resulting in read timeout.
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.
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¶
DRS incremental synchronization consists of three phases: task start, incremental synchronization, and task completion. To ensure smooth synchronization, read the following notes before creating a synchronization task.
Type | Restrictions |
---|---|
Starting a task |
|
Incremental synchronization |
|
Synchronization comparison |
|
Stopping a task | Stop a task normally.
Forcibly stop a task.
|
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.
You have read Suggestions and Precautions.
Procedure¶
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 Out of the cloud.
Source DB Engine
Select GaussDB Distributed Edition.
Destination DB Engine
Select MySQL.
Network Type
The public network is used as an example. Available options: Public network and VPN or Direct Connect
Source DB Instance
The GaussDB distributed instance you created.
Synchronization Mode
Incremental
Through log parsing, incremental data generated on the source database is synchronized to the destination database.
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, click Next.
Establish the connectivity between the DRS instance and the source and destination databases.
Network connectivity: Ensure that the source and destination databases accept connections from the DRS instance.
Account connectivity: Ensure that the source and destination databases allows connections from the DRS instance using the username and password.
¶ 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 source database.
Database Password
The password for the database username.
Note
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.
¶ Parameter
Description
IP Address or Domain Name
IP address or domain name of the destination database in the IP address/Domain name:Port format. The port of the destination database. Range: 1 - 65535
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.
Note
The username and password of the destination 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.
On the Set Synchronization Task page, select the objects to be synchronized, and then 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.
Synchronization Object
DRS supports table-level synchronization. You can select data for synchronization based on your 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 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.
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 Confirm Task 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.