Migrating a database to Yandex MPP Analytics for PostgreSQL

You can migrate your database from a third-party Greenplum® or PostgreSQL cluster to Yandex MPP Analytics for PostgreSQL using Yandex Data Transfer. This method enables you to:

• Migrate the database without interrupting user service.
• Migrate from older Greenplum® versions to newer versions.
• Eliminate the need for an intermediate VM or public internet access to your Managed Service for PostgreSQL target cluster.

For more information, see Problems addressed by Yandex Data Transfer.

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 resourcesRequired paid resources

• 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 startedGetting started

Create a Greenplum® target cluster whose computing and storage capacity match those of the source database environment.

The source and target database names must be the same.

Transferring dataTransferring data

1. Prepare the source cluster:

   • Greenplum®
   • PostgreSQL

2. Prepare the target cluster.

3. Create a source endpoint with the following settings:

   • Database type: Greenplum or PostgreSQL

   • Endpoint parameters → Connection settings: Custom installation

     Configure the source cluster connection settings.

4. Create a target endpoint with the following settings:

   • Database type: Greenplum

   • Endpoint parameters → Connection settings: Managed Service for Greenplum cluster

     Specify the target cluster ID.

5. Create a Snapshot-type transfer configured to use the new endpoints.

6. Activate the transfer.

7. Wait for the transfer status to change to Completed.

   For more information about transfer statuses, see Transfer lifecycle.

8. Switch the source cluster to read-only mode and move the workload to the target cluster.

9. To reduce the consumption of resources you do not need, delete them:

   1. Delete the completed transfer.
   2. Delete the source and target endpoints.

Greenplum® and Greenplum Database® are registered trademarks or trademarks of Broadcom Inc. in the United States and/or other countries.