Migrating data from a third-party Greenplum® or PostgreSQL cluster to Yandex Managed Service for Greenplum® using Yandex Data Transfer
You can migrate your database from a third-party Greenplum® or PostgreSQL cluster to Managed Service for Greenplum® using Yandex Data Transfer. This method allows you to:
- Migrate the database without interrupting user service.
- Migrate from older Greenplum® versions to newer versions.
- Go without creating an intermediate VM or granting online access to your Managed Service for PostgreSQL target cluster.
To learn more, see Problems addressed by Yandex Data Transfer.
Note
Data Transfer enables you to transfer the state of the source database to the Managed Service for Greenplum® target without keeping it up-to-date (the Snapshot transfer type). Changes occurring on the source after the transfer is completed will not be transferred.
To migrate your database, you need to directly transfer the data, acquire a write lock for the old database, and switch over the load to the database cluster in Yandex Cloud.
Required paid resources
The support cost includes:
- 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 if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
Getting started
Create a Managed Service for Greenplum® target cluster with the computing capacity and storage size appropriate for the environment where the migrated database is deployed.
The database name in the target cluster must be the same as the source database name.
Transferring data
-
Prepare the source cluster:
-
Create a source endpoint with the following parameters:
-
Database type:
Greenplum
orPostgreSQL
-
Endpoint parameters → Connection settings:
Custom installation
Specify the parameters for connecting to the source cluster.
-
-
Create a target endpoint with the following parameters:
-
Database type:
Greenplum
-
Endpoint parameters → Connection settings:
Managed Service for Greenplum cluster
Specify the ID of the target cluster.
-
-
Create a transfer of the Snapshot type that will use the created endpoints.
-
Wait for the transfer status to change to Completed.
For more information about transfer statuses, see Transfer lifecycle.
-
Switch the source cluster to
read-only
mode and transfer the load to the target cluster. -
Delete the endpoints for both the source and target.