Migrating MySQL® clusters

With Data Transfer, you can transfer data from a third-party source cluster to a Managed Service for MySQL® target cluster.

Thus, you can migrate the entire database without interrupting user service. To use it, allow connections to the source cluster from the internet.

To transfer a database from MySQL® to Managed Service for MySQL®:

1. Start data transfer.
2. Finish data transfer.

If you no longer need the resources you created, delete them.

Start data transferStart data transfer

1. Prepare the source cluster.

2. Prepare the infrastructure and start the data transfer:

   Manually

   Terraform

   1. Create a Managed Service for MySQL® target cluster in any suitable configuration. Note that:

      • The MySQL® version must be the same or higher than the version in the source cluster.

        Transferring data with MySQL® major version upgrade is possible but not guaranteed. For more information, see the MySQL® documentation.

        You cannot perform migration while downgrading MySQL® version.

      • SQL mode must be the same as in the source cluster.

   2. Prepare the target cluster.

   3. Create a source endpoint:

      • Database type: MySQL.

      • Endpoint parameters → Connection settings: Custom installation.

        Specify the parameters for connecting to the source cluster.

   4. Create a target endpoint:

      • Database type: MySQL.

      • Endpoint parameters → Connection settings: Managed Service for MySQL cluster.

        Select a target cluster from the list and specify its connection settings.

   5. Create a transfer of the Snapshot and increment type that will use the created endpoints.

   6. Activate your transfer.

      Warning

      Abstain from making any changes to the data schema in the source and target clusters when the data transfer is running. For more information, see Working with databases during transfer.

   1. Prepare the source cluster.

   2. If you do not have Terraform yet, install it.

   3. Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.

   4. Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it.

   5. Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.

   6. Download the data-transfer-mysql-mmy.tf configuration file to the same working directory.

      This file describes:

      • Network.
      • Subnet.
      • Security group and the rule required to connect to a cluster.
      • Managed Service for MySQL® target cluster.
      • Source endpoint.
      • Target endpoint.
      • Transfer.

   7. Specify in the data-transfer-mysql-mmy.tf file:

      • Source endpoint parameters.

      • Target cluster parameters also used as target endpoint parameters:

        • target_mysql_version: MySQL® version must be the same or higher than the version in the source cluster.
        • target_sql_mode: SQL mode must be the same as in the source cluster.
        • target_db_name: Database name.
        • target_user and target_password: Database owner username and password.

   8. Make sure the Terraform configuration files are correct using this command:

      terraform validate
      

      If there are any errors in the configuration files, Terraform will point them out.

   9. Create the required infrastructure:

      1. Run the command to view planned changes:

         terraform plan
         

         If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.

      2. If you are happy with the planned changes, apply them:

         1. Run the command:

            terraform apply
            

         2. Confirm the update of resources.

         3. Wait for the operation to complete.

      All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

      Once created, your transfer will be activated automatically.

Finish data transferFinish data transfer

1. Wait for the transfer status to change to Replicating.

2. Switch the source cluster to read-only and transfer the load to the target cluster.

3. On the transfer monitoring page, wait for the Maximum data transfer delay metric to decrease to zero. This means that all changes that occurred in the source cluster after data was copied are transferred to the target cluster.

4. Deactivate the transfer and wait for its status to change to Stopped.

   For more information about transfer statuses, see Transfer lifecycle.

Delete the resources you createdDelete the resources you created

Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:

For a real example of MySQL® database migration using Data Transfer, see Syncing MySQL data using Yandex Data Transfer.

See alsoSee also

For other migration methods, see the Yandex Managed Service for MySQL® documentation.