Migrating data from MySQL® to YDB

Data Transfer enables you to transfer data from a Managed Service for MySQL® source cluster to Managed Service for YDB.

To transfer data:

1. Prepare the source cluster.
2. Set up and activate the transfer.
3. Test your transfer.

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

Required paid resourcesRequired paid resources

The support cost for this solution includes:

• Managed Service for MySQL® cluster fee: Covers the use of computational resources allocated to hosts and disk storage (see Managed Service for MySQL® pricing).

• Fee per transfer: Based on computational resource usage and the number of data rows transferred (see Data Transfer pricing).

• Fee for public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).

• Managed Service for YDB database fee. The charge depends on the usage mode:

  • For the serverless mode, you pay for data operations and the amount of stored data.
  • For the dedicated instance mode, you pay for the use of computing resources, dedicated DBs, and disk space.

  Learn more about the Managed Service for YDB pricing plans.

Set up the infrastructureSet up the infrastructure

Prepare the source clusterPrepare the source cluster

1. If you created the infrastructure manually, prepare the source cluster.

2. Connect to the Managed Service for MySQL® source cluster.

3. Add test data to the database. As an example, we will use a simple table with information transmitted by car sensors.

   Create a table:

   CREATE TABLE measurements (
       device_id varchar(200) NOT NULL,
       datetime timestamp NOT NULL,
       latitude real NOT NULL,
       longitude real NOT NULL,
       altitude real NOT NULL,
       speed real NOT NULL,
       battery_voltage real,
       cabin_temperature real NOT NULL,
       fuel_level real,
       PRIMARY KEY (device_id)
   );
   

   Populate the table with data:

   INSERT INTO measurements VALUES
       ('iv9a94th6rzt********', '2022-06-05 17:27:00', 55.70329032, 37.65472196,  427.5,    0, 23.5, 17, NULL),
       ('rhibbh3y08qm********', '2022-06-06 09:49:54', 55.71294467, 37.66542005, 429.13, 55.5, NULL, 18, 32);
   

Set up and activate the transferSet up and activate the transfer

1. Create a target endpoint:

   • Database type: YDB.

   • Endpoint parameters:

     • Connection settings → Database: Select the Managed Service for YDB database from the list.

     • Service account ID: Select or create a service account with the ydb.editor role.

2. Create a source endpoint and transfer:

   Manually

   Terraform

   1. Create a source endpoint:

      • Database type: MySQL®

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

        Select your source cluster from the list and specify its connection settings.

   2. Create the Snapshot and replication type transfer and configure it to use the previously created endpoints.

   3. Activate the transfer.

   1. In the data-transfer-mmy-ydb.tf file, uncomment the following:

      • target_endpoint_id variable. Also, set it to the value of the endpoint ID for the target created in the previous step.
      • yandex_datatransfer_endpoint and yandex_datatransfer_transfer resources.

   2. Validate your Terraform configuration files using this command:

      terraform validate
      

      Terraform will display any configuration errors detected in your files.

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

      The transfer will activate automatically upon creation.

Test the transferTest the transfer

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

2. Verify that the data has been transferred from the source Managed Service for MySQL® cluster to the Managed Service for YDB database:

   Management console

   CLI

   1. In the management console, select the folder with the DB you need.
   2. From the list of services, select Managed Service for YDB.
   3. Select the database from the list.
   4. Navigate to the Navigation tab.
   5. Check that the Managed Service for YDB database contains the <source_cluster_DB_name>_measurements table with test data.

   1. Connect to the Managed Service for YDB database.

   2. Check that the database contains the <source_cluster_DB_name>_measurements table with test data:

      SELECT *
      FROM <source_cluster_DB_name>_measurements;
      

3. Connect to the Managed Service for MySQL® source cluster and populate the measurements table with data:

   INSERT INTO measurements VALUES
       ('iv7b74th678t********', '2020-06-08 17:45:00', 53.70987913, 36.62549834, 378.0, 20.5, 5.3, 20, NULL);
   

4. Check that the Managed Service for YDB database shows information about the added row:

   Management console

   CLI

   1. In the management console, select the folder with the DB you need.
   2. From the list of services, select Managed Service for YDB.
   3. Select the database from the list.
   4. Navigate to the Navigation tab.
   5. Check that new data has been added to the <source_cluster_DB_name>_measurements table.

   1. Connect to the Managed Service for YDB database.

   2. Check that new data has been added to the <source_cluster_DB_name>_measurements table:

      SELECT *
      FROM <source_cluster_DB_name>_measurements;
      

Delete the resources you createdDelete the resources you created

Some resources incur charges. To avoid unnecessary charges, delete the resources you no longer need:

1. Delete the transfer.

2. Delete the target endpoint.

3. If you created a service account when creating the target endpoint, delete it.

Delete other resources using the method matching their creation method: