Recovering an external VM or server from a backup
Note
You cannot restore a VM backup to a server or a server backup to a VM. However, you can restore an external server backup to a Yandex BareMetal server.
To avoid errors when restoring from a backup, start by comparing the disks and partitions of the backup against those of the VM or server you are restoring to. For more information, see Viewing the parameters of backup disks and partitions.
To recover a VM or server located in your infrastructure or a third-party provider's infrastructure from a backup:
- Start the recovery process on the Yandex Cloud side.
- Make sure you have network access on the resource side.
Start the recovery process on the Yandex Cloud side
- In the management console
, select the folder containing the backup. - Navigate to Cloud Backup.
- In the left-hand panel, select
Backups. - Depending on the type of resource you want to recover, open the External virtual machines or External servers tab.
- In the line with the backup you want to use to recover an external VM or server, click
and select Restore VM. - In the Restoring from a backup window that opens, select the external resource the backup will be recovered to in the Target resource field.
- Click Restore.
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.
-
See the description of the CLI command to restore a resource from a backup:
yc backup backups recover --help -
Get the ID of the backup:
yc backup backups listResult:
+--------------------------------------+--------------------------------------+----------------------+--------------------------------------+----------------------+------+------------------+--------+---------------------+ | ID | ARCHIVE ID | COMPUTE INSTANCE ID | RESOURCE ID | POLICY ID | TYPE | DISKS | SIZE | CREATED AT | +--------------------------------------+--------------------------------------+----------------------+--------------------------------------+----------------------+------+------------------+--------+---------------------+ | ab55286e-795f-44dc-90af-b718******** | ef3e8144-fb65-6a59-5ec1-3162******** | jklp0o9i8012******** | 2465BE59-5687-4539-9589-DF7E******** | abc7n3wln123******** | FULL | Disk 1 (15.0 GB) | 1.5 GB | 2023-07-07 16:00:15 | | cd50e147-7dfa-449f-816b-67f8******** | gh06b195-c095-1234-7809-0700******** | mnoa5s6d8345******** | 135C519D-B5A3-4781-8DFA-40B3******** | deflqbiwc456******** | FULL | Disk 1 (15.0 GB) | 1.6 GB | 2023-07-03 10:00:10 | +--------------------------------------+--------------------------------------+----------------------+--------------------------------------+----------------------+------+------------------+--------+---------------------+ -
Get the ID of the resource to restore:
yc backup vm listResult:
+----------------------+--------------------------------------+--------+---------+--------+-----------------+----------------+---------------------+---------------------+--------+---------------------+---------------------+-------------+ | INSTANCE ID | RESOURCE ID | ONLINE | ENABLED | STATUS | STATUS PROGRESS | STATUS DETAILS | LAST BACKUP TIME | NEXT BACKUP TIME | ACTIVE | CREATED AT | UPDATED AT | TYPE | +----------------------+--------------------------------------+--------+---------+--------+-----------------+----------------+---------------------+---------------------+--------+---------------------+---------------------+-------------+ | ly5mzirn6xhd******** | 4fc0d855-b76c-****-99a4-bf01******** | true | true | IDLE | 0 | | | | true | 2026-04-29 05:45:34 | 2026-04-29 05:54:21 | BMS | | epd930eo5156******** | 6c58577d-409d-****-bc10-f464******** | true | true | IDLE | 0 | | | | true | 2026-04-29 08:46:47 | 2026-04-29 08:54:00 | COMPUTE | | cdgd246kiae3******** | d1fdd342-0ea8-****-9906-fa6c******** | false | true | IDLE | 0 | | 2026-04-27 13:07:05 | 2026-04-27 13:07:05 | true | 2026-04-24 14:23:06 | 2026-04-29 08:54:33 | EXTERNAL_VM | +----------------------+--------------------------------------+--------+---------+--------+-----------------+----------------+---------------------+---------------------+--------+---------------------+---------------------+-------------+ -
Recover a VM or server from a backup:
yc backup backups recover \ --source-backup-id <backup_ID> \ --destination-instance-id <external_resource_ID>Where:
--source-backup-id: ID of the backup to recover the VM or server from.--destination-instance-id: ID of the VM or server to recover the backup to.
For more information about this command, see the CLI reference.
Use the startRecovery REST API method for the Backup resource or the BackupService/StartRecovery gRPC API call.
This will start recovery of the external resource from a backup.
Note
If you are using LVM
Make sure you have network access on the resource side
To be recovered from Yandex Cloud Backup backups, external VMs and servers need to have internet access. During the process of recovering an external resource from a backup, it will be restarted and the Recovery Bootable Media tool will be started on it. Make sure your VM or server has internet access in this mode.
If necessary, configure network access in the Recovery Bootable Media tool. Proceed as follows:
- In the top menu, click Tools and, depending on the interface you are using, select
Configure networkorWi-Fi settings. - In the window that opens, configure the settings and make sure you have an internet connection.