Migrating data from Yandex Object Storage to Yandex Managed Service for MySQL®
Note
With Data Transfer, you can transfer data from an Object Storage object storage to a Managed Service for MySQL® target cluster.
To transfer data:
If you no longer need the resources you created, delete them.
Required paid resources
- Object Storage bucket: use of storage, data operations (see Object Storage pricing).
- Managed Service for MySQL® cluster: computing resources allocated to hosts, size of storage and backups (see Managed Service for MySQL® pricing).
- Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
- Each transfer: use of computing resources and number of transferred data rows (see Data Transfer pricing).
Getting started
Set up the infrastructure:
-
Create a service account named
storage-viewerwith thestorage.viewerrole. The transfer will use it to access the bucket. -
Create a static access key for the
storage-viewerservice account. -
Create a target Managed Service for MySQL® cluster with the following settings:
- DB name:
db1 - Username:
mmy-user - Password:
<user_password>
- DB name:
-
Assign the MySQL® user the
ALL_PRIVILEGESrole for the target database.
-
If you do not have Terraform yet, install it.
-
Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.
-
Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it
. -
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.
-
Download the data-transfer-objs-mmy.tf
configuration file to the same working directory.This file describes:
- Network.
- Subnet.
- Security group and the rule required to connect to a Managed Service for MySQL® cluster.
- Service account for creating and accessing the bucket
- Yandex Lockbox secret for the service account static key required to configure the source endpoint.
- Source Object Storage bucket.
- Target Managed Service for MySQL® cluster.
- Target endpoint.
- Transfer.
-
In the
data-transfer-objs-mmy.tffile, specify the following:folder_id: ID of the folder to create the resources in.bucket_name: Bucket name consistent with the naming conventions.mmy_password: MySQL® user password.
-
Make sure the Terraform configuration files are correct using this command:
terraform validateTerraform will show any errors found in your configuration files.
-
Create the required infrastructure:
-
Run this command to view the planned changes:
terraform planIf 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.
-
If everything looks correct, apply the changes:
-
Run this command:
terraform apply -
Confirm updating the resources.
-
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
. -
Prepare the test data
-
Create a
data.csvtext 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. -
Upload the file to the Object Storage bucket you created earlier.
Prepare and activate your transfer
-
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
Manualand specify field names and data types:-
id:INT64, Key property -
device_id:INT32 -
datetime:DATETIMENote
The target endpoint writes
DATETIMEtype 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.
-
-
Create an endpoint for the target and transfer:
ManuallyTerraform-
-
Database type:
MySQL -
Endpoint parameters:
- Connection settings:
-
Connection type:
Managed Service for MySQL clusterSelect a source cluster from the list and specify its connection settings.
-
- Connection settings:
-
-
Create a transfer of the Snapshot and replication type that will use the new endpoints.
-
Activate the transfer.
-
In the
data-transfer-objs-mmy.tffile, specify the following variables:source_endpoint_id: ID of the source endpoint.transfer_enabled: Set to1to create a transfer.
-
Make sure the Terraform configuration files are correct using this command:
terraform validateTerraform will show any errors found in your configuration files.
-
Create the required infrastructure for the transfer:
-
Run this command to view the planned changes:
terraform planIf 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.
-
If everything looks correct, apply the changes:
-
Run this command:
terraform apply -
Confirm updating the resources.
-
Wait for the operation to complete.
-
Once created, your transfer will be activated automatically.
-
-
Test the transfer
-
Wait for the transfer status to change to Replicating.
-
Connect to the target Managed Service for MySQL® cluster’s database.
-
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 | -
Create the
data2.csvtext 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. -
Upload the file to the Object Storage bucket for transfer.
-
Make sure the new data has been added to the
db1.measurementstable of the MySQL® target database.
Delete the resources you created
Note
Before deleting the resources, deactivate the transfer.
Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:
Delete the other resources depending on how you created them:
-
If you have created a service account when creating the target endpoint, delete it.
-
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.
-
Delete resources:
-
Run this command:
terraform destroy -
Confirm deleting the resources and wait for the operation to complete.
All the resources described in the Terraform manifests will be deleted.
-