Network volumes are persistent block devices suitable for scaling volume space without changing the basic volume.
A cloud server is created with a boot (system) volume. A boot (system) volume can be either local or network. Only network volumes can be connected as additional volumes.
Network volume types:
- Basic volume. Solution based on enterprise-class SATA volumes. Best for storing large amounts of data with few read and write operations;
- Fast volume. Solution based on SSD. Faster response time and higher performance compared to basic volumes;
- Universal volume. Solution based on SSD. Best for storing system volumes of virtual machines.
Network scalable volume settings are listed on our website.
When using a network volume together with a local volume, the network volume should be mounted as a separate device in the OS. To connect an additional volume to the server, you can create a new volume or reconnect the volume from another server.
Creating and Connecting Network Volumes
To create an additional volume:
- Go to the Volumes section of the desired project.
- Click Create volume.
- Specify the region and location.
- Select a source by clicking on the appropriate field. You can use both prepared images and your own one or load images from existing snapshots (learn more).
- Select volume type and size.
- Click Create.
To connect an additional volume:
- Open the volume card and go to the Control tab.
- Select the desired server in the Attach to server field.
- Click Attach.
Network Volumes Limits
Depending on the selected volume type, purpose of use and the possibility of further fine-tuning of the file system, we recommend that you do not exceed the limits indicated in the table:
|Volume type||Recommended limits for the system volume||Recommended limits for the additional volume|
|Basic (all regions)||500 GB||10 TB|
|Universal (ru-1, ru-2, ru-3)||2 TB||10 TB|
|Universal (ru-7, ru-8, ru-9)||5 TB||10 TB|
|Fast (ru-1, ru-2, ru-3)||2 TB||10 TB|
|Fast (ru-7, ru-8, ru-9)||10 TB||10 TB|
The data is provided for volumes with GPT partitioning, as this partitioning is used by default in the Cloud Platform’s prepared images.
If you prepare images yourself and plan to create volumes with a capacity of more than 2 TB from these images, use GPT partitioning instead of the common MBR partitioning. Read more about partitioning formats in the article GUID Partition Table.
When you first launch the cloud server, the file system on the system volume “stretches” to fit the volume. The larger the volume size and the lower its IOPS limits are, the more this process will take, and therefore, the longer the cloud server will start.
The file system size also affects the time it takes to check the status of the file system in the event of a server crash. This check is enabled by default for the system volume in all servers created from the Cloud platform’s prepared images and can be manually configured for connected volumes.
Different volume types in the Cloud platform have different limits on IOPS – the number of operations per second. Creating or checking a file system is a procedure requiring a certain number of read and write operations to volume. The higher the volume performance, the faster these operations are completed.
Creating Your Own Image with GPT Partitioning Format
The procedure for creating your own image with GPT partitioning format is described in the article.