---
title: "Link a Managed Database to a dedicated server"
sidebar_label: "Link a Managed Database to a dedicated server"
sidebar_position: 4
description: "How to link a Managed Database to a dedicated server over a private network"
---
import Formbricks from '@theme/MDXComponents/Formbricks'
import Tabs from '@theme/Tabs'
import TabItem from '@theme/TabItem'
import MoreVerticalIcon from '@selectel/docux/icons/more-vertical'
import {TabItemLabel} from '@selectel/docux/components'
import CreateGlobalRouter from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/global-router/create-global-router.mdx'
import ConnectDedicatedNetworkToGlobalRouter from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/global-router/connect-dedicated-network-to-global-router.mdx'
import ConnectCloudNetworkToGlobalRouter from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/global-router/connect-cloud-network-to-global-router.mdx'
import ConfigureNetworkInterfaceOfPrivateNetwork from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/dedicated/configure-network-interface-of-private-network.mdx'
import WriteStaticRoutesDedicated from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/global-router/write-static-routes-dedicated.mdx'
# Link a Managed Database to a dedicated server
:::info
Some dedicated server configurations [Chipcore Line](/dedicated/order/dedicated-configurations.mdx#prebuilt-servers) cannot be added to a global router network because they lack a port for connection to a private network. You can check for a private network port in the [Control Panel](https://my.selectel.ru/servers/servers/) on the server page on the **Ports** tab.
:::
1. [Create a global router](#create-global-router).
2. [Connect to the global router a network and subnet linking to the dedicated server VLAN](#connect-network-and-subnet-to-router-up-to-dedicated-server-vlan).
3. [Connect to the global router a network and subnet linking to the Cloud Platform project](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
4. [Assign IP addresses from the created subnets to the dedicated server](#assign-ip-to-dedicated-server).
5. [Specify routes on the dedicated server](#write-routes-on-dedicated-server).
6. [Create a Managed Database cluster](#create-managed-database-cluster): new or from a backup of an existing Managed Database cluster.
See an [example of networking](#example-of-network-organization-between-managed-database-and-dedicated-server) between a dedicated server and a Managed Database.
## Example of networking between a Managed Database and a dedicated server \{#example-of-network-organization-between-managed-database-and-dedicated-server}
If you need to configure private connectivity between a dedicated server in the SPB-2 pool and a new Managed Database in the ru-2 pool:
1. Create a global router.
2. Connect two private subnets to the router — `192.168.0.0/29` with a gateway of `192.168.0.1` for the SPB-2 pool and `172.16.0.0/29` with a gateway of `172.16.0.1` for the ru-2 pool.
3. Assign an address from the `192.168.0.0/29` subnet to the dedicated server, for example, `192.168.0.2`.
4. Specify routes on the dedicated server in the SPB-2 pool — in the `172.16.0.0/29` subnet via the gateway `192.168.0.1`.
5. Create a new Managed Database cluster on the subnet `172.16.0.0/29`.
## 1. Create a global router \{#create-global-router}
## 2. Connect to the router a network and subnet linking to the dedicated server VLAN \{#connect-network-and-subnet-to-router-up-to-dedicated-server-vlan}
## 3. Connect to the router a network and subnet linking to the Cloud Platform project \{#connect-network-and-subnet-to-router-up-to-cloud-platform-project}
## 4. Assign an IP address to the dedicated server \{#assign-ip-to-dedicated-server}
Configure a local port on the dedicated server that is included in the global router network. Assign an IP address from the private subnet that you [connected to the global router in step 2](#connect-network-and-subnet-to-router-up-to-dedicated-server-vlan).
## 5. Specify routes on the dedicated server \{#write-routes-on-dedicated-server}
## 6. Create a Managed Database cluster \{#create-managed-database-cluster}
PostgreSQL
New
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Enter the cluster name.
4. Select a [location](/infrastructure/locations.mdx). You cannot change the location after creation.
5. Select the PostgreSQL version. You will not be able to change it after creating the cluster.
6. Select the [node configuration](/managed-databases/postgresql/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
7. For a fixed configuration, select a [configuration line](/managed-databases/postgresql/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
8. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
9. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/postgresql/network-access-control.mdx) from which access to the database cluster will be allowed.
10. Select a [connection pooler mode](/managed-databases/postgresql/connection-pooler.mdx):
* transaction — connection assigned to a client for the duration of a transaction;
* session — connection assigned while a client is connected;
* statement — transactions with multiple statements are prohibited.
11. Optional: change the [DBMS settings](/managed-databases/postgresql/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
12. Click **Create database cluster**. The cluster will be ready to work once it enters the `ACTIVE` status.
From backup
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Select the [location](/infrastructure/locations.mdx) that hosts your existing Managed Database cluster.
4. Select the **Restore cluster from backup** checkbox.
5. Select an existing Managed Database cluster.
6. Select how to restore the cluster — from the latest available backup or to a specific point in time within the last 7 days.
7. Click **Continue**.
8. Select the [node configuration](/managed-databases/postgresql/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
9. For a fixed configuration, select a [configuration line](/managed-databases/postgresql/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
10. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
11. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/postgresql/network-access-control.mdx) from which access to the database cluster will be allowed.
12. Select a [connection pooler mode](/managed-databases/postgresql/connection-pooler.mdx):
* transaction — connection assigned to a client for the duration of a transaction;
* session — connection assigned while a client is connected;
* statement — transactions with multiple statements are prohibited.
13. Optional: change the [DBMS settings](/managed-databases/postgresql/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
14. Click **Create cluster**.
15. After restoring the cluster, node addresses will change — update them in your application.
PostgreSQL for 1C
New
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Enter the cluster name.
4. Select a [location](/infrastructure/locations.mdx). You cannot change the location after creation.
5. Select the PostgreSQL version. You will not be able to change it after creating the cluster.
6. Select the [node configuration](/managed-databases/postgresql-for-1c/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
7. For a fixed configuration, select a [configuration line](/managed-databases/postgresql-for-1c/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
8. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
9. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/postgresql-for-1c/network-access-control-1c.mdx) from which access to the database cluster will be allowed.
10. Select a [connection pooler mode](/managed-databases/postgresql-for-1c/connection-pooler-1c.mdx):
* transaction — connection assigned to a client for the duration of a transaction;
* session — connection assigned while a client is connected;
* statement — transactions with multiple statements are prohibited.
11. Optional: change the [DBMS settings](/managed-databases/postgresql-for-1c/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
12. Click **Create database cluster**. The cluster will be ready to work once it enters the `ACTIVE` status.
From backup
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Select the [location](/infrastructure/locations.mdx) that hosts your existing Managed Database cluster.
4. Select the **Restore cluster from backup** checkbox.
5. Select an existing Managed Database cluster.
6. Select how to restore the cluster — from the latest available backup or to a specific point in time within the last 7 days.
7. Click **Continue**.
8. Select the [node configuration](/managed-databases/postgresql-for-1c/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
9. For a fixed configuration, select a [configuration line](/managed-databases/postgresql-for-1c/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
10. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
11. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/postgresql-for-1c/network-access-control-1c.mdx) from which access to the database cluster will be allowed.
12. Select a [connection pooler mode](/managed-databases/postgresql-for-1c/connection-pooler-1c.mdx):
* transaction — connection assigned to a client for the duration of a transaction;
* session — connection assigned while a client is connected;
* statement — transactions with multiple statements are prohibited.
13. Optional: change the [DBMS settings](/managed-databases/postgresql-for-1c/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
14. Click **Create cluster**.
15. After restoring the cluster, node addresses will change — update them in your application.
PostgreSQL TimescaleDB
New
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Enter the cluster name.
4. Select a [location](/infrastructure/locations.mdx). You cannot change the location after creation.
5. Select the PostgreSQL TimescaleDB version. You will not be able to change it after creating the cluster.
6. Select the [node configuration](/managed-databases/timescaledb/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
7. For a fixed configuration, select a [configuration line](/managed-databases/timescaledb/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
8. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
9. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/timescaledb/network-access-control.mdx) from which access to the database cluster will be allowed.
10. Select a [connection pooler mode](/managed-databases/timescaledb/connection-pooler.mdx):
* transaction — connection assigned to a client for the duration of a transaction;
* session — connection assigned while a client is connected;
* statement — transactions with multiple statements are prohibited.
11. Optional: change the [DBMS settings](/managed-databases/timescaledb/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
12. Click **Create database cluster**. The cluster will be ready to work once it enters the `ACTIVE` status.
From backup
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Select the [location](/infrastructure/locations.mdx) that hosts your existing Managed Database cluster.
4. Select the **Restore cluster from backup** checkbox.
5. Select an existing Managed Database cluster.
6. Select how to restore the cluster — from the latest available backup or to a specific point in time within the last 7 days.
7. Click **Continue**.
8. Select the [node configuration](/managed-databases/timescaledb/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
9. For a fixed configuration, select a [configuration line](/managed-databases/timescaledb/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
10. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
11. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/timescaledb/network-access-control.mdx) from which access to the database cluster will be allowed.
12. Select a [connection pooler mode](/managed-databases/timescaledb/connection-pooler.mdx):
* transaction — connection assigned to a client for the duration of a transaction;
* session — connection assigned while a client is connected;
* statement — transactions with multiple statements are prohibited.
13. Optional: change the [DBMS settings](/managed-databases/timescaledb/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
14. Click **Create cluster**.
15. After restoring the cluster, node addresses will change — update them in your application.
MySQL semi-sync
New
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Enter the cluster name.
4. Select a [location](/infrastructure/locations.mdx). You cannot change the location after creation.
5. Select the MySQL semi-sync version. You will not be able to change it after creating the cluster.
6. Select the [node configuration](/managed-databases/mysql-semi-sync/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
7. For a fixed configuration, select a [configuration line](/managed-databases/postgresql/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
8. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
9. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/mysql-semi-sync/network-access-control.mdx) from which access to the database cluster will be allowed.
10. Optional: change the [DBMS settings](/managed-databases/mysql-semi-sync/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
11. Click **Create database cluster**. The cluster will be ready to work once it enters the `ACTIVE` status.
From backup
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Select the [location](/infrastructure/locations.mdx) that hosts your existing Managed Database cluster.
4. Select the **Restore cluster from backup** checkbox.
5. Select an existing Managed Database cluster.
6. Select how to restore the cluster — from the latest available backup or to a specific point in time within the last 7 days.
7. Click **Continue**.
8. Select the [node configuration](/managed-databases/mysql-semi-sync/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
9. Select the [configuration line](/managed-databases/mysql-semi-sync/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
10. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
11. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/mysql-semi-sync/network-access-control.mdx) from which access to the database cluster will be allowed.
12. Optional: change the [DBMS settings](/managed-databases/mysql-semi-sync/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
13. Click **Create cluster**.
14. After restoring the cluster, node addresses will change — update them in your application.
MySQL sync
New
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Enter the cluster name.
4. Select a [location](/infrastructure/locations.mdx). You cannot change the location after creation.
5. Select the MySQL sync version. You will not be able to change it after creating the cluster.
6. Select the [node configuration](/managed-databases/mysql-sync/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
7. For a fixed configuration, select a [configuration line](/managed-databases/postgresql/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
8. Optional: select the **Add 2 replicas** checkbox. Replicas improve cluster high availability. MySQL sync clusters with replicas have [limitations](/managed-databases/mysql-sync/limitations.mdx).
9. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/mysql-sync/network-access-control.mdx) from which access to the database cluster will be allowed.
10. Optional: change the [DBMS settings](/managed-databases/mysql-sync/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
11. Click **Create database cluster**. The cluster will be ready to work once it enters the `ACTIVE` status.
From backup
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Select the [location](/infrastructure/locations.mdx) that hosts your existing Managed Database cluster.
4. Select the **Restore cluster from backup** checkbox.
5. Select an existing Managed Database cluster.
6. Select how to restore the cluster — from the latest available backup or to a specific point in time within the last 7 days.
7. Click **Continue**.
8. Select the [node configuration](/managed-databases/mysql-sync/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
9. For a fixed configuration, select a [configuration line](/managed-databases/postgresql/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
10. Optional: select the **Add 2 replicas** checkbox. Replicas improve cluster high availability. MySQL sync clusters with replicas have [limitations](/managed-databases/mysql-sync/limitations.mdx).
11. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/mysql-sync/network-access-control.mdx) from which access to the database cluster will be allowed.
12. Optional: change the [DBMS settings](/managed-databases/mysql-sync/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
13. Click **Create cluster**.
14. After restoring the cluster, node addresses will change — update them in your application.
Redis
New
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Enter the cluster name.
4. Select a [location](/infrastructure/locations.mdx). You cannot change the location after creation.
5. Select the Redis version. You will not be able to change it after creating the cluster.
6. Select the [configuration line](/managed-databases/redis/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
7. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
8. Select a [eviction policy](/managed-databases/redis/eviction-policy.mdx).
9. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/redis/network-access-control.mdx) from which access to the database cluster will be allowed.
10. Click **Create database cluster**. The cluster will be ready to work once it enters the `ACTIVE` status.
From backup
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Select the [location](/infrastructure/locations.mdx) that hosts your existing Managed Database cluster.
4. Select the **Restore cluster from backup** checkbox.
5. Select an existing Managed Database cluster.
6. Select how to restore the cluster — from the latest available backup or to a specific point in time within the last 7 days.
7. Click **Continue**.
8. Select the [configuration line](/managed-databases/redis/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
9. Optional: select the **Add replicas** checkbox and specify the number of replicas. Replicas improve cluster high availability.
10. Select a [eviction policy](/managed-databases/redis/eviction-policy.mdx).
11. Select the subnet that you [connected to the global router in step 3](#connect-network-and-subnet-to-router-up-to-cloud-platform-project).
You can [restrict the list of addresses](/managed-databases/redis/network-access-control.mdx) from which access to the database cluster will be allowed.
12. Click **Create cluster**.
13. After restoring the cluster, node addresses will change — update them in your application.
Kafka
1. In the [Control Panel](https://my.selectel.ru/vpc/default/dbaas/), on the top menu, click **Products** and select **Managed Databases**.
2. Click **Create cluster**.
3. Enter the cluster name.
4. Select a [location](/infrastructure/locations.mdx).
5. Select the Kafka version. You will not be able to change it after creating the cluster.
6. Select the [node configuration](/managed-databases/kafka/configurations.mdx):
* fixed — configurations with different vCPU, RAM, and local disk ratios;
* custom — free choice of resource ratios.
7. For a fixed configuration, select a [configuration line](/managed-databases/postgresql/configurations.mdx#configuration-lines):
* Standard;
* CPU;
* Memory;
* HighFreq.
8. Select the subnet type to connect the cluster to:
* private subnet — a subnet with no internet access;
* public subnet — all addresses in the public subnet are accessible from the internet.
Public IP address cannot be used.
Addresses are assigned to each node in the cluster. Ensure the number of addresses in the network is at least as large as the number of nodes in the cluster. The network cannot be changed after creating the cluster.
You can [restrict the list of addresses](/managed-databases/kafka/network-access-control.mdx) from which access to the database cluster will be allowed.
9. If you selected a private subnet, specify the subnet CIDR.
10. If you want to use the DHCP protocol for a private subnet, enable the **DHCP** switch. Learn more about the DHCP protocol in the Selectel blog article [DHCP protocol principles](https://selectel.ru/blog/dhcp-protocol/).
11. If you selected a public network, specify the subnet size.
12. Optional: change the [DBMS settings](/managed-databases/kafka/settings.mdx); to do this, click **Edit**. We recommend changing settings only when necessary — incorrect values can reduce cluster performance.
13. Click **Create database cluster**. The cluster will be ready to work once it enters the `ACTIVE` status.