Help Center/ Data Replication Service/ Real-Time Migration/ To the Cloud/ From MySQL to GaussDB(for MySQL) Primary/Standby
Updated on 2022-09-21 GMT+08:00

From MySQL to GaussDB(for MySQL) Primary/Standby

Supported Source and Destination Databases

Table 1 Supported databases

Source DB

Destination DB

  • On-premises MySQL databases
  • MySQL databases on an ECS
  • MySQL databases on other clouds
  • RDS for MySQL
  • GaussDB(for MySQL) primary/standby

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:

Table 2 Precautions

Type

Restrictions

Database permissions

  • Full migration (minimum permissions):
    • The source database user must have the SELECT, SHOW VIEW, and EVENT permissions.
    • The destination database user must have the following permissions: SELECT, CREATE, DROP, DELETE, INSERT, UPDATE, INDEX, EVENT, CREATE VIEW, CREATE ROUTINE, TRIGGER, REFERENCES, and WITH GRANT OPTION.

      If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

  • Full+incremental migration (minimum permissions):
    • The source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT.
    • The destination database user must have the following permissions: SELECT, CREATE, DROP, DELETE, INSERT, UPDATE, INDEX, EVENT, CREATE VIEW, CREATE ROUTINE, TRIGGER, REFERENCES, and WITH GRANT OPTION.

      If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

Migration objects

  • Supported objects: databases, tables, views, indexes, constraints, functions, stored procedures, triggers, and events.
  • The system database and event statuses cannot be migrated.
  • Encrypted tables cannot be migrated.
  • Tables with storage engine different to MyISAM and InnoDB tables cannot be migrated.

Source database

  • The database name, table name, and view name in the source database cannot contain non-ASCII characters or the following characters .<'>`/\"
  • The binlog of the MySQL source database must be enabled and use the row-based format.
  • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
  • If the expire_logs_days value of the source database is 0, the migration may fail.
  • During an incremental migration, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
  • Enable skip-name-resolve for the MySQL source database to reduce the possibility of connection timeout.
  • Enable the Global Transaction Identifier (GTID) of the source database.
  • The source cannot contain empty databases.

Destination database

  • Data cannot be migrated from a newer version database to an older version database.
  • You are advised to use the row-based binlog in the destination MySQL database. Otherwise, an error may occur during an incremental migration.
  • The destination DB instance is running properly.
  • The destination DB instance must have sufficient storage space.
  • The destination DB instance cannot contain databases with the same name as the source databases (except the MySQL system database).
  • The destination database isolation level must be set to at least read committed.

Precautions

  • Cascade operations cannot be performed on tables with foreign keys.
  • If the source databases are RDS MySQL instances, TDE is not supported, and tables with the encryption function cannot be created.
  • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
  • If the source database is an on-premises database and has Percona Server for MySQL 5.6.x or Percona Server for MySQL 5.7.x installed, the memory manager must use Jemalloc to prevent Out of Memory errors caused by frequent queries on system tables.
  • The destination database of a migration task can be set to Read-only or Read/Write.
    • Read-only: During the 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 expire_log_day parameter to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.
  • During task startup or full migration, you are not advised to perform DDL operations on the source database, such as deleting the database, indexes, or views. Otherwise, the migration may fail.
  • During migration, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
  • To ensure data consistency, you are not allowed to modify the destination database (including but not limited to DDL and DML operations) during migration.
  • Ensure that the source database is publicly accessible before the migration task is complete.
  • During migration, do not write the statement-based binlog into the source database.
  • During migration, do not clear the binlog in the source database.
  • During migration, GaussDB(for MySQL) automatically converts the MyISAM table to the InnoDB table. If the conversion fails, the migration fails.
  • During an incremental migration, do not perform the point-in-time recovery (PITR) operation on the source database.
  • During an incremental migration, if distributed transactions exist in the source database, the migration may fail.
  • During an incremental migration, resumable upload is supported. However, data may be repeatedly inserted into a non-transactional table that does not have a primary key when the server system breaks down.
  • During an incremental migration of table-level objects, you are not advised to rename the tables.
  • When a migration task is completed, the system begins to migrate the selected events and triggers. You must therefore check the status of the migration log to ensure database integrity.

Procedure

  1. On the Online Migration Management page, click Create Migration Task.
  2. On the Create Replication Instance page, select a region, configure task details, description, and the replication instance, 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 is a DB instance on the current cloud.

    Source DB Engine

    Select MySQL.

    Destination DB Engine

    Select GaussDB(for MySQL) Primary/Standby Edition.

    Network Type

    Available options: VPC, Public network, and VPN or Direct Connect. By default, the value is Public network.

    • VPC is suitable for migrations of cloud databases.
    • VPN and Direct Connect are suitable for migrations from on-premises databases to cloud databases or between cloud databases across regions.
    • Public network is suitable for migration from on-premises databases or external cloud databases to destination databases.

    Destination DB Instance

    The GaussDB(for MySQL) primary/standby 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.

    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.

    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.

    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 configuration
      Figure 3 Source database information
      Table 5 Source database settings

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

    • Destination database configuration
      Figure 4 Destination database information
      Table 6 Destination database settings

      Parameter

      Description

      DB Instance Name

      The GaussDB(for MySQL) primary/standby instance selected during the migration task creation and cannot be changed.

      Database Username

      The username for accessing the destination database.

      Database Password

      The password for the database username.

      Migrate Definer to User

      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 Migration object

    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 6 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.

    Migrate Account

    During a database migration, accounts need to be migrated separately.

    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.
    • No

      During migration, accounts, permissions, and passwords are not migrated.

    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.

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

  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 8 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.