Moving a disk to a different availability zone
A disk is created in a single availability zone. You can move it to a different zone using a snapshot or CLI command.
If a disk is attached to a VM, it will be moved during VM migration. You cannot migrate attached disks separately from their VMs.
Warning
To monitor the progress of migration and avoid possible issues during it, use disk snapshots or backups from Cloud Backup for migration. In this way, you yourself determine when to shut down your VM in the source availability zone and when to make it appear in the target availability zone. The VM in the source availability zone may continue to run until you make sure that the VM you created from a snapshot works properly in the new availability zone. For detailed recommendations, see Migrating resources to the ru-central1-d availability zone.
Currently, you can use the relocate
command to migrate VMs and disks only to the ru-central1-d
zone from any other zone.
Moving a disk by creating a snapshot
Prepare the disks
A disk snapshot only contains the data that had already been written to the disk when the snapshot was created. If the disk is attached to a running VM, the OS and app cache will not be included in the snapshot.
To ensure the integrity of the snapshot data:
-
Stop all disk write operations in applications.
-
Write the OS cache to the disk:
sync
-
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
. -
Create a snapshot following the guide below.
-
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
.
- Stop the virtual machine (see Stop).
- Wait until the VM status changes to
STOPPED
.
Create snapshots
To create a disk snapshot:
-
In the management console
, select the folder where the disk is located. -
Select Compute Cloud.
-
In the left-hand panel, select
Disks. -
In the line of the disk, click
and select Create snapshot. -
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.
-
If necessary, enter a description of the snapshot.
-
Click Create.
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.
-
View a description of the CLI create snapshot commands:
yc compute snapshot create --help
-
Select the disk to take a snapshot of. To get a list of disks in the default folder, run the command:
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 | | | | +----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+
-
Create a snapshot in the default folder:
yc compute snapshot create \ --name first-snapshot \ --description "my first snapshot via CLI" \ --disk-id fhm4aq4hvq5g********
As a result, a disk snapshot is created with the name
first-snapshot
and descriptionmy first snapshot via CLI
.The snapshot 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.
If you don't have Terraform, install it and configure the Yandex Cloud provider.
-
Describe the resource parameters in the
yandex_compute_snapshot
configuration file.Here is an example of the configuration file structure:
resource "yandex_compute_snapshot" "snapshot-1" { name = "disk-snapshot" source_disk_id = "<disk_ID>" }
For more information about resources you can create with Terraform, see the provider documentation
. -
Make sure the configuration files are valid.
-
In the command line, go to the directory where you created the configuration file.
-
Run a check using this command:
terraform plan
If the configuration is described correctly, the terminal will display a list of created resources and their parameters. If the configuration contains any errors, Terraform will point them out.
-
-
Deploy cloud resources.
-
If the configuration does not contain any errors, run this command:
terraform apply
-
Confirm that you want to create the resources.
All the resources you need will then be created in the specified folder. You can check the new resources and their configuration using the management console
. -
- Get the list of disks using the list REST API method for the Disk resource or the DiskService/List gRPC API call.
- Create a snapshot using the create REST API method for the Snapshot resource or the SnapshotService/Create gRPC API call.
Repeat the steps to create a snapshot of each disk.
Create a VM in a different availability zone with the disks from the snapshots
To create a VM in a different availability zone with the disks from the snapshots:
-
In the management console
, select the folder to create the virtual machine in. -
In the list of services, select Compute Cloud.
-
At the top right, click Create virtual machine.
-
Under Basic parameters:
-
Enter a name and description for the VM. 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.
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.
-
Select an availability zone to put your virtual machine in.
-
-
Under Image/boot disk selection, choose a snapshot:
- Go to the Custom image tab and click Choose.
- In the window that opens, go to the Snapshot tab.
- Select a disk snapshot from the list and click Apply.
-
(Optional) To encrypt a boot disk, under Disks and file storages, configure encryption parameters for the disk:
- Select the Encrypted disk option.
- In the KMS Key field, select the key with which you want to encrypt the disk. To create a new key, click Create.
- In the Service account field, select the service account with the
kms.keys.encrypterDecrypter
role for the specified key. To create a service account, click Create.
The encryption feature in Compute Cloud is currently at the Preview stage. To access it, open the resource creation page and click Request access under Encryption or contact support
.If you deactivate the key used to encrypt a disk 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 or snapshot, access to the data will be irrevocably lost. Learn more in Destroying key versions.
-
Under Disks and file storages, add a disk:
-
Click Add disk.
-
Enter the disk name.
-
Select the disk type.
-
Specify the required block size.
-
Specify the required disk size.
-
(Optional) To encrypt a disk, configure encryption parameters.
-
(Optional) Enable the Delete with the VM option if you need to automatically delete the disk when deleting the VM it will be attached to.
-
Select
Snapshot
as content. -
Click Add.
-
-
(Optional) Under Disks and file storages, select the File storages tab and attach the file storage:
- Click Attach file storage.
- In the window that opens, select the file storage.
- Enter the device name.
- Click Attach file storage.
-
Under Computing resources:
- Choose a platform.
- Specify the guaranteed share and the required number of vCPUs, as well as the amount of RAM.
- If required, make your VM preemptible.
- (Optional) Enable a software-accelerated network.
-
Under Network settings:
-
Enter a subnet ID or select a cloud network from the list.
If you do not have a network, click Create network to create one:- In the window that opens, enter the network name and specify the folder to host the network.
- (Optional) To automatically create subnets, select the Create subnets option.
- Click Create.
Each network must have at least one subnet. If there is no subnet, create one by selecting Add subnet.
-
In the Public IP field, choose a method for assigning an IP address:
Auto
: Assign a random IP address from the Yandex Cloud IP pool. With this, 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
: Do not assign a public IP address.
-
In the Internal IPv4 address field, select the method for assigning internal addresses:
Auto
orManual
. -
(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.
-
Select the appropriate security groups.
-
-
(Optional) To back up your VMs automatically using Cloud Backup, under Backups, select how your VM should connect to the service.
For more information, see Connecting Compute Cloud VMs to Cloud Backup.
-
Under Access, specify the information required to access the instance:
-
(Optional) Select or create a service account. With a service account, you can flexibly configure access rights for your resources.
-
Enter the username in the Login field.
Alert
Do not use the
root
username or other names reserved by the operating system. To perform operations that require superuser permissions, use thesudo
command. -
In the SSH key field, paste the contents of the public key file.
-
If required, grant access to the serial console.
In public Linux images provided by Yandex Cloud, the functionality of connecting over SSH using login and password is disabled by default.
-
-
(Optional) Under Placement, select a VM placement group.
-
Click Create VM.
The virtual machine will appear in the list. When a VM is created, it is assigned an IP address and host name (FQDN).
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.
-
View the description of the CLI command for creating a VM:
yc compute instance create --help
-
Prepare snapshots of the required disks, see Creating a disk snapshot.
-
Get a list of snapshots in the default folder:
yc compute snapshot list
Result:
+----------------------+-----------------+----------------------+--------+----------------------------+ | ID | NAME | PRODUCT IDS | STATUS | DESCRIPTION | +----------------------+-----------------+----------------------+--------+----------------------------+ | fd8rlt1u2rf0l******* | first-snapshot | f2ecl5vhsftd******** | READY | my first snapshot via CLI | | fhmolt1u2rf0******** | second-snapshot | f2eclmol5lps******** | READY | my second snapshot via CLI | +----------------------+-----------------+----------------------+--------+----------------------------+
-
Select the
ID
s orNAME
s of the snapshots you need. -
Create a VM in the default folder:
yc compute instance create \ --name first-instance \ --zone ru-central1-a \ --public-ip \ --create-boot-disk snapshot-name=first-snapshot \ --create-disk snapshot-name=second-snapshot \ --ssh-key ~/.ssh/id_ed25519.pub
This command creates a VM named
first-instance
in theru-central1-a
availability zone, with a public IP and the disks from the snapshots.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.
To create a VM without a public IP, remove the
--public-ip
flag.
Use the create REST API method for the Instance resource or the InstanceService/Create gRPC API call.
Moving a disk using the CLI
Note
If data is being written to the disk, its move may fail. In this case, stop the disk write operation or shut down the VM and restart the move.
To attach the disk to a VM from a different availability zone, move it:
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.
-
View the description of the CLI disk move command:
yc compute disk relocate --help
-
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 | | | | +----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+
-
Select the
ID
of the appropriate disk. -
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 you need to move.--destination-zone-id
: ID of the availability zone to move the disk to, e.g.,ru-central1-a
.
If you are moving a disk in a placement group, provide the group ID in the
--disk-placement-group-id
parameter.