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

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. Prepare and activate the transfer.
3. Test the transfer.

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

Getting startedGetting started

Prepare 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 the 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 previously created Object Storage bucket.

Prepare and activate the transferPrepare and activate the transfer

1. Create a source endpoint with the following settings:

   • Database type: Object Storage.

   • Bucket: Bucket name in Object Storage.

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

   • Secret Access Key: Private part of the service account static 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 mark (;).

   • Table: measurements.

   • Add system columns: Disable the 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

   Leave the default values for the other parameters.

2. Create an endpoint for the target and the 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 a transfer of the Snapshot and replication type that will use the created endpoints.

   3. Activate your transfer.

   1. In the data-transfer-objs-mmy.tf file, specify the following variables:

      • source_endpoint_id: ID of the source endpoint.
      • transfer_enabled: Set to 1 to enable transfer creation.

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

   3. Create the required infrastructure for the transfer:

      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.

      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 Managed Service for MySQL® target cluster database.

3. To make sure the data was successfully transferred, run the following query:

   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 is added to the db1.measurements table of the MySQL® target database.

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:

1. Delete the transfer.
2. Delete the target endpoint.

Delete the other resources depending on how they were created: