Moving a VM to a different availability zone

1. Stop all disk write operations in applications.

2. Write the OS cache to the disk:

   sync
   

3. Freeze the file system:

   sudo fsfreeze --freeze <mount_point>
   

   Where --freeze is the parameter to freeze the file system. Instead of <mount_point>, specify the folder the file system is connected to, e.g., /mnt/vdc2.

4. Create a snapshot following the guide below.

5. Unfreeze the file system:

   sudo fsfreeze --unfreeze <mount_point>
   

   Where --unfreeze is the parameter to unfreeze the file system. Instead of <mount_point>, specify the folder the file system is connected to, e.g., /mnt/vdc2.

1. In the management console, select the folder containing the disk.

2. Select Compute Cloud.

3. In the left-hand panel, select Disks.

4. In the row with the disk, click and select Create snapshot.

5. Enter a name for the snapshot. The naming requirements are as follows:

   • The name must be from 3 to 63 characters long.
   • It may contain lowercase Latin letters, numbers, and hyphens.
   • The first character must be a letter and the last character cannot be a hyphen.

6. If necessary, enter a description of the snapshot.

7. Click Create.

1. In the management console, select the folder to create your VM in.

2. In the list of services, select Compute Cloud.

3. In the left-hand panel, select Virtual machines.

4. Click Create virtual machine.

5. Under Boot disk image:

   • Go to the Custom tab.
   • Click , and, in the window that opens, select Create new.
   • In the Contents field, select Snapshot and then select the disk snapshot you need from the list below. Use filters if you need to.
   • Enter a name for the new boot disk.
   • Select the disk type.
   • Specify the required disk and block size.
   • (Optional) In the Additional field, enable Delete along with the virtual machine if you need to automatically delete this disk when deleting the VM.
   • Click Add disk.

6. Under Location, select an availability zone to place your VM in.

7. Add a secondary disk:

   • Under Disks and file storages, click Add.
   • In the window that opens, select Disk → Create new.
   • In the Contents field, select Snapshot.
   • Enter a name for the new disk.
   • Select the disk type.
   • Specify the required disk and block size.
   • (Optional) In the Additional field, enable Delete along with the virtual machine if you need to automatically delete this disk when deleting the VM.
   • Click Add disk.

8. (Optional) To encrypt a boot disk or a secondary disk, under Disks and file storages, click to the right of the disk name and configure encryption parameters for the disk:

   • Select Encrypted disk.
   • In the KMS key field, select the key to encrypt the disk with. To create a new key, click Create new key.

   Warning

   You can specify encryption settings only when creating a disk. You cannot disable or change disk encryption.

   If you deactivate the key used to encrypt a disk, image, or snapshot, access to the data will be suspended until you reactivate the key.

   Alert

   If you destroy the key or its version used to encrypt a disk, image, or snapshot, access to the data will be irrevocably lost. Learn more in Destroying key versions.

9. (Optional) Connect a file storage:

   • Under Disks and file storages, click Add.

     • In the window that opens, select File storage and select the storage you want to connect from the list.

     • Click Add file storage.

10. Under Computing resources, select a preset configuration or create a new one. To create a configuration:

    • Go to the Custom tab.
    • Choose a platform.
    • Specify the guaranteed share and required number of vCPUs, as well as RAM size.
    • Enable a software-accelerated network if needed.
    • If required, make your VM preemptible.

11. Under Network settings:

    • In the Subnet field, enter the ID of a subnet in the new VM’s availability zone. Alternatively, you can select a cloud network from the list.

      • Each network must have at least one subnet. If there is no subnet, create one by selecting Create subnet.

      • If you do not have a network, click Create network to create one:

        • In the window that opens, enter the network name and select the folder to host the network.
        • (Optional) Select the Create subnets option to automatically create subnets in all availability zones.
        • Click Create network.

    • In the Public IP field, choose a method for assigning an IP address:

      • Auto: Assign a random IP address from the Yandex Cloud IP address pool. In this case, you can enable DDoS protection using the option below.
      • List: Select a public IP address from the list of previously reserved static addresses. For more information, see Converting a dynamic public IP address to static.
      • No address: Not to assign a public IP address.

    • Select the appropriate security groups. If you leave this field empty, the default security group will be assigned to the VM.

    • Expand the Additional section and select a method for internal IP address assignment in the Internal IPv4 address field:

      • Auto: Assign a random IP address from the pool of IP addresses available in the selected subnet.
      • Manual: Manually assign a private IP address to the VM.
      • Enable the DDoS protection option, if needed. The option is available if you previously selected the automatic IP assignment method in the public address settings.

    • (Optional) Create records for the VM in the DNS zone:

      • Expand the DNS settings for internal addresses section and click Add record.
      • Specify the zone, FQDN, and TTL for the record. When setting the FQDN, you can select Detect automatically for the zone.
        You can add multiple records to internal DNS zones. For more information, see Cloud DNS integration with Compute Cloud.
      • To create another record, click Add record.

    If you want to attach an additional network interface to your VM, click Add network interface and repeat the settings from this step for the new interface. You can add up to eight network interfaces to a single VM.

12. Under Access:

    • Select Access by OS Login to connect and manage access to the new VM using OS Login in Yandex Cloud Organization.

      With OS Login, you can connect to VMs using SSH keys and SSH certificates via a standard SSH client or the Yandex Cloud CLI. OS Login allows you to rotate the SSH keys used to access VMs, providing the most secure access option.

    • If you prefer not to use OS Login, select SSH key and specify the following info for VM access:

      • Under Login, enter the username.

        Alert

        Do not use root or other usernames reserved by the OS. To perform operations requiring superuser permissions, use the sudo command.

      • In the SSH key field, select the SSH key saved in your organization user profile.

        If there are no saved SSH keys in your profile, or you want to add a new key:

        • Click Add key.
        • Enter a name for the SSH key.
        • Upload or paste the contents of the public key file. You need to create a key pair for the SSH connection to a VM yourself.
        • Click Add.

        The SSH key will be added to your organization user profile.

        If users cannot add SSH keys to their profiles in the organization, the added public SSH key will only be saved to the user profile of the VM being created.

    If you want to add several users with SSH keys to the VM at the same time, specify these users' data under Metadata. You can also use metadata to install additional software on a VM when creating it.

    In public Linux images provided by Yandex Cloud, the functionality of connecting over SSH using login and password is disabled by default.

13. Under General information, specify the VM name:

    • The name must be from 3 to 63 characters long.
    • It may contain lowercase Latin letters, numbers, and hyphens.
    • The first character must be a letter and the last character cannot be a hyphen.

    Note

    The VM name is used to generate an internal FQDN only once: when creating a VM. If the internal FQDN is important to you, choose an appropriate name for the VM at the creation stage.

14. Under Additional:

    • (Optional) Select or create a service account. With a service account, you can flexibly configure access rights for your resources.

    • (Optional) Grant access to the serial console.

    • (Optional) Under Backup, enable Connect and select or create a backup policy to back up your VMs automatically using Cloud Backup.

      For more information, see Connecting Compute Cloud VMs and Yandex BareMetal servers to Cloud Backup.

    • (Optional) Under Monitoring, enable the Agent for delivering metrics option to configuire delivery of metrics to Yandex Monitoring.

    • (Optional) Under Placement, select a VM placement group.

15. Click Create VM.

You will see the new VM in the list. Every new VM gets an IP address and host name (FQDN).

1. In the management console, select the folder the VM belongs to.

2. Select Compute Cloud.

3. In the row with the VM you need, click → Delete.

   To delete multiple VMs, select the VMs you need to delete in the list and click Delete at the bottom of the screen.

4. In the window that opens, click Delete.

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

1. See the description of the CLI command for moving a VM to a different availability zone:

   yc compute instance relocate --help
   

2. Get a list of all subnets in the default folder:

   yc vpc subnet list
   

   Result:

   +----------------------+-----------------------+----------------------+----------------+---------------+-------------------+
   |          ID          |         NAME          |      NETWORK ID      | ROUTE TABLE ID |     ZONE      |       RANGE       |
   +----------------------+-----------------------+----------------------+----------------+---------------+-------------------+
   | bucqps2lt75g******** | subnet-ru-central1-a1 | c64pv6m0aqq6******** |                | ru-central1-a | [192.168.11.0/24] |
   | e2lrucutusnd******** | subnet-ru-central1-a2 | c64pv6m0aqq6******** |                | ru-central1-a | [192.168.12.0/24] |
   | e2lv9c6aek1d******** | subnet-ru-central1-a3 | c64pv6m0aqq6******** |                | ru-central1-a | [192.168.13.0/24] |
   | bltign9kcffv******** | default-ru-central1-b | c64pv6m0aqq6******** |                | ru-central1-b | [192.168.1.0/24]  |
   +----------------------+-----------------------+----------------------+----------------+---------------+-------------------+
   

3. Get a list of all security groups in the default folder:

   yc vpc sg list
   

   Result:

   +----------------------+---------------------------------+--------------------------------+----------------------+
   |          ID          |              NAME               |          DESCRIPTION           |      NETWORK-ID      |
   +----------------------+---------------------------------+--------------------------------+----------------------+
   | c646ev94tb6k******** | my-sg-group                     |                                | c64pv6m0aqq6******** |
   | c64r84tbt32j******** | default-sg-c64pv6m0aqq6******** | Default security group for     | c64pv6m0aqq6******** |
   |                      |                                 | network                        |                      |
   +----------------------+---------------------------------+--------------------------------+----------------------+
   

4. Get a list of all VMs in the default folder:

   yc compute instance list
   

   Result:

   +----------------------+---------+---------------+---------+---------------+-------------+
   |          ID          |  NAME   |    ZONE ID    | STATUS  |  EXTERNAL IP  | INTERNAL IP |
   +----------------------+---------+---------------+---------+---------------+-------------+
   | a7lh48f5jvlk******** | my-vm-1 | ru-central1-a | RUNNING |               | 192.168.0.7 |
   | epdsj30mndgj******** | my-vm-2 | ru-central1-b | RUNNING |               | 192.168.1.7 |
   +----------------------+---------+---------------+---------+---------------+-------------+
   

5. Get a list of network interfaces of the VM in question by specifying the VM ID:

   yc compute instance get <VM_ID>
   

   Result:

   ...
   network_interfaces:
     - index: "0"
       mac_address: d0:0d:24:**:**:**
       subnet_id: bucqps2lt75g********
       primary_v4_address:
         address: 192.168.11.23
         one_to_one_nat:
           address: 158.160.**.***
           ip_version: IPV4
     - index: "1"
       mac_address: d0:1d:24:**:**:**
       subnet_id: e2lrucutusnd********
       primary_v4_address:
         address: 192.168.12.32
     - index: "2"
       mac_address: d0:2d:24:**:**:**
       subnet_id: e2lv9c6aek1d********
       primary_v4_address:
         address: 192.168.13.26
   ...
   

6. Move the VM to a different availability zone:

   yc compute instance relocate <VM_ID> \
     --destination-zone-id <availability_zone_ID> \
     --network-interface subnet-id=<subnet_ID>,security-group-ids=<security_group_ID>
   

   Where:

   • <VM_ID>: ID of the VM to move to a different availability zone.

   • --destination-zone-id: ID of the availability zone to move the VM to.

   • --network-interface: VM network interface settings:

     • subnet-id: ID of the subnet in the availability zone to move the VM to.
     • security-group-ids: ID of the security group to link to the VM you are moving. You can link multiple security groups to a single VM by providing a comma-separated list of security group IDs in [id1,id2] format.

     If a VM has multiple network interfaces, specify the --network-interface parameter as many times as needed (for each network interface).

   For more information about the yc compute instance relocate command, see the CLI reference.

   Here is an example:

   yc compute instance relocate a7lh48f5jvlk******** \
     --destination-zone-id ru-central1-b \
     --network-interface \
       subnet-id=bltign9kcffv********,security-group-ids=c646ev94tb6k********
   

   In this example, we are moving a VM named my-vm-1 from the ru-central1-a availability zone to ru-central1-b.

   Result:

   done (3m15s)
   id: a7lh48f5jvlk********
   folder_id: aoeg2e07onia********
   created_at: "2023-10-13T19:47:40Z"
   name: my-vm-1
   zone_id: ru-central1-b
   platform_id: standard-v3
   resources:
     memory: "2147483648"
     cores: "2"
     core_fraction: "100"
   status: RUNNING
   metadata_options:
     gce_http_endpoint: ENABLED
     aws_v1_http_endpoint: ENABLED
     gce_http_token: ENABLED
     aws_v1_http_token: DISABLED
   boot_disk:
     mode: READ_WRITE
     device_name: a7lp7jpslu59********
     auto_delete: true
     disk_id: a7lp7jpslu59********
   network_interfaces:
     - index: "0"
       mac_address: d0:0d:11:**:**:**
       subnet_id: bltign9kcffv********
       primary_v4_address:
         address: 192.168.1.17
       security_group_ids:
         - c646ev94tb6k********
   gpu_settings: {}
   fqdn: my-vm-1.ru-central1.internal
   scheduling_policy: {}
   network_settings:
     type: STANDARD
   placement_policy: {}
   

   If you are moving a VM with a disk in a placement group, use this command:

   yc compute instance relocate <VM_ID> \
     --destination-zone-id <availability_zone_ID> \
     --network-interface subnet-id=<subnet_ID>,security-group-ids=<security_group_ID> \
     --boot-disk-placement-group-id <disk_placement_group_ID> \
     --boot-disk-placement-group-partition <partition_number> \
     --secondary-disk-placement disk-name=<disk_name>,disk-placement-group-id=<disk_placement_group_ID>,disk-placement-group-partition=<partition_number>
   

   Where:

   • --boot-disk-placement-group-id: Disk placement group ID.

   • --boot-disk-placement-group-partition: Partition number in the disk placement group with the partition placement strategy.

   • --secondary-disk-placement: Placement policy for secondary disks. Parameters:

     • disk-name: Disk name.
     • disk-placement-group-id: ID of the disk placement group to place the disk in.
     • disk-placement-group-partition: Partition number in the disk placement group.

   For more information about the yc compute instance relocate command, see the CLI reference.

Please note that connecting VM's network interfaces to new subnets changes their IP addressing. If you need to specify internal IP addresses for the VM's network interfaces, use the ipv4-address=<internal_IP_address> property of the network-interface parameter; for public IP addresses, use the nat-address=<public_IP_address> property. Other than that, setting up network interface parameters when moving a VM to a different availability zone is similar to setting up the same parameters when creating a VM.