Migrating data from Object Storage to Yandex Managed Service for MySQL® using Yandex Data Transfer

With Data Transfer, you can transfer data from an Object Storage object storage to a Managed Service for MySQL® target cluster.

To transfer data:

1. Prepare the test data.
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:

• Fee for an Object Storage bucket: Covers data storage and bucket operations (see Object Storage pricing).
• Managed Service for MySQL® cluster fee: Using computing resources allocated to hosts and disk space (see Managed Service for MySQL® pricing).
• Fee for public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
• Fee per transfer: Based on computational resource usage and the number of data rows transferred (see Data Transfer pricing).

Getting startedGetting started

Set up the infrastructure:

Prepare the test dataPrepare the test data

1. Create a data.csv text file on the running instance and fill it with test data. As an example, we will use readings returned by car sensors:

   1;99101;2022-06-05 17:27:00;55.70329032;37.65472196;427.5;52.3;23.5;17.;52.
   2;95106;2022-06-06 09:49:54;55.71294467;37.66542005;429.13;55.5;21.;18.;32.
   3;117890;2023-06-07 06:21:29;55.71294467;37.66542005;429.13;56.2;20.;18.7;45.
   4;99101;2022-06-07 08:15:32;55.29194467;37.66542005;429.13;59.1;21.;18.;20.
   

2. Upload the file to the Object Storage bucket you created earlier.

Prepare and activate your transferPrepare and activate your transfer

1. Create a source endpoint with the following settings:

   • Database type: Object Storage.

   • Bucket: Object Storage bucket name.

   • Access Key ID: Public component of the service account’s static key. If you created your infrastructure using Terraform, copy the key value from the Yandex Lockbox secret.

   • Secret Access Key: Service account’s secret access key. If you created your infrastructure using Terraform, copy the key value from the Yandex Lockbox secret.

   • Endpoint: https://storage.yandexcloud.net.

   • Region: ru-central1.

   • Data format: CSV.

   • Delimiter: Semicolon (;).

   • Table: measurements.

   • Add system columns: Disable this option.

   • Result table schema: Select Manual and specify field names and data types:

     • id: INT64, Key property

     • device_id: INT32

     • datetime: DATETIME

       Note

       The target endpoint writes DATETIME type data in the UTC+0 time zone.

     • latitude: DOUBLE

     • longitude: DOUBLE

     • altitude: DOUBLE

     • speed: DOUBLE

     • battery_voltage: DOUBLE

     • cabin_temperature: DOUBLE

     • fuel_level: DOUBLE

   Keep the default values for all other settings.

2. Create an endpoint for the target and transfer:

   Manually

   Terraform

   1. Create a target endpoint:

      • Database type: MySQL

      • Endpoint parameters:

        • Connection settings:

          • Connection type: Managed Service for MySQL cluster

            Select a 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-objs-mmy.tf file, specify these variables:

      • source_endpoint_id: ID of the source endpoint.
      • transfer_enabled: 1 to create a transfer.

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

      terraform validate
      

      Terraform will display any configuration errors detected in your files.

   3. Create the required infrastructure for the transfer:

      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.

      Once created, your transfer will be activated automatically.

Test the transferTest the transfer

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

2. Connect to the target Managed Service for MySQL® cluster’s database.

3. To make sure the data was successfully transferred, run this request:

   SELECT * FROM db1.measurements;
   

   Response example

    id | device_id |     datetime        |  latitude | longitude | altitude | speed | battery_voltage | cabin_temperature | fuel_level
   ----------------+---------------------+-----------+-----------+----------+-------+-----------------+-------------------+----------+
     1 |     99101 | 2022-06-05T17:27:00 | 55.703289 |  37.66542 |   427.50 | 52.29 |            23.5 |              17.0 |     52.0 |
     2 |     95106 | 2022-06-06T09:49:54 | 55.712944 |  37.66542 |   429.13 | 55.50 |            21.0 |              18.0 |     32.0 |
     3 |    117890 | 2023-06-07T06:21:29 | 55.712944 |  37.66542 |   429.13 | 56.20 |            20.0 |              18.7 |     45.0 |
     4 |     99101 | 2022-06-05 17:27:00 | 55.291944 |  37.66542 |   429.13 | 59.09 |            21.0 |              18.0 |     20.0 |
   

4. Create the data2.csv text file containing new data:

   7;95106;2022-06-07 09:54:32;47.71294467;37.66542005;429.13;62.2;21.;20.4;27.
   9;117890;2022-06-07 11:56:27;52.71294467;37.66542005;429.13;65.5;19.;19.;38.
   10;117890;2022-06-07 12:36:27;57.71294467;37.66542005;429.13;72.1;19.;20.;25.
   11;99101;2022-06-07 15:22:27;59.71294467;37.66542005;429.13;35.5;19.;18.;12.
   

5. Upload the file to the Object Storage bucket for transfer.

6. Make sure the new data has been added to the db1.measurements table of the MySQL® target database.

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.

Delete other resources using the method matching their creation method: