Skip to main content

Transfer a cloud server or cloud infrastructure

Last update:

If you need to transfer a configured infrastructure (servers, networks, volumes, backups, and other resources) or if it is important to keep the public IP address when transferring a server, we recommend you transfer the infrastructure project to another account. When performing such a transfer, you cannot choose a different pool segment.

Облачный сервер можно перенести in другой сегмент пула, проект or аккаунт. Для этого нужно создать and перенести образ загрузочного диска сервера or перенести диск сервера напрямую. При переносе образа in другой проект or аккаунт можно также изменить сегмент пула. Напрямую перенести сервер невозможно.

Transfer a cloud infrastructure project to another account

To transfer cloud infrastructure to another account, transfer the project.

Можно перенести проект только in рамках одного сегмента пула. Все объекты проекта сохранятся: серверы, сети, публичные IP-адреса, диски and остальные ресурсы.

Чтобы перенести проект in другой аккаунт, используйте инструкцию Перенести услуги in другой аккаунт

Transfer a cloud server to another pool segment, project, or account

warning

When transferring a cloud server, its public IP address and other project resources will not be transferred. After the transfer, you can connect a new IP address or create a public subnet. If you want to keep the public IP address, transfer the entire project to another account.

A cloud server can be transferred to another pool segment, project, and account. When transferring an image to another project or account, you can also change the pool segment, including choosing a different pool and region.

You can transfer a server in two ways:

  • transfer a boot volume image to use it for creating a new server in another pool segment, project, or account. We recommend using this method for transferring a server with a small amount of data;
  • transfer the server volume directly to a server in another pool segment, project, or account. We recommend using this method for transferring a server with a large amount of data.

  1. View the name and type of the source cloud server's boot volume.

  2. Create a boot volume image of the source cloud server.

  3. Transfer the image to the account, project, or pool segment where you want to transfer the cloud server.

  4. Create the target cloud server from the boot volume image.

  5. If the source server uses additional volumes, transfer them and connect them to the target server.

  6. If the source and target servers are in different pools, create a new public IP address for the server.

1. View the name and type of the source server's boot volume

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

  2. Open the Servers tab → server page.

  3. Open the Configuration tab. If the tab has a Local disk field, the server has a local boot volume.

  4. Open the Network volumes tab. If the volume line has a Bootable tag, the server has a network boot volume.

2. Create a boot volume image of the source server

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

  2. In the server menu, select Shutdown. The server status will change to SHUTOFF.

  3. Перейдите in раздел Образы.

  4. Click Create image.

  5. Enter the image name.

  6. Выберите локацию, in которую загрузится образ. Образы размером менее 16 ГБ автоматически реплицируются in соседние сегменты пула локации.

  7. Select a volume as the image source.

  8. Select a volume — an image can only be created in the pool where the volume is located.

  9. Optional: check the Specify minimum disk and memory requirements checkbox. Specify the minimum RAM in MB and disk size in GB. When a cloud server is created from this image, the Control panel or API will automatically check these restrictions.

  10. Click Create.

3. Transfer the image

The image can be transferred to another account, project, or pool segment.

When transferring an image to another account or project, you can also change the pool segment.

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

  2. Перейдите in раздел Образы.

  3. In the menu for the boot volume image, select Copy link.

  4. Go to the account you want to transfer the server to.

  5. Open the projects menu (name of the current project) and select the required project.

  6. Click Create image.

  7. Enter the image name.

  8. Выберите локацию, in которую нужно перенести образ. Облачный сервер перенесется in эту же локацию.

  9. Select URL as the image source.

  10. Paste the image URL that you copied in step 3.

  11. Select the image format and the container format.

    If you are not sure which formats to specify, set the image format to raw and the container format to bare.

  12. Select the operating system.

  13. Optional: check the Specify minimum disk and memory requirements checkbox. Specify the minimum RAM in MB and disk size in GB. When a cloud server is created from this image, the Control panel or API will automatically check these restrictions.

  14. Click Create.

4. Create a target server from the image

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

  2. Click Create server.

  3. Enter the cloud server name. It will be set as the hostname in the operating system on the server.

  4. Select the location to which you transferred the boot volume image.

  5. В блоке Источник откройте вкладку Образы.

  6. Select the boot volume image you created earlier.

  7. Click Select.

  8. Select a cloud server configuration range:

    • fixed — configurations of ranges with different specifications in which the resource ratio is fixed;
    • custom — configurations in which you can specify any resource ratio.

    В разных линейках and конфигурациях сервера in зависимости от сегмента пула используются разные процессоры. К конфигурациям можно добавить графические процессоры — подробнее in инструкции Создать облачный сервер with GPU

    After creating a server, you can change its configuration.

    Объем оперативной памяти, который выделяется серверу, может быть меньше указанного — ядро операционной системы резервирует часть оперативной памяти in зависимости от версии ядра and дистрибутива. Выделенный объем on существующем сервере можно проверить with помощью команды sudo dmesg | grep Memory.

  9. Select the server's boot (system) volume:

    • local disk without network latency — check the Local SSD NVMe disk box. If you selected a custom configuration, specify the local disk size. If you selected a fixed one, the disk size will depend on the configuration;
    • or a network volume — in the Disk type field, select the disk type and specify its size.

    After creating the server, you will be able to replace only the network boot volume.

  10. Click Add.

  11. Optional: to add an additional volume to the server, click Add. You can add multiple volumes.

    After creating the server, you can detach additional volumes and connect new ones.

    You can transfer additional volumes that were connected to the source server.

  12. In the Network block, connect an existing private subnet with a cloud router or create a new one:

    12.1. Нажмите Приватная подсеть.

    12.2. В поле Публичный IP-адрес для доступа из интернета выберите Новый публичный IP-адрес.

    12.3. Разверните блок with настройками приватной подсети

    12.4. В поле Подсеть выберите существующую подсеть.

    12.5. В поле Приватный IP укажите приватный IP-адрес сервера. Публичный IP-адрес будет автоматически подключен к приватному адресу.

  13. Выберите группы безопасности для фильтрации трафика on портах сервера. Без групп безопасности трафик будет запрещен. Если блок отсутствует, in сети сервера выключена фильтрация трафика (port security). С выключенной фильтрацией трафика весь трафик будет разрешен.

  14. To connect to the server securely, place an SSH key on it. You can add multiple keys. Key types ed25519, rsa, ecdsa, and dsa are supported.

    Select an existing key or click Add SSH-key. Enter the key name and paste the public SSH key in OpenSSH format. Click Add.

    If SSH keys are not created, generate them.

  15. Optional: copy and save the root user password (a user with unlimited rights for all system actions). Store the password in a secure place and do not transmit it in plain text.

  16. Optional: чтобы создать прерываемый сервер, отметьте чекбокс Прерываемый сервер.

  17. Optional: if you plan to create multiple servers and want to increase infrastructure reliability, we recommend using placement groups or placing cloud servers in different pool segments — in other cases, we do not guarantee placement on different hosts.

    Select an existing placement group or click Create group and enter the group name. Select a placement policy:

    • preferably on different hosts — soft-anti-affinity, the system will try to place servers on different hosts. If there is no suitable host available when creating the server, it will be created on the same host;
    • must be on different hosts — anti-affinity, servers in a group must be located on different hosts. If we do not find a suitable host, the server will not be created.

    After creating a server, it cannot be added to a group directly — only by creating a copy.

  18. Optional: чтобы добавить к серверу дополнительную информацию or фильтровать серверы in списке, добавьте тег. Можно добавить несколько тегов. Автоматически добавляются теги операционной системы and конфигурации.

    In the Tags field, check the existing tags or enter a new one. The maximum tag length is 60 characters. You can use Latin or Cyrillic letters, numbers, and hyphens.

  19. Optional: in поле User data вставьте or загрузите скрипт, который выполнится при загрузке системы. Максимальный размер скрипта with данными, которые не закодированы in Base64, — 16 КБ. Примеры скриптов and поддерживаемые форматы можно посмотреть in инструкции User data

  20. Click Create server.

5. Transfer additional volumes

If the source cloud server uses additional volumes, they can be transferred.

  1. Create images of additional volumes.

  2. Transfer the additional volume images to the account, project, or pool segment to which you transferred the cloud server.

  3. Create network volumes from the images.

  4. Connect the network volumes to the new cloud server.

6. Create a public IP address for the server

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

  2. Перейдите in раздел Сеть.

  3. Откройте вкладку Публичные IP-адреса.

  4. Click Create IP address.

  5. Select the location where the public IP address will be created.

  6. Specify the number of public IP addresses.

  7. Click Create.