Managed Database Migration FAQ

How do I migrate my PostgreSQL databases to Selectel?

Use the instructions in Migrating PostgreSQL databases to Managed PostgreSQL.

You can also:

How do I migrate my MySQL databases to Selectel?

Use the instructions in Migrating MySQL databases to Managed MySQL semi-sync.

You can also migrate data from MySQL to Managed MySQL using Trino.

How do I migrate my ClickHouse® databases to Selectel?

Use the instructions in Migrating ClickHouse® databases to Managed ClickHouse®.

You can also migrate data from ClickHouse® to Managed ClickHouse® using Trino.

How do I migrate my Redis databases to Selectel?

Use the instructions in Migrating Redis databases to Managed Databases.

You can also migrate Redis and Valkey data to Selectel with continuous synchronization and minimal downtime using RedisShake. For more details, see the instructions in Migrate Redis data to Managed Redis.

How do I migrate my MongoDB databases to Selectel?

MongoDB is not supported in Selectel as a managed service. You can deploy MongoDB yourself on a cloud or dedicated server and migrate your data, or choose other supported managed databases in Selectel.

Can I create a PostgreSQL database in Selectel from backups stored in Yandex Cloud?

Selectel has no technical capability to retrieve your backups from Yandex Cloud.

To migrate your PostgreSQL databases to Selectel:

Restore the database from the backup in an available zone of Yandex Cloud.
Create a PostgreSQL cluster in Selectel.
Configure logical replication; for details, see the instructions in Migrating PostgreSQL databases to Managed PostgreSQL.

Can I create a MySQL database in Selectel from backups stored in Yandex Cloud?

Selectel has no technical capability to retrieve your backups from Yandex Cloud.

To migrate your MySQL databases to Selectel:

Restore the database from the backup in an available zone of Yandex Cloud.
Create a MySQL semi-sync cluster in Selectel.
Migrate data using an SQL dump; for details, see the instructions in Migrating MySQL databases to Managed MySQL semi-sync.

Can I create a fault-tolerant cluster?

You can create a fault-tolerant cluster using replication for all supported DBMSs except Kafka. The data replication type depends on the DBMS.

We recommend creating clusters in a multizone pool: nodes will be hosted in different data centers geographically distant from each other. The single point of failure for a multizone pool is an outage across all data centers hosting the cluster nodes.

For more details, see the cluster fault tolerance instructions for the relevant DBMS in the Managed Databases section of the documentation.

Can I create a PostgreSQL cluster with nodes located in different countries?

In Managed PostgreSQL, you cannot create a cluster where nodes are located in different countries. You can create a separate cluster in the required country and configure logical replication to it from the source cluster. Data will be transmitted to the new cluster from the source in real time. For more details on logical replication, see the instructions in PostgreSQL logical replication slots.

Why are nodes not distributed across different data centers when creating a fault-tolerant PostgreSQL cluster in a multizone pool?

The node placement type in a cluster depends on the multizone pool and configuration line.

If you created a cluster with replicas in the ru-6 pool, nodes will be placed sequentially across pool segments — different data centers geographically distant from each other. If the nodes are placed in the same pool segment, submit a ticket.

If you created a cluster with replicas in a HighFreq line configuration in the uz-1 pool, all nodes will be placed in the same pool segment.

For more details on node placement types, see the instructions in PostgreSQL cluster fault tolerance.

Why can't I create a database cluster?

Errors when creating a cluster can occur for various reasons, including a lack of resources in the location.

We recommend proceeding in the following order:

Check the up-to-date information on the status of Managed Databases and resource availability in locations in the control panel or on the status page.
If there is no information about an incident or resource unavailability, try creating it again. Try choosing a different configuration and replacing local disks with network drives.
If there is information about resource unavailability, try creating the cluster in a different location.
If the previous steps did not help and you could not determine the cause yourself, submit a ticket. In the ticket, specify:
- The UUID of the managed database cluster. You can copy it in the control panel: in the top menu, click Products → Managed Databases → in the cluster's menu, select Copy UUID.
- Project ID. You can copy it in the control panel: in the top menu, click IAM → Projects → in the project row, in the ID column, click ;
- the pool where the cluster was created.

How do I increase project quotas and limits?

Each project has quotas and limits set:

limits — the maximum amount of resources that can be created in a project. Limits are set automatically upon project creation and may differ by pools and pool segments;
quotas — restrictions within limits to control costs. When a project is created, quotas equal to the limits are allocated for each resource. Once resource usage reaches the quota value, you cannot create new resources.

If there are not enough quotas to create resources, you can change them yourself. The quota value cannot exceed the project limit.

If you need more quotas than defined by the project limit to create resources, increase the limits. To do this, submit a ticket and specify:

Project ID. You can copy it in the control panel: in the top menu, click IAM → Projects → in the project row, in the ID column, click ;
the pool where the limit needs to be increased;
the new limit value.

After a Selectel specialist increases the limit, change the quotas yourself in the control panel.

How is backup performed?

Backups are created automatically for all supported DBMSs except Kafka and ClickHouse®. You can restore a cluster or data from backups. All backups are stored in Selectel S3 isolated from other users. The backup retention period is 7 days.

The backup frequency depends on the selected DBMS. For more details on backups, see the backup instructions for the relevant DBMS in the Managed Databases section of the documentation.

Where are backups physically stored?

Backups are stored in Selectel S3 separately from Managed Database clusters and isolated from other users.

Backups of clusters created in Russia are geo-redundant — they are stored simultaneously in two data centers located in different regions.

Backups of clusters created in other countries are stored in the same country as the cluster.

For more details on Selectel infrastructure, see the instructions in Locations: countries, regions, availability zones, pools, and data center addresses.

Can I restore a cluster in another region?

You cannot change the location when restoring a cluster from a backup. The cluster can only be restored in the same pool where it was created.

Why can't I add an extension to a PostgreSQL database?

In Managed PostgreSQL, you can only add supported extensions. You can view the list of available extensions in the instructions in PostgreSQL extensions.

If the required extension is not in the list of available extensions, submit a ticket.

Can I get a superuser role?

No, we do not provide a superuser role for working with Managed Databases.

A superuser can fully control the database and server, such as modifying configurations, managing users, and executing critical commands. Granting this role may lead to failures, data leaks, and security breaches. If you need to perform actions with superuser privileges during migration, submit a ticket.

How do I work with Selectel Managed Databases?

You can find instructions on working with Managed Databases in the Managed Databases section of the documentation.

We also recommend taking the course on working with Managed Databases: Product Dive: Selectel Managed Databases.

ClickHouse® is a registered trademark of ClickHouse, Inc. https://clickhouse.com.