Migrating a database from Managed Service for PostgreSQL to Object Storage
You can migrate a database from Yandex Managed Service for PostgreSQL to Yandex Object Storage using Yandex Data Transfer. Proceed as follows:
If you no longer need the resources you created, delete them.
Required paid resources
- Managed Service for PostgreSQL cluster: Computing resources allocated to hosts, storage and backup size (see Managed Service for PostgreSQL pricing).
- Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
- Object Storage bucket: Use of storage, data operations (see Object Storage pricing).
Getting started
Set up the infrastructure:
-
Create a source Managed Service for PostgreSQL cluster using any suitable configuration with publicly accessible hosts. Specify the following settings:
- DB name:
db1. - Username:
pg-user. - Password:
<source_password>.
- DB name:
-
If using security groups in your cluster, make sure they are configured correctly and allow connecting to the cluster.
-
Create a service account named
storage-sawith thestorage.uploaderrole. The transfer will use it to access the bucket.
-
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 postgresql-to-objstorage.tf
configuration file to your current working directory.This file describes:
- Network.
- Subnet.
- Security group required for cluster access.
- Source Managed Service for PostgreSQL cluster.
- Service account for creating and accessing the bucket.
- Target Object Storage bucket.
- Source endpoint.
- Transfer.
-
In the
postgresql-to-objstorage.tffile, specify the following:- PostgreSQL user password.
- Bucket name consistent with the naming conventions.
-
Validate your Terraform configuration files using this command:
terraform validateTerraform will display any configuration errors detected in your 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
. -
Set up your transfer
-
Connect to the Managed Service for PostgreSQL cluster. In the
db1database, create a table namedx_taband populate it with data:CREATE TABLE x_tab ( id NUMERIC PRIMARY KEY, name CHAR(5) ); INSERT INTO x_tab (id, name) VALUES (40, 'User1'), (41, 'User2'), (42, 'User3'), (43, 'User4'), (44, 'User5'); -
Create an
Object Storage-type target endpoint with the following settings:-
Bucket:
<name_of_previously_created_bucket> -
Service account:
storage-sa -
Serialization format:
CSV -
Encoding format:
UNCOMPRESSED -
Folder name:
from_PostgreSQL
-
-
Create a source endpoint and set up the transfer.
-
Create a
PostgreSQL-type source endpoint and configure it using the following settings:- Installation type:
Managed Service for PostgreSQL cluster. - Managed Service for PostgreSQL cluster:
<source_PostgreSQL_cluster_name>from the drop-down list. - Database:
db1. - User:
pg-user. - Password:
<user_password>.
- Installation type:
-
Create a Snapshot-type transfer configured to use the new endpoints.
-
In the
postgresql-to-objstorage.tffile, specify these variables:objstorage_endpoint_id: Target endpoint ID.transfer_enabled:1to create a transfer.
-
Validate your Terraform configuration files using this command:
terraform validateTerraform will display any configuration errors detected in your 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.
-
-
Activate the transfer
-
Activate the transfer and wait for its status to change to Completed.
-
Verify that the table
public_x_tab.csv, containing data fromx_tab, has appeared in the Object Storage bucket.
Verify that the copy operation works upon reactivation
-
Connect to the Managed Service for PostgreSQL cluster and perform the following operations on the table
x_tab: delete the row with ID =41and update the row with ID =42:DELETE FROM x_tab WHERE id = 41; UPDATE x_tab SET name = 'Key3' WHERE id = 42; -
Reactivate the transfer and wait for its status to change to Completed.
-
Verify that the changes have been propagated to the target
public_x_tab.csvtable.
Delete the resources you created
To reduce the consumption of resources you do not need, delete them:
-
Make sure the transfer status is Completed.
-
Delete other resources using the same method used for their creation:
ManuallyTerraform-
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.
-
-