Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Data Transfer
  • Available transfers
  • Getting started
    • All tutorials
      • MySQL® to YDB
      • PostgreSQL to YDB
      • MySQL® to PostgreSQL
      • PostgreSQL to MySQL®
      • MySQL® to Greenplum®
      • Elasticsearch to OpenSearch
      • OpenSearch to YDB
      • OpenSearch in Greenplum®
      • PostgreSQL in OpenSearch
  • Troubleshooting
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials

In this article:

  • Required paid resources
  • Getting started
  • Prepare the test data
  • Create a database in the target cluster
  • Prepare and activate your transfer
  • Test the transfer
  • Test the copy process
  • Test the replication process
  • Delete the resources you created
  1. Tutorials
  2. Migration with data storage type changed
  3. MySQL® to Greenplum®

Migrating data from Yandex Managed Service for MySQL® to Yandex Managed Service for Greenplum®

Written by
Yandex Cloud
Updated at May 5, 2025
  • Required paid resources
  • Getting started
  • Prepare the test data
  • Create a database in the target cluster
  • Prepare and activate your transfer
  • Test the transfer
    • Test the copy process
    • Test the replication process
  • Delete the resources you created

You can set up data transfer from Managed Service for MySQL® to Managed Service for Greenplum® databases using Data Transfer. To do this:

  1. Prepare the test data.
  2. Create a database in the target cluster.
  3. Prepare and activate your transfer.
  4. Test the transfer.

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

Required paid resourcesRequired paid resources

The support cost includes:

  • Managed Service for MySQL® cluster fee: Using computing resources allocated to hosts and disk space (see Managed Service for MySQL® pricing).
  • Managed Service for Greenplum® cluster fee: Using computing resources allocated to hosts and disk space (see Managed Service for Greenplum® pricing).
  • Fee for using public IP addresses for cluster hosts (see Virtual Private Cloud pricing).
  • Per-transfer fee: Using computing resources and the number of transferred data rows (see Data Transfer pricing).

Getting startedGetting started

Set up your infrastructure:

Manually
Using Terraform
  1. 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>.
  2. Grant the REPLICATION CLIENT and REPLICATION SLAVE administrative privileges to mmy_user.

    For more information about administrative privileges, see the settings description.

  3. In the same availability zone, create a Managed Service for Greenplum® target cluster in any suitable configuration with publicly available hosts and the following settings:

    • Username: mgp_user.
    • Password: <target_password>.
    • Access from Data Transfer: Enabled.
  4. Make sure that the cluster security groups are set up correctly and allow connecting to them:

    • Managed Service for MySQL®.
    • Managed Service for Greenplum®.
  1. If you do not have Terraform yet, install it.

  2. Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.

  3. Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it.

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

  5. Download the mmy-to-mgp.tf configuration file to the same working directory.

    This file describes:

    • Networks and subnets for hosting the clusters.
    • Security groups for making cluster connections.
    • Managed Service for MySQL® source cluster.
    • Managed Service for Greenplum® target cluster.
    • Source endpoint.
    • Transfer.
  6. Specify the following in the mmy-to-mgp.tf file:

    • MySQL® and Greenplum® versions
    • MySQL® and Greenplum® user passwords
  7. 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.

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

    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 dataPrepare the test data

  1. Connect to the mmy_db database in the Managed Service for MySQL® source cluster.

  2. Create a simple table named table1:

    CREATE TABLE table1 (
    id int NOT NULL,
    name varchar (10),
    PRIMARY KEY (id)
    );
    
  3. Populate the table with data:

    INSERT INTO table1 VALUES
    (1, 'Name1'),
    (2, 'Name2'),
    (3, 'Name3');
    

Create a database in the target clusterCreate a database in the target cluster

  1. Connect to the auxiliary postgres database in the Managed Service for Greenplum® target cluster as mgp_user.

  2. Create a database named mgp_db:

    CREATE DATABASE mgp_db;
    

Prepare and activate your transferPrepare and activate your transfer

  1. Create a target endpoint of the Greenplum® type and specify the cluster connection settings in it:

    • Connection type: Managed Service for Greenplum cluster.
    • Managed Service for Greenplum cluster: <name_of_Greenplum®_target_cluster> from the drop-down list.
    • Database: mgp_db.
    • User: mgp_user.
    • Password: <user_password>.
  2. Create a source endpoint and transfer.

    Manually
    Using Terraform
    1. Create a source endpoint of the MySQL® type and specify these cluster connection settings in it:

      • Connection type: Managed Service for MySQL cluster.
      • Managed Service for MySQL cluster: <name_of_MySQL®_source_cluster> from the drop-down list.
      • Database: mmy_db.
      • User: mmy_user.
      • Password: <user_password>.
    2. Create a transfer of the Snapshot and replication type that will use the created endpoints.

    3. Activate the transfer and wait for its status to change to Replicating.

    1. In the mmy-to-mgp.tf file, specify the following settings:

      • target_endpoint_id: Target endpoint ID.
      • transfer_enabled: 1 to create a transfer.
    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:

      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.

    4. The transfer will be activated automatically. Wait for its status to change to Replicating.

Test the transferTest the transfer

Check the transfer performance by testing the copy and replication processes.

Test the copy processTest the copy process

  1. Connect to mgp_db in the Managed Service for Greenplum® target cluster.

  2. Run this request:

    SELECT * FROM mmy_db.table1;
    

Test the replication processTest the replication process

  1. Connect to the mmy_db database in the Managed Service for MySQL® source cluster.

  2. Populate the table1 table with data:

    INSERT INTO table1 VALUES
    (4, 'Name4');
    
  3. Make sure the new row has been added to the target database:

    1. Connect to mgp_db in the Managed Service for Greenplum® target cluster.

    2. Run this request:

      SELECT * FROM mmy_db.table1;
      

Delete the resources you createdDelete the resources you created

Note

Before deleting the resources you created, deactivate the transfer.

Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:

Manually
Using Terraform
  • Transfer
  • Endpoints
  • Managed Service for MySQL® cluster
  • Managed Service for Greenplum® cluster
  1. 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.

  2. Delete resources:

    1. Run this command:

      terraform destroy
      
    2. Confirm deleting the resources and wait for the operation to complete.

    All the resources described in the Terraform manifests will be deleted.

Was the article helpful?

Previous
PostgreSQL to MySQL®
Next
Elasticsearch to OpenSearch
© 2025 Direct Cursus Technology L.L.C.