The procedure for recovering a backup to the original VM is as follows:

1. Obtain the VM configuration from the backup.
2. Call the VM status query API to obtain the status of VM A.
3. Call the VM edit API to recover the backup configuration, such as group, CPU, and memory. The run location and datastore cannot be modified.
4. Call the VM edit API to recover the backup configuration, such as disk QoS.
5. Call the VM edit API to recover the backup configuration, such as NIC MAC address.
6. If a BIOS file exists, call the file upload API to recover the BIOS file.
7. If a TPM file exists, call the file upload API to recover the TPM file.
8. Call the backup resource creation API to lock VM A with the type set to "Recovery" to the original VM.
9. Recover data of the existing disks, the recovery workflow is the same as "Recover to a New VM".

10. Release backup resources.
11. Power on the VM (optional).

Note:

1. Data can be recovered only when the VMs are shut down.
2. Third-party backup vendors are responsible for the recovery effect. For example, if the VM has 2 disks, and backups to be recovered exist in 3 disks, third-party backup vendors can choose to add a disk before recovery or recover data of the existing 2 disks only.
3. For encrypted VMs, when the backup data is in ciphertext, it can only be recovered to the original VM in the original cluster. Otherwise, the VM fail to be powered on.