Downloading a copy via the management console
You can download VM disk backups not only via the management console but also with OpenStack CLI and API.
-
Go to your VK Cloud management console.
-
Go to Cloud Backup → Backup.
-
Open the required list of backup copies and select the copies to download.
Created automaticallyCreated manually-
Go to the Automatic tab.
-
Click the name of the required plan, or click
for the plan and select View backups.
-
Click the name of the required instance or the
icon.
-
Select the copies to download.
The copy name contains the disk name, the creation date and time (UTC), and the copy type: full or incremental. For example,
CentOS_Basic-1-1_10GB_03.10.2022_16:39_UTC_full. The copy type is shown in the Backups column. You can also determine it by the suffix in the name:- For full copies (the
_fullsuffix), download only this copy. - For incremental copies (the
_incrementalsuffix), download the entire chain. It includes the base full copy and all incremental copies after it, up to the one you need.
- For full copies (the
-
-
Click
for the required copy and select Download archive.
-
Download all five files for each copy.
The name of each file contains the same copy ID, which is the UUID of the backup in the Cinder service. You can use it to determine the size of the source disk via OpenStack CLI. Only the file type differs:
contentobject_segmentsvolume_segmentssha_listvolume_metadata
For more information, see Migrating VM disk backups outside VK Cloud.
-
Wait for the download to finish.
-
If the VM has several disks, repeat these steps for the copies of each disk.
-
Move the files of each copy to a separate folder.
If the name of a copy file includes an ID, remove it so that each file name contains only the file type:
contentobject_segmentsvolume_segmentssha_listvolume_metadata
The verification looks for files with these names. You can name the folders as you like. When you assemble the copy, specify the folders in the order of the chain: from the full copy to the latest incremental copy.
-
Go to Cloud Servers → Disks and make note of the size in GB of the disk whose copy you downloaded. You will need it for the assembly.
The Volume column in the list of backups shows the size of the copy, not the disk. Do not use it for the assembly.
-
Make sure that the folder of each copy contains all five files (
content,object_segments,volume_segments,sha_list, andvolume_metadata). To do this, run the command:ls -l ./<COPY_FOLDER>/Here
<COPY_FOLDER>is the folder that contains the backup copy files. -
If the
contentfile was downloaded in parts (content1,content2, and so on), join them via natural sorting:cat $(ls ./<COPY_FOLDER>/content[0-9]* | sort -V) > ./<COPY_FOLDER>/contentHere
<COPY_FOLDER>is the folder that contains the backup copy files. -
Make sure that the
contentfile was downloaded completely. To do this, take the last element in theobject_segmentsfile. Compare the sum ofobject_offsetandobject_lengthwith the size of thecontentfile:python3 -I - <<'EOF'import json, osd = "./<COPY_FOLDER>"seg = json.load(open(os.path.join(d, "object_segments")))last = seg[-1]print("by map:", last["object_offset"] + last["object_length"],"file:", os.path.getsize(os.path.join(d, "content")))EOFHere
<COPY_FOLDER>is the folder that contains the backup copy files.If the numbers do not match, the file was not downloaded completely. Download the copy again.