Migrating data from Managed Service for MySQL® to Yandex MPP Analytics for PostgreSQL using Yandex Data Transfer
You can set up a data transfer from a Managed Service for MySQL® database to a Yandex MPP Analytics for PostgreSQL one using Data Transfer. Proceed as follows:
- Prepare your test data.
- Create a database in the target cluster.
- Set up and activate the transfer.
- Test your transfer.
If you no longer need the resources you created, delete them.
Required paid resources
- Managed Service for MySQL® cluster: Computing resources allocated to hosts, storage and backup size (see Managed Service for MySQL® pricing).
- Yandex MPP Analytics for PostgreSQL cluster: Computing resources allocated to hosts, storage and backup size (see Yandex MPP Analytics for PostgreSQL pricing).
- Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
Getting started
Set up your infrastructure:
-
Create a Managed Service for MySQL® source cluster in any availability zone with publicly available hosts in any suitable configuration and the following settings:
- DB name:
mmy_db. - Username:
mmy_user. - Password:
<source_password>.
- DB name:
-
Grant the
REPLICATION CLIENTandREPLICATION SLAVEadministrative privileges tommy_user.For more information about administrative privileges, see the settings description.
-
In the same availability zone, create a Greenplum® target cluster of any suitable configuration with publicly available hosts and the following settings:
- Username:
mgp_user. - Password:
<target_password>. - Access from Data Transfer: Enabled.
- Username:
-
Make sure the cluster security groups are configured correctly and allow inbound cluster connections:
-
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 mmy-to-mgp.tf
configuration file to the same working directory.This file describes:
- Networks and subnets that will host your clusters.
- Security groups for cluster access.
- Managed Service for MySQL® source cluster.
- Greenplum® target cluster in Yandex MPP Analytics for PostgreSQL.
- Source endpoint.
- Transfer.
-
In the
mmy-to-mgp.tffile, specify the following:- MySQL® and Greenplum® versions.
- MySQL® and Greenplum® user passwords.
-
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 your test data
-
Connect to the
mmy_dbdatabase in the Managed Service for MySQL® source cluster. -
Create a simple table named
table1:CREATE TABLE table1 ( id int NOT NULL, name varchar (10), PRIMARY KEY (id) ); -
Populate the table with data:
INSERT INTO table1 VALUES (1, 'Name1'), (2, 'Name2'), (3, 'Name3');
Create a database in the target cluster
-
Connect to the
postgressystem database in the Greenplum® target cluster asmgp_user. -
Create a database named
mgp_db:CREATE DATABASE mgp_db;
Set up and activate the transfer
-
Create a
Greenplum®target endpoint with these cluster connection settings:- Connection type:
Managed Service for Greenplum cluster. - Managed Service for Greenplum cluster:
<Greenplum®_target_cluster_name>from the drop-down list. - Database:
mgp_db. - User:
mgp_user. - Password:
<user_password>.
- Connection type:
-
Create a source endpoint and transfer:
Manually-
Create a
MySQL®source endpoint with these cluster connection settings:- Connection type:
Managed Service for MySQL cluster. - Managed Service for MySQL cluster:
<MySQL®_source_cluster_name>from the drop-down list. - Database:
mmy_db. - User:
mmy_user. - Password:
<user_password>.
- Connection type:
-
Create a transfer of the Snapshot and replication-type that will use the endpoints you created.
-
Activate the transfer and wait for its status to change to Replicating.
-
Test your transfer
To make sure the transfer works correctly, test the copy and replication processes.
Test the copy operation
-
Connect to the
mgp_dbdatabase in the Greenplum® target cluster. -
Run this query:
SELECT * FROM mmy_db.table1;
Test the replication process
-
Connect to the
mmy_dbdatabase in the Managed Service for MySQL® source cluster. -
Populate
table1with data:INSERT INTO table1 VALUES (4, 'Name4'); -
Make sure the target database contains the row you added:
-
Connect to the
mgp_dbdatabase in the Greenplum® target cluster. -
Run this query:
SELECT * FROM mmy_db.table1;
-
Delete the resources you created
Note
Before deleting the resources, deactivate the transfer.
Some resources are not free of charge. Delete the resources you no longer need to avoid paying for them:
-
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.
-