Skip to main content
Private pool segments
Last update:

Private pool segments

Private pool segments can be used to back up one or more virtualization hosts — running cloud servers with isolation at the physical layer if there are special security requirements or to guarantee availability of computing resources at any given time.

In public pool segments, cloud servers run on physical hosts that can be shared by many clients. Each pool segment is associated with one or more physical servers. Within each private segment, you can fully control cloud platform resources without sharing host hardware with other clients.

Available Resources

The private pool segment can be used in any account project along with public pools. Access to resource utilization is limited by project limits.

In the private segment of the pool:

  • all network volume types of the cloud platform are available. To implement non-standard capacity or performance requirements for network disks, you can organize dedicated NAS;
  • you can configure network volumes to be backed up with backups;
  • cloud servers can use the same network resources as in public segments;
  • cloud servers can be interconnected with servers in other segments by a private network;
  • are used image storages of the pool segments on the basis of which they are launched.


A private pool segment can consist of one or more virtualization hosts. It is not possible to use several different processors within the same segment.

Account limit on private segment pool resources:

  • vCPU — 1 vCPU per physical processor core (can be changed on request);
  • RAM — sum of virtualization host capacities;
  • local disk — the sum of virtualization host capacities.

In the private segment, you can only run cloud servers with fixed configurations.

There are restrictions on the maximum size of the cloud server — it is determined by the parameters of virtualization hosts included in the pool segment. For example, if a private pool segment is formed by hosts with 36 physical cores and 354 GB RAM, the maximum server size will be limited to 36 vCPUs and 354 GB RAM.

Maintenance of virtualization hosts in private pool segments is performed by Selectel specialists.

Available processors

You can view the availability of processors in regions in the [Private Pool Segments] availability matrix(/control-panel-actions/availability-matrix.mdx#private-pool-segments).

Intel® Xeon® Processor E5-2670 v3 @ 2.30 GHzIntel® Xeon® Processor E5-2680 v4 @ 2.40 GHzIntel® Xeon® Processor E5-2699 v4 @ 2.20 GHzIntel® Xeon® Gold 5218 @ 2.30 GHzIntel® Xeon® Gold 6140 @ 2.30 GHzIntel® Xeon® Gold 6240 @ 2.60 GHz (in the ru-7a pool segment)Intel® Xeon® Gold 6240 @ 2.60 GHz (in the ru-7a, ru-9a pool segments)Intel® Xeon® Gold 6240R @ 2.40 GHzIntel® Xeon® Gold 6336Y @ 2.40 GHzAMD EPYC™ 7742 @ 2.25 GHz
Number of Processors22242 / 424222
Number of Cores2428446436 / 7236724848128
RAM, GB229229229731349 / 371221 / 349731221 / 349221450
Local SSD disk capacity, TB
(for hosts with local storage)
3.6 / /

Connect a private pool segment

To connect a private pool segment create a ticket.

Creating a private pool segment with up to four hosts takes one business day, from five hosts — from one week.

You can transfer resources to a private pool segment from a public pool segment by yourself — create disk from a snapshot or image.


Private pool segments are paid using cloud platform payment model.

The cost of a private pool segment depends on the selected configuration of virtualization hosts and their number — the number of physical cores, amount of memory and local disk capacity are taken into account.

We will provide the exact cost in the ticket response.