Moving a disk 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. Replace <mount_point> with the folder where the file system is mounted, e.g., /mnt/vdc2.

4. Create a snapshot by following the steps below.

5. Unfreeze the file system:

   sudo fsfreeze --unfreeze <mount_point>
   

   Where --unfreeze is the parameter to unfreeze the file system. Replace <mount_point> with the folder where the file system is mounted, 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 line with the disk, click and select Create snapshot.

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

   • It must be 2 to 63 characters long.
   • It may contain lowercase Latin letters, numbers, and hyphens.
   • It must start with a letter and cannot end with a hyphen.

6. Provide a description for the snapshot, if required.

7. Click Create.

1. In the management console, select the folder where you want to create your VM.

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 the filter as needed.
   • Enter a name for the new boot disk.
   • Select the disk type.
   • Specify the required disk and block size.
   • Optionally, enable Additional in the Delete along with the virtual machine field if you need this disk automatically deleted when deleting the VM.
   • Click Add disk.

6. Under Location, select an availability zone for your VM.

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.
   • Optionally, enable Additional in the Delete along with the virtual machine field if you need this disk automatically deleted when deleting the VM.
   • Click Add disk.

8. Optionally, 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 you want to use to encrypt the disk. 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. For details, see Destroying key versions.

9. Optionally, connect a file storage:

   • Under Disks and file storages, click Add.

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

     • Click Add file storage.

10. Under Computing resources, select one of the preset configurations or create a custom one. To create a custom configuration:

    • Go to the Custom tab.
    • Select a platform.
    • Specify the guaranteed performance and required number of vCPUs, as well as RAM size.
    • Optionally, enable a software-accelerated network.
    • Make your VM preemptible, if required.

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 your network has no subnets, create one by selecting Create subnet.

      • If there are no networks in the list, click Create network to create one:

        • In the window that opens, specify the network name and select the folder where you want to create it.
        • Optionally, select Create subnets to automatically create subnets in all availability zones.
        • Click Create network.

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

      • Auto: To 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: To 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 relevant security groups. If you leave this field empty, the default security group will be assigned to the VM.

    • Expand Additional and select a method for assigning internal addresses in the Internal IPv4 address field:

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

    • Optionally, create records for your VM in the DNS zone:

      • Expand DNS settings for internal addresses and click Add record.
      • Specify a zone, FQDN, and TTL for the record. When setting the FQDN, you can enable 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 add another 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 enables rotating 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 VM access data:

      • Under Login, enter a username.

        Alert

        Do not use root or other usernames reserved by the OS. To perform operations requiring superuser privileges, 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 multiple 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, enter a name for the VM:

    • It must be 2 to 63 characters long.
    • It may contain lowercase Latin letters, numbers, and hyphens.
    • It must start with a letter and cannot end with a hyphen.

    Note

    The VM name is used to generate an internal FQDN, which is set only once, when you create the VM. If the internal FQDN is important to you, make sure to choose an appropriate name for your VM.

14. Under Additional:

    • Optionally, select or create a service account. With a service account, you can flexibly configure access permissions for your resources.

    • Optionally, enable access to the serial console.

    • Optionally, under Backup, enable Connect and select or create a backup policy to make automatic backups of your VMs using Cloud Backup.

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

    • Optionally, under Monitoring, enable Agent for delivering metrics to configure delivering metrics to Yandex Monitoring.

    • Optionally, under Placement, select a VM placement group.

15. Click Create VM.

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

If you do not have the Yandex Cloud CLI yet, install and initialize it.

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

1. See the description of the CLI command for moving a disk:

   yc compute disk relocate --help
   

2. Request a list of available disks:

   yc compute disk list
   

   Result:

   +----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+
   |          ID          |     NAME     |    SIZE     |       ZONE        | STATUS |     INSTANCE IDS     | PLACEMENT GROUP | DESCRIPTION |
   +----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+
   | a7lqgbt0bb9s******** | first-disk   | 20401094656 |   ru-central1-a   | READY  | a7lcvu28njbh******** |                 |             |
   | a7lv5j5hm1p1******** | second-disk  | 21474836480 |   ru-central1-a   | READY  |                      |                 |             |
   +----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+
   

3. Select ID of the disk you need.

4. Move the disk to a different availability zone:

   yc compute disk relocate --id <disk_ID> \
     --destination-zone-id <availability_zone>
   

   Where:

   • --id: ID of the disk to move.
   • --destination-zone-id: ID of the availability zone to move the disk to, e.g., ru-central1-a.

   If moving a disk in a placement group, provide the group ID in the --disk-placement-group-id parameter.