When restoring a BIOS boot environment backup to a new virtual machine on a Hyper-V host using HyperRecovery, the OS fails to boot.

Details

The OS fails to boot when restoring a BIOS boot environment backup to a new virtual machine on a Hyper-V host using HyperRecovery. 

Conditions
・ActiveImage Protector 2022 7.5.0.9448 with Update Patch 25.3.24.1 (Agent Version 7.5.1.9530) is applied.
・A BIOS boot environment backup (Linux/Windows) is used.
・Hyper-V is chosen as the hypervisor in HyperRecovery, and the backup is restored to a new virtual machine. 
As a result, the recovery completes successfully, but the virtual machine stops at a window and the OS fails to boot.

Causes

This issue occurred because the vhd/vhdx containing the OS was attached to the virtual machine via the SCSI controller. This is a known issue.

Workaround

Use the following operating procedures:

1) Go to Hyper-V Manager and shut down the target guest.
2) Right click on the target guest and open the Setting window.
3) Select the hard drive connected to the SCSI controller and click [Delete].

4) The "vhdx" on the SCSI controller will be crossed out and the settings deleted, but the actual vhd/vhdx file remains. Please note the path of the virtual hard disk.

5) Click "IDE controller 0" and click [Add] while the hard drive is highlighted.

6) The window is displayed as follows. Click [Reference].

7) Open Explorer and browse to the vhd/vhdx file containing the OS from step 4).   

8) Click [OK].

9) The guest OS can boot up.

Target Product

- ActiveImage Protector 2022 Version 7.5.1.9530

(45628912423321)