Move a cloud server or cloud infrastructure

If you need to migrate the configured infrastructure (servers, networks, disks, backups and other resources) or it is important to keep the public IP address when migrating a server, we recommend migrating the infrastructure project to another account. You cannot select a different pool segment during this migration.

You can migrate a cloud server to another pool segment, project, or account.To do this, you must create and migrate a boot disk image of the server or migrate the server disk directly.When migrating the image to another project or account, you can also change the pool segment.You cannot migrate the server directly.

Move a cloud infrastructure project to another account⁠

To migrate your cloud infrastructure to another account, migrate the project.

You can migrate a project only within one pool segment.All project objects will be preserved: servers, networks, public IP addresses, disks and other resources.

To transfer a project to another account, use the Transfer Services to Another Account instructions.

Move the cloud server to another pool segment, project or account⁠

carefully

When migrating the server, the public IP address of the cloud server and other project resources will not be migrated.After migrating the server, you can create a new IP address or public subnet.If you want to keep the public IP address, migrate the entire project to another account.

You can move the cloud server to a different pool segment, project, and account.When you move the image to a different project or account, you can also change the pool segment, including selecting a different pool and region.

You can move a server in two ways:

• Transfer the boot disk image to use it to create a new server in a different pool segment, project, or account. We recommend using this method to migrate a server with a small amount of data;
• move the server disk directly to a server in another pool segment, project or account. We recommend using this method to migrate a server with a large amount of data.

Transfer disk image

1. Look at the name and type of boot disk of the source cloud server.

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

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

4. Create a target cloud server from the boot disk image.

5. If additional disks are used on the source server, migrate 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 boot disk of the source server⁠

1. In the Dashboard, 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 the Local Disk field, the server has a bootable local disk.

4. Open the Network Disks tab. If there is a Bootable tag in the disk line, the server has a bootable network disk.

2. Create a bootable disk image of the source server⁠

Control panel

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

2. From the server menu, select Shutdown. The server will enter the SHUTOFF status.

3. Go to the Images section.

4. Click Create Image.

5. Enter a name for the image.

6. Select the pool segment to which the image will be loaded. Images smaller than 16 GB are automatically replicated to neighboring pool segments.

7. Select the disk as the image source.

8. Select a disk — you can only create an image in the pool where the disk is located.

9. Optional: check the box Specify minimum disk and memory requirements. Specify the minimum amount of RAM in MB and disk capacity in GB. When you create a cloud server from this image, the control panel or API will automatically check these limits.

10. Click Create.

OpenStack CLI

The image will only be available for one project and pool for which you have configured authorization in the OpenStack API.

The process of creating an image depends on the type of disk you looked at earlier.

Local disk

1. Open the OpenStack CLI.

2. Shut down the server — a non-consistent image may be created from a running disk:

   openstack server stop <server>

   Specify <server> — server ID or name. The list can be viewed using the openstack server list command.

   The server will go into SHUTOFF status.

3. Create a local disk image:

   openstack server image create --name <image_name> <server>

   Specify:

   • <image_name> — image name;
   • <server> — The server ID or name. The list can be viewed with the command openstack server list.

Network disk

1. Open the OpenStack CLI.

2. Shut down the server — a non-consistent image may be created from a running disk:

   openstack server stop <server>

   Specify <server> — server ID or name. The list can be viewed using the openstack server list command

   The server will go into SHUTOFF status.

3. Disconnect the network drive from the server:

   openstack server remove volume <server> <volume>

   Specify:

   • <server> — The server ID or name. The list can be viewed with the command openstack server list;
   • <volume> — ID or name of the network drive. You can view the list with the command openstack volume list.

4. Check that the network drive has entered the AVAILABLE status:

   openstack volume list

5. Create a network disk image:

   openstack image create --volume <volume> <image_name>

   Specify <image_name> — image name.

3. Transfer the image⁠

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

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

Control panel

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

2. Go to the Images section.

3. From the menu of the boot disk image, select Copy link.

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

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

6. Click Create Image.

7. Enter a name for the image.

8. Select the pool segment to which you want to migrate the image. The cloud server will be moved to the same segment.

9. Select URL as the image source.

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

11. Select the image format and container format.

    If you don't know what formats to specify, specify raw image format, bare container format.

12. Select the operating system.

13. Optional: check the box Specify minimum disk and memory requirements. Specify the minimum amount of RAM in MB and disk capacity in GB. When you create a cloud server from this image, the control panel or API will automatically check these limits.

14. Click Create.

4. Create a target server from the image⁠

Control panel

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

2. Click Create Server.

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

4. Select the pool segment to which you transferred the boot disk image.

5. Click the default source name → My Images tab.

6. Select the boot disk image you created earlier.

7. Press Select.

8. Select a cloud server configuration:

   • fixed — lines with different vCPU to RAM ratios up to 48 vCPUs, 320 GB of RAM, and 1.25 TB of local disk capacity;
   • arbitrary — select any resource ratio up to 32 vCPUs, 256 GB RAM and 2 TB of local disk space.

   Different configurations and server lines use different processors depending on the pool segment. You can add GPUs to the configurations — more details in the Create a cloud server with GPU instructions.

   After the server is created, you can change the configuration.

   The amount of RAM that is allocated to the server may be less than the specified amount — the operating system kernel reserves some RAM depending on the kernel version and distribution. You can check the allocated amount on an existing server with sudo dmesg | grep Memory.

9. Select the server boot (system) disk:

   • local disk without network latency — check the box Local SSD NVMe disk. If you have selected an arbitrary configuration, specify the local disk size. If you selected fixed, the disk size will depend on the configuration;
   • or network disk — in the Disk Type field, select the type of disk and specify its size.

   Once the server is created, only the network boot disk can be replaced.

10. Click Add.

11. Optional: To add an additional disk to the server, click Add. Multiple disks can be added.

    After the server is created, you can disconnect additional disks from the server and connect new disks.

    You can migrate additional disks that were attached to the source server.

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

    Existing private subnet

    12.1 Click Private Subnet.

    12.2. In the Public IP Address for Internet Access field, select New Public IP Address.

    12.3. Expand the block with private subnet settings.

    12.4. In the Subnet field, select an existing subnet.

    12.5. In the Private IP field, specify the private IP address of the server. The public IP address will be automatically connected to the private address.

    New private subnet

    12.1 Click Private Subnet.

    12.2. In the Public IP Address for Internet Access field, select New Public IP Address.

    12.3. Expand the block with private subnet settings.

    12.4 If you have existing networks in the project, select New Subnet in the Subnet field.

    12.5 Optional: Change the CIDR of the subnet.

    12.6 Optionally: enable the DHCP toggle switch.

    12.7. Optional: in the Gateway field, change the IP address of the default gateway.

    12.8. In the Network field, select the existing network where the subnet will be created or New network. For a private subnet with a public IP address, router-<network_name>, where <network_name> is the network name, will be automatically created.

    12.9. If you selected New Network, enter the name of the network.

13. Select security groups to filter traffic on server ports. Without security groups, traffic will not be allowed. If there is no block, port security is disabled on the server network . With traffic filtering disabled, all traffic will be allowed.

14. To securely connect to the server, place an SSH key on the server. Multiple keys can be added. The supported key types are ed25519, rsa, ecdsa, and dsa.

    Select an existing key or click Add SSH Key. Enter a key name and insert a public SSH key in OpenSSH format. Click Add.

    If SSH keys are not created, generate them.

15. Optional: Copy and save the password of the root user (a user with unlimited rights to all actions on the system). Store the password in a safe place and do not share it in plaintext.

16. Optional: To create an interruptible server, check the Interruptible Server checkbox.

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

    Select an existing placement group or click Create Group and enter a 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 when creating a server, it will be created on the same host;
    • necessarily on different hosts — anti-affinity, servers in a group are necessarily located on different hosts. If we do not find a suitable host, the server will not be created.

    Once a server is created, it cannot be added to the group directly — only by creating a copy.

18. Optional: to add additional information to the server or filter the servers in the list, add a tag. Multiple tags can be added. Operating system and configuration tags are automatically added.

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

19. Optional: in the User data field, insert or upload a script that will be executed at system startup. The maximum size of a script with non-Base64 encoded data is 16 KB. Examples of scripts and supported formats can be found in the User data instruction.

20. Click Create Server.

OpenStack CLI

1. Open the OpenStack CLI.

2. Create a cloud server:

openstack server create \
    [--image <image> | --volume <volume> | --snapshot <snapshot>] \
    --flavor <flavor> \
    --availability-zone <pool_segment> \
    --nic net-id=<net_uuid> \
    --security-group <security_group> \
    --key-name <key_name> \
    <server_name>

Specify:

• source type:
  • --image <image> — to create a server from off-the-shelf or custom image. Parameter <image> — ID or name of the image. The list of images can be viewed with the command openstack image list;
  • --volume <volume> — to create a server from network disk. Parameter <volume> — ID or disk name. You can view the list of network disks with the command openstack volume list;
  • --snapshot <snapshot> — to create a server from snapshot. Parameter <snapshot> — ID or name of the snapshot. The list of snapshots can be viewed with the command openstack snapshot list;
• <flavor> — The ID or name of the flavor. The flavors correspond to cloud server configurations and determine the number of vCPUs, RAM, and local disk size (optional) of the server. You can use fixed configuration flavors or create a flavor. For example, 4011 — ID to create a Memory Line fixed configuration server with 2 vCPUs, 16 GB RAM in a ru-9 pool. You can view the list of flavors using the command openstack flavor list or in the table List of fixed configuration flavors in all pools;
• <pool_segment> — pool segment in which the cloud server will be created, e.g. ru-9a. The list of available pool segments can be found in the instructions. Availability matrices;
• <net_uuid> — ID of the private or public network to which the server will be connected. The list can be viewed with the command openstack network list;
• <security_group> — The ID or name of the security group that will be assigned to all ports on the server. To create a server with a security group, the network must have port security enabled. port security. The list of groups can be viewed with the command openstack security group list;
• <key_name> — name of the SSH key pair for the service user. If SSH keys are not created, generate them. The list can be viewed with the command openstack keypair list;
• optional: --block-device-mapping vdb=<extra_volume> — ID or name of the extra disk. The list can be viewed using the openstack volume list command;
• optional: --tag <tag_name> --os-compute-api-version 2.52 — tag to add more information about the server;
• optional: --tag preemptible --os-compute-api-version 2.72 — tag to create an interruptible server;
• optional: --user-data <user_data.file> — path to the script with Base64 encoded data. Scripts and tasks from the script will be executed at the first boot of the operating system. Examples of scripts can be found in the User data instruction;
• <server_name> — server name.

5. Move additional disks⁠

If additional disks are used on the original cloud server, you can migrate them.

1. Create images of additional disks.

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

3. Create network disks from the images.

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

6. Create a public IP address for the server⁠

Control panel

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

2. Go to the Network section.

3. Open the Public IP Addresses tab.

4. Click Create IP Address.

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

6. Specify the number of public IP addresses.

7. Click Create.

OpenStack CLI

1. Open the OpenStack CLI.

2. Create a public IP address:

   openstack floating ip create external-network

Transfer the disk directly

1. Look at the name and type of boot disk of the source cloud server.

2. Create a target cloud server.

3. Transfer the disk of the source cloud server.

4. If additional disks are used on the source server, migrate them and connect them to the target cloud server.

1. View the name and type of the boot disk⁠

1. In the dashboard, 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 the Local Disk field, the server has a bootable local disk.

4. Open the Network Disks tab. If there is a Bootable tag in the disk line, the server has a bootable network disk.

2. Create a target server⁠

Control panel

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

2. Click Create Server.

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

4. Select a pool segment.

5. Click on the default source name.

6. Select the source from which the server will be created. The boot type of the source (BIOS or UEFI) must match the boot type of the source server.

7. Press Select.

8. Select a cloud server configuration:

   • fixed — lines with different vCPU to RAM ratios up to 48 vCPUs, 320 GB of RAM, and 1.25 TB of local disk capacity;
   • arbitrary — select any resource ratio up to 32 vCPUs, 256 GB RAM and 2 TB of local disk space.

   Different configurations and server lines use different processors depending on the pool segment. You can add GPUs to the configurations — more details in the Create a cloud server with GPU instructions.

   After the server is created, you can change the configuration.

   The amount of RAM that is allocated to the server may be less than the specified amount — the operating system kernel reserves some RAM depending on the kernel version and distribution. You can check the allocated amount on an existing server with sudo dmesg | grep Memory.

9. Select the server boot (system) disk:

   • local disk without network latency — check the box Local SSD NVMe disk. If you have selected an arbitrary configuration, specify the local disk size. If you selected fixed, the disk size will depend on the configuration;
   • or network disk — in the Disk Type field, select the type of disk and specify its size.

   The disk must be at least as large as the disk size of the source server.

   Once the server is created, only the network boot disk can be replaced.

10. Click Add.

11. Optional: To add an additional disk to the server, click Add. Multiple disks can be added.

    After the server is created, you can disconnect additional disks from the server and connect new disks.

    You can migrate additional disks that were attached to the source server.

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

    Existing private subnet

    12.1 Click Private Subnet.

    12.2. In the Public IP Address for Internet Access field, select New Public IP Address.

    12.3. Expand the block with private subnet settings.

    12.4. In the Subnet field, select an existing subnet.

    12.5. In the Private IP field, specify the private IP address of the server. The public IP address will be automatically connected to the private address.

    New private subnet

    12.1 Click Private Subnet.

    12.2. In the Public IP Address for Internet Access field, select New Public IP Address.

    12.3. Expand the block with private subnet settings.

    12.4. If you have existing networks in the project, select New Subnet in the Subnet field.

    12.5 Optional: Change the CIDR of the subnet.

    12.6 Optionally: enable the DHCP toggle switch.

    12.7. Optional: in the Gateway field, change the IP address of the default gateway.

    12.8. In the Network field, select the existing network where the subnet will be created or New network. For a private subnet with a public IP address, router-<network_name>, where <network_name> is the network name, will be automatically created.

    12.9. If you selected New Network, enter the name of the network.

13. Select security groups to filter traffic on server ports. Without security groups, traffic will not be allowed. If there is no block, port security is disabled on the server network . With traffic filtering disabled, all traffic will be allowed.

14. To securely connect to the server, place an SSH key on the server. Multiple keys can be added. The supported key types are ed25519, rsa, ecdsa, and dsa.

    Select an existing key or click Add SSH Key. Enter a key name and insert a public SSH key in OpenSSH format. Click Add.

    If SSH keys are not created, generate them.

15. Optional: Copy and save the password of the root user (a user with unlimited rights to all actions on the system). Store the password in a safe place and do not share it in plaintext.

16. Optional: To create an interruptible server, check the Interruptible Server checkbox.

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

    Select an existing placement group or click Create Group and enter a 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 when creating a server, it will be created on the same host;
    • necessarily on different hosts — anti-affinity, servers in a group are necessarily located on different hosts. If we do not find a suitable host, the server will not be created.

    Once a server is created, it cannot be added to the group directly — only by creating a copy.

18. Optional: to add additional information to the server or filter the servers in the list, add a tag. Multiple tags can be added. Operating system and configuration tags are automatically added.

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

19. Optional: in the User data field, insert or upload a script that will be executed at system startup. The maximum size of a script with non-Base64 encoded data is 16 KB. Examples of scripts and supported formats can be found in the User data instruction.

20. Click Create Server.

OpenStack CLI

1. Open the OpenStack CLI.

2. Create a cloud server:

   openstack server create \
       [--image <image> | --volume <volume> | --snapshot <snapshot>] \
       --flavor <flavor> \
       --availability-zone <pool_segment> \
       --nic net-id=<net_uuid> \
       --security-group <security_group> \
       --key-name <key_name> \
       <server_name>

   Specify:

   • source type:
     • --image <image> — to create a server from off-the-shelf or custom image. Parameter <image> — ID or name of the image. The list of images can be viewed with the command openstack image list;
     • --volume <volume> — to create a server from network disk. Parameter <volume> — ID or disk name. You can view the list of network disks with the command openstack volume list;
     • --snapshot <snapshot> — to create a server from snapshot. Parameter <snapshot> — ID or name of the snapshot. The list of snapshots can be viewed with the command openstack snapshot list;
   • <flavor> — The ID or name of the flavor. The flavors correspond to cloud server configurations and determine the number of vCPUs, RAM, and local disk size (optional) of the server. You can use fixed configuration flavors or create a flavor. For example, 4011 — ID to create a Memory Line fixed configuration server with 2 vCPUs, 16 GB RAM in a ru-9 pool. You can view the list of flavors using the command openstack flavor list or in the table List of fixed configuration flavors in all pools;
   • <pool_segment> — pool segment in which the cloud server will be created, e.g. ru-9a. The list of available pool segments can be found in the instructions. Availability matrices;
   • <net_uuid> — ID of the private or public network to which the server will be connected. The list can be viewed with the command openstack network list;
   • <security_group> — The ID or name of the security group that will be assigned to all ports on the server. To create a server with a security group, the network must have port security enabled. port security. The list of groups can be viewed with the command openstack security group list;
   • <key_name> — name of the SSH key pair for the service user. If SSH keys are not created, generate them. The list can be viewed with the command openstack keypair list;
   • optional: --block-device-mapping vdb=<extra_volume> — ID or name of the extra disk. The list can be viewed using the openstack volume list command;
   • optional: --tag <tag_name> --os-compute-api-version 2.52 — tag to add more information about the server;
   • optional: --tag preemptible --os-compute-api-version 2.72 — tag to create an interruptible server;
   • optional: --user-data <user_data.file> — path to the script with Base64 encoded data. Scripts and tasks from the script will be executed at the first boot of the operating system. Examples of scripts can be found in the User data instruction;
   • <server_name> — server name.

3. Transfer the source server disk to the destination server⁠

1. Connect to the target server.

2. Look up the boot disk ID, to do this, bring up the disk information:

   lsblk

   The response will show information about the server disks. The value /boot/efi in the MOUNTPOINTS column indicates the boot disk. For example:

   NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
   sda         8:0      0 931.5G  0 disk 
   └─sda1      8:1      0 931.5G  0 part /mnt/data
   nvme0n1     259:0    0 465.8G  0 disk 
   ├─nvme0n1p1 259:1    0   512M  0 part /boot/efi
   ├─nvme0n1p2 259:2    0    16G  0 part [SWAP]
   └─nvme0n1p3 259:3    0 449.3G  0 part /

   Here nvme0n1 is the disk ID.

3. Copy the boot disk ID you got in step 2.

4. Boot the source server in Rescue mode.

5. Connect to the source cloud server.

6. Look at the disk IDs, to do this, bring up the disk information:

   lsblk

   The response will show information about the server disks. The value /boot/efi in the MOUNTPOINTS column indicates the boot disk. For example:

   NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
   sda           8:0    0   1.8T  0 disk 
   └─sda1        8:1    0   1.8T  0 part /mnt/data
   sdb           8:16   0 931.5G  0 disk 
   └─sdb1        8:17   0 931.5G  0 part /mnt/backup
   nvme0n1     259:0    0 465.8G  0 disk 
   ├─nvme0n1p1 259:1    0   512M  0 part /boot/efi
   ├─nvme0n1p2 259:2    0    16G  0 part [SWAP]
   └─nvme0n1p3 259:3    0 449.3G  0 part /

   Here nvme0n1 is the disk ID.

7. Copy the boot disk ID that you obtained in step 6.

8. Transfer the disk to the target server:

   ssh root@NEW-IP '> /dev/<target_disk_id>' < /dev/<source_disk_id>

   Specify:

   • <target_disk_id> — The disk identifier of the target server. The target server's drive letter can be the same as the source server's drive letter;
   • <source_disk_id> — the disk ID of the source server.

4. Move additional disks⁠

If additional disks are used on the original cloud server, you can migrate them.

1. Create images of additional disks.

2. Transfer the additional disk images to the account, project, or pool segment to which you migrated the source cloud server disk.

3. Create network disks from the images.

4. Connect the network disks to the target cloud server.