Move the disk

Last update: April 16 2025

Move the disk

The only thing that can be transferred network disk:

• to another segment of the pool any availability zone and any region — you can choose another project or account when migrating;
• to another project or account — only within one segment of the pool.

Move the disk to another segment of the pool⁠

To move a disk to another pool segment You need to create an image of the disk, transfer the image and create a new disk from it. It is not possible to directly transfer a disk to another pool segment.

When transferring a disk image, you can select a different project or an account.

1. Create a disk image.
2. Transfer the image to another segment of the pool.
3. Create a disk from the image.

Transfer the disk to another project or account⁠

Move a network drive to another project or account can only be within the same pool segment. You can migrate a single disk or several at once.

Control panel

Move one disk⁠

1. Disconnect the disk from the cloud server.
2. In control panel from the top menu, press Products and select Cloud servers.
3. Go to the section Disks.
4. On the menu of the disk, select Transfer to another project.
5. Click Start transferring. The disk will enter the status AWAITING-TRANSFER and will be unavailable for work. In the window that opens, the data for completing the migration — the migration ID and Key — will appear.
6. Optional: to cancel the transfer at any time (put the disk back in status) ACTIVE), in the menu of the disk, select Transfer control and press Cancel the postponement.
7. In the adjacent browser tab, open the project to which you want to move the disk.
8. Go to the section Cloud platform → Disks. Make sure you open the list of disks in the same pool segment from which the disk is being migrated.
9. On the menu of the section header, select Accept disks from another project.
10. In the window that opens, enter the Transfer ID and Key that you received in step 5. Click Accept.

Transfer multiple disks⁠

1. Disconnect the disk from the cloud servers.
2. in control panels from the top menu, press Products and select Cloud servers.
3. Go to the section Disks.
4. On the menu of the section header, select Move disks to another project.
5. Select the desired disks and click Download the list. A JSON file with the data to be transferred will be downloaded to your computer. The disks will go to the status AWAITING-TRANSFER and will be unavailable for work.
6. Optional: to cancel the transfer at any time (put the disk back in status) ACTIVE), in the menu of the disk, select Transfer control and press Cancel the postponement.
7. In the adjacent browser tab, open the project to which you want to migrate disks.
8. Go to the section Cloud platform → Disks. Make sure that you open a list of disks from the same pool segment from which the disks are being migrated.
9. On the menu of the section header, select Accept disks from another project.
10. In the window that opens, open the tab Multiple disks.
11. Click Download the list and attach the JSON file you received in step 4. A list of disks to migrate will appear.
12. Check the list of disks. Press Accept.

OpenStack CLI

1. Open the OpenStack CLI.

2. Disconnect the disk from the cloud server:

   openstack server remove volume <server> <volume>

   Specify:

   • <server> — ID or server name. The list can be viewed with openstack server list
   • <volume> — ID or disk name. The list can be viewed with openstack volume list

3. Create a request to move the disk to another project:

   openstack volume transfer request create <volume>

4. If you want to transfer multiple disks at once, enter:

   openstack volume transfer request create <volume_1> <volume_2> <volume_3>

5. Save from the output of the command:

   • auth_key — key value;
   • id — Transfer ID.

6. Optional: to cancel the transfer, delete the request:

   openstack volume transfer request delete <id>

7. Configure authorization in the OpenStack CLI for another project.

8. Confirm the transfer:

   openstack volume transfer request accept --auth-key <auth_key> <id>