Migrating to a third-party MySQL® cluster

To migrate a database deployed in a Yandex Managed Service for MySQL® cluster to a third-party MySQL® cluster:

1. Transfer the data.
2. Disable data writes to the source database.
3. Switch all traffic to the third-party cluster.

You can migrate your databases from one MySQL® version to another, e.g., from MySQL® 5.7 to MySQL® 8. Note that the third-party cluster must run a major MySQL® version not lower than that on your Yandex Managed Service for MySQL® cluster.

Required paid resourcesRequired paid resources

The migration infrastructure cost includes a fee for each transfer: Use of computing resources and number transferred data rows (see Data Transfer pricing).

Getting startedGetting started

Create a MySQL® cluster with any suitable configuration. For this operation, the following requirements apply:

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

  Data transfer with a major MySQL® version upgrade is possible but not guaranteed. For more information, see this MySQL® article.

  Migration to an earlier MySQL® version is not supported.

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

Transferring dataTransferring data

1. Set up the source cluster database.

2. Set up the target cluster database.

3. Create endpoints and a transfer:

   Manually

   Terraform

   1. Create a source endpoint:

      • Database type: MySQL.

      • Connection settings: Managed Service for MySQL cluster.

        Specify the source cluster ID.

   2. Create a target endpoint:

      • Database type: MySQL.

      • Connection settings: Custom installation.

        Configure the target cluster connection settings.

   3. Create a Snapshot and increment-type transfer configured to use the new endpoints.

   4. Activate the transfer.

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

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

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

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

   5. Download the data-transfer-mmy-mysql.tf file with the transfer and endpoint configuration file to the same working directory.

   6. Specify the following in the configuration file:

      • Source endpoint parameters.
      • Target endpoint parameters.

   7. Validate your Terraform configuration files using this command:

      terraform validate
      

      Terraform will display any configuration errors detected in your files.

   8. Create the required infrastructure:

      1. Run this command to view the planned changes:

         terraform plan
         

         If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

      2. If everything looks correct, apply the changes:

         1. Run this command:

            terraform apply
            

         2. Confirm updating the 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.

      The transfer will activate automatically upon creation.

   Warning

   Avoid changing the data schema in either the source or target cluster while the transfer is in progress. For more information, see Working with databases during transfer.

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

5. Switch the source cluster to "read-only" mode and move the workload to the target cluster.

6. On the transfer monitoring page, wait until the Maximum data transfer delay value drops to zero. This indicates that the target cluster now contains all changes made in the source cluster after the data copy completed.

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

   For more information about transfer statuses, see Transfer lifecycle.

8. To reduce the consumption of resources you do not need, delete them:

   Manually

   Terraform

   1. Ensure the transfer is stopped, then delete it.
   2. Delete the source and target endpoints.

   1. In the terminal window, go to the directory containing the infrastructure plan.

      Warning

      Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

   2. Delete resources:

      1. Run this command:

         terraform destroy
         

      2. Confirm deleting the resources and wait for the operation to complete.

      All the resources described in the Terraform manifests will be deleted.

See alsoSee also

For other migration methods, see this Yandex Managed Service for MySQL® tutorial.