Help Center/ TaurusDB/ Best Practices/ From Other Cloud MySQL to GaussDB(for MySQL)/ Creating a DRS Migration Task
Updated on 2024-09-05 GMT+08:00
View PDF
Share

Creating a DRS Migration Task

This section describes how to create a DRS instance and migrate data from a MySQL database on other clouds to a GaussDB(for MySQL) instance.

Pre-migration Check

Before creating a migration task, check the migration environment.

This section describes how to migrate data from a MySQL database to GaussDB(for MySQL). For details, see Before You Start.

Creating a Migration Task

  1. Log in to the management console.
  2. Click in the upper left corner of the management console and select region AP-Singapore.
  3. Under the service list, choose Databases > Data Replication Service.
  4. In the upper right corner, click Create Migration Task.
  5. Configure parameters as needed.

    1. Specify a migration task name.

    2. Configure replication instance details as needed.

      Select the GaussDB(for MySQL) instance created in Creating a GaussDB(for MySQL) Instance as the destination database.

  6. Click Create Now.

    It takes about 5 to 10 minutes to create a replication instance.

  7. Configure a whitelist for the source database to manage network access.

    Add the EIP of the DRS replication instance to the whitelist of the source MySQL database to ensure that the source database can communicate with the DRS instance.

    The method for configuring the whitelist depends on the cloud database vendor. For details, see the official documents of the corresponding cloud database vendor.

  8. Configure source and destination database information.

    1. Configure the source database information and click Test Connection. If a successful test message is returned, login to the destination is successful.
    2. Configure destination database information and click Test Connection. If a successful test message is returned, login to the destination is successful.

  9. Click Next.
  10. On the Set Task page, select migration accounts and objects.

    • Select No for Migrate Account.
    • Select All for Migrate Object.

  11. Click Next. 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.
    • If all check items are successful, click Next.

  12. Click Submit.

    Return to the Online Migration Management page and check the migration task status.

    It takes several minutes to complete.

    If the status changes to Completed, the migration task has been created.

    • Currently, MySQL to GaussDB(for MySQL) migration supports two modes: full migration and full+incremental migration.
    • If you create a full migration task, the task automatically stops after the full data is migrated to the destination.
    • If you create a full+incremental migration task, a full migration is executed first. After the full migration is complete, an incremental migration starts.
    • During the incremental migration, data is continuously migrated so the task will not automatically stop.