Link a Managed Database to a dedicated server

For your information

Some dedicated server configurations Chipcore Line 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 on the server page on the Ports tab.

1. Create a global router.
2. Connect to the global router a network and subnet linking to the dedicated server VLAN.
3. Connect to the global router a network and subnet linking to the Cloud Platform project.
4. Assign IP addresses from the created subnets to the dedicated server.
5. Specify routes on the dedicated server.
6. Create a Managed Database cluster: new or from a backup of an existing Managed Database cluster.

See an example of networking between a dedicated server and a Managed Database.

Example of networking between a Managed Database and a 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

1. In the Control panel, in the top menu, click Products and select Global Router.
2. Click Create router. A limit of five global routers is set for each account.
3. Enter the router name.
4. Click Create.
5. If the router was created with the status ERROR or is stuck in one of the statuses, create a ticket.

2. Connect to the router a network and subnet linking to the dedicated server VLAN

You can connect a new or existing network to the router if it is not already connected to any of the account's global routers.

1. In the control panel, on the top menu, click Products and select Global Router.

2. Go to the router page → Networks tab.

3. Click Create network.

4. Enter a network name. It will only be used in the control panel.

5. Select the Servers and Equipment service.

6. Select a location for the network.

7. Select or enter a VLAN.

8. If you want to create a network up to an internal segment (Q-in-Q), specify its tag—a number from 2 to 4094. If a network already exists for the VLAN, you must specify the Q-in-Q segment of this VLAN.

9. Enter a subnet name. It will only be used in the control panel.

10. Enter the CIDR—the IP address and mask of the private subnet. You can enter a new subnet or an existing private server subnet if it has not yet been added to any of the global routers in the account. The subnet must meet the following conditions:

    • belong to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
    • have a size of at least /29, as three addresses will be occupied by Servercore network equipment;
    • do not overlap with other subnets added to this router—IP addresses must not repeat across subnets on the same router;
    • if a Managed Kubernetes cluster on cloud servers is included in the global router network, the subnet must not overlap with the ranges 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is included in the network — with ranges 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for Managed Kubernetes internal addressing, and their use may lead to conflicts in the global router network.

11. Enter the gateway IP or leave the first address from the subnet that is assigned by default. Do not assign this address to your devices to avoid network disruption.

12. Enter the service IPs or leave the last addresses from the subnet that are assigned by default. Do not assign these addresses to your devices to avoid network disruption.

13. Click Create network.

14. Optional: check the network topology on the global router. In the Control panel, in the top menu, click Products → Global Router → router page → Network map.

15. If you specified a Q-in-Q tag in step 8, you need to enable Q-in-Q technology on the switch port and configure the private network interface that you specified in step 10. Learn more in the Configure Q-in-Q section of the Q-in-Q guide.

3. Connect to the router a network and subnet linking to the Cloud Platform project

You can connect a new or existing network to the router if it is not already connected to any of the account's global routers.

Connect a new network

1. In the Control panel, on the top menu, click Products and select Global Router.

2. Open the router page → Networks tab.

3. Click Create network.

4. Enter a network name. It will only be used in the control panel.

5. Select the Cloud Platform service.

6. Select the network location.

7. Select a project.

8. Enter a subnet name. It will only be used in the control panel.

9. Enter the CIDR — the IP address and subnet mask. The subnet must meet the following conditions:

   • belong to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • have a size of at least /29, as three addresses will be occupied by Servercore network equipment;
   • does not overlap with other subnets added to this router — there must be no identical IP addresses within the subnets of a single router;
   • если in сеть глобального роутера будет включен кластер Managed Kubernetes on облачных серверах, подсеть не должна пересекаться with диапазонами 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. Если in сеть будет включен кластер on выделенных серверах — with диапазонами 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. Эти подсети участвуют во внутренней адресации Managed Kubernetes, их использование может привести к конфликтам in сети глобального роутера.

10. Enter the gateway IP or leave the first address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid disrupting network operations.

11. Enter the service IPs or leave the last addresses from the subnet, which are assigned by default. Do not assign these addresses to your devices to avoid disrupting network operations.

12. Click Create network.

13. Optional: check the network topology on the Global Router. In the Control panel, on the top menu, click Products → Global Router → router page → Network map.

Connect an existing network

1. Ensure that the network has not yet been added to any global router in your account. In the Control panel, on the top menu, click Products → Cloud Servers → Network → Private networks tab → make sure the network card does not have the Global Router tag.

2. Ensure the subnet meets the following conditions:

   • belongs to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • is at least /29, as three addresses will be occupied by Servercore network equipment;
   • does not overlap with other subnets added to this router: the IP addresses of each subnet on the router must not overlap with the IP addresses of other subnets on the router;
   • if a Managed Kubernetes cluster on cloud servers is to be added to the Global Router network, the subnet must not overlap with the 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is to be added to the network — with the 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for internal Managed Kubernetes addressing; using them may lead to conflicts in the Global Router network.

3. In the Control panel, on the top menu, click Products and select Cloud Servers.

4. Go to Network → Private networks tab.

5. In the network menu, select Connect to Global Router.

6. Select a global router.

7. For each subnet of the network, enter the IP address to be assigned to the router, or leave the first available address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid disrupting network operations. The last two available subnet addresses will be reserved as service addresses.

8. Click Connect. Do not close the window until a message appears confirming that the network is connected. After that, in the Control panel:

   • the network will appear in the section Servercore Global Router on the page of the router you connected it to;
   • in the section Cloud Servers → Network → on the Private networks tab, the network will have a Global Router tag.

4. Assign an IP address to the dedicated server

Configure a local port on the dedicated server that joins the global router network. Assign to the port an IP address from the private subnet that you connected to the global router for the dedicated server.

Ubuntu

1. Connect to the server via SSH or via KVM console.

2. Open the netplan utility configuration file with the vi:

   vi /etc/netplan/01-netcfg.yaml

3. Add or change the values of the private network interface settings:

       <eth_name>:
               addresses: [<ip_address>]

   Specify:

   • <eth_name> — the name of the private network interface;
   • <ip_address> — the private IP address of the server with a subnet mask, for example 192.168.0.2/24.

4. Press ESC.

5. Exit the vi text editor with your changes saved:

   :wq

6. Apply the configuration:

   netplan apply

7. Optional: reboot the server.

8. Optional: assign a private IP address to the server in the control panel.

Debian

1. Connect to the server via SSH or via KVM console.

2. Open the network interfaces configuration file with the vi:

   vi /etc/network/interfaces.d/50-cloud-init

3. Add or change the values of the private network interface settings:

   auto <eth_name>
   iface <eth_name> inet static
       address <ip_address>/<mask>

   Specify:

   • <eth_name> — the name of the private network interface;
   • <ip_address> — the private IP address of the server, for example 192.168.0.2;
   • <mask> — the subnet mask, for example /24.

4. Press ESC.

5. Exit the vi text editor with your changes saved:

   :wq

6. Restart the network:

   service networking restart

7. Optional: reboot the server.

8. Optional: assign a private IP address to the server in the control panel.

CentOS

1. Connect to the server via SSH or via KVM console.

2. Output information about the network interfaces:

   ip address

3. Create or open the private network interface configuration file with the vi:

   vi /etc/sysconfig/network-scripts/ifcfg-<eth_name>

   Specify <eth_name> — the name of the private network interface.

4. Add or change the values of the network interface settings:

   NAME="<eth_name>"
   ONBOOT=yes
   BOOTPROTO=none
   IPADDR="<ip_address>"

   Specify:

   • <eth_name> — the name of the private network interface;
   • <ip_address> — the private IP address of the server with a subnet mask, for example 192.168.0.2/24;

5. Press ESC.

6. Exit the vi text editor with your changes saved:

   :wq

7. Restart the network:

   systemctl restart network

8. Optional: reboot the server.

9. Optional: assign a private IP address to the server in the control panel.

Windows

1. Connect to the server via RDP or via KVM console.

2. Open the Network and Sharing Center.

3. Open the private network interface.

4. Click Properties.

5. From the list, select IPv4.

6. Click Properties.

7. Specify the network interface parameters:

   • IP-address — the private IP address of the server with a subnet mask, for example 192.168.0.2;
   • Subnet mask — the subnet mask.

8. Click OK.

9. Optional: assign a private IP address to the server in the control panel.

5. Specify routes on the dedicated server

Ubuntu

1. Connect to the server.

2. Open the network configuration file:

   vi /etc/netplan/01-netcfg.yaml

3. At the end of the data block for the required network interface, add the route:

   routes:
     - to: <ip_address>/<mask>
       via: <gateway>

   Specify:

   • <ip_address>/<mask> — the subnet to which you need to add a route, specifying the mask, for example 192.168.0.0/28;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router.

4. If you need to define multiple routes, add them sequentially in the same block, for example:

   routes:
   - to: 192.168.0.0/28
       via: 172.16.0.1
   - to: 192.168.1.0/28
       via: 172.16.0.1

5. Save the file.

6. Check the settings:

   sudo netplan try

7. Apply the changes:

   netplan apply

Debian

1. Connect to the server.

2. Open the network configuration file:

   vi  /etc/network/interfaces

3. At the end of the data block for the corresponding network interface, add the required route:

   up route add -net <ip_address> netmask <mask> gw <gateway>
   down route del -net <ip_address> netmask <mask> gw <gateway>

   Specify:

   • <ip_address> — the subnet to which you need to add a route, for example 192.168.0.0;
   • <mask> — the subnet mask to which you need to add a route, for example 255.255.255.0;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router.

4. If you need to define multiple routes, add them sequentially in the same block.

5. Save the file.

6. Restart the network:

   sudo /etc/init.d/networking restart

CentOS

1. Connect to the server.

2. Create and fill out the file for configuring static routes:

   echo "<ip_address>/<mask> via <gateway>" >> /etc/sysconfig/network-scripts/route-<eth_name>

   Specify:

   • <ip_address>/<mask> — the subnet to which you need to add a route, specifying the mask, for example 192.168.1.0/28;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router;
   • <eth_name> — the name of the corresponding local network interface.

   If you need to add multiple routes, specify them in one command. List each route on a new line, for example:

   echo "192.168.0.0/28 via 172.16.0.1
   192.168.1.0/28 via 172.16.0.1" >> /etc/sysconfig/network-scripts/route-eno2

3. Restart the network:

   systemctl restart network

Windows

1. Connect to the server via RDP or via KVM console.

2. Add the required routes one by one:

   route -p ADD <ip_address> MASK <mask> <gateway> METRIC <x>

   Specify:

   • <ip_address> — the subnet to which you need to add a route, for example 192.168.0.0;
   • <mask> — the subnet mask to which you need to add a route, for example 255.255.255.0;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router;
   • <x> — a parameter determining the priority of the specified gateway, 1 being the highest priority.

6. Create a Managed Database cluster

PostgreSQL

New

1. In the Control Panel, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Enter the cluster name.

4. Select a location. 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:

   • 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:

   • 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 linking to the Cloud Platform project.

   You can restrict the list of addresses from which access to the database cluster will be allowed.

10. Select a connection pooler mode:

    • 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; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Select the location 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:

   • 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:

   • 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 linking to the Cloud Platform project.

    You can restrict the list of addresses from which access to the database cluster will be allowed.

12. Select a connection pooler mode:

    • 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; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Enter the cluster name.

4. Select a location. 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:

   • 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:

   • 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 linking to the Cloud Platform project.

   You can restrict the list of addresses from which access to the database cluster will be allowed.

10. Select a connection pooler mode:

    • 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; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Select the location 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:

   • 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:

   • 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 linking to the Cloud Platform project.

    You can restrict the list of addresses from which access to the database cluster will be allowed.

12. Select a connection pooler mode:

    • 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; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Enter the cluster name.

4. Select a location. 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:

   • 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:

   • 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 global router subnet that you created linking to the Cloud Platform project.

   You can restrict the list of addresses from which access to the database cluster will be allowed.

10. Select a connection pooler mode:

    • 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; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Select the location 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:

   • 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:

   • 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 global router subnet that you created linking to the Cloud Platform project.

    You can restrict the list of addresses from which access to the database cluster will be allowed.

12. Select a connection pooler mode:

    • 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; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Enter the cluster name.

4. Select a location. 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:

   • 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:

   • 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 linking to the Cloud Platform project.

   You can restrict the list of addresses from which access to the database cluster will be allowed.

10. Optional: change the DBMS settings; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Select the location 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:

   • fixed — configurations with different vCPU, RAM, and local disk ratios;
   • custom — free choice of resource ratios.

9. Select the configuration line:

   • 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 linking to the Cloud Platform project.

    You can restrict the list of addresses from which access to the database cluster will be allowed.

12. Optional: change the DBMS settings; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Enter the cluster name.

4. Select a location. 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:

   • 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:

   • Standard;
   • CPU;
   • Memory;
   • HighFreq.

8. Optional: select the Add 2 replicas checkbox. Replicas improve cluster high availability. MySQL sync clusters with replicas have limitations.

9. Select the subnet that you connected to the global router linking to the Cloud Platform project.

   You can restrict the list of addresses from which access to the database cluster will be allowed.

10. Optional: change the DBMS settings; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Select the location 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:

   • 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:

   • Standard;
   • CPU;
   • Memory;
   • HighFreq.

10. Optional: select the Add 2 replicas checkbox. Replicas improve cluster high availability. MySQL sync clusters with replicas have limitations.

11. Select the subnet that you connected to the global router linking to the Cloud Platform project.

    You can restrict the list of addresses from which access to the database cluster will be allowed.

12. Optional: change the DBMS settings; 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Enter the cluster name.

4. Select a location. 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:

   • 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.

9. Select the subnet that you connected to the global router linking to the Cloud Platform project.

   You can restrict the list of addresses 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Select the location 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:

   • 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.

11. Select the subnet that you connected to the global router linking to the Cloud Platform project.

    You can restrict the list of addresses 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, on the top menu, click Products and select Managed Databases.

2. Click Create cluster.

3. Enter the cluster name.

4. Select a location.

5. Select the Kafka version. You will not be able to change it after creating the cluster.

6. Select the node configuration:

   • 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:

   • 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 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.

11. If you selected a public network, specify the subnet size.

12. Optional: change the DBMS settings; 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.