Previous Topic: After BMR, dynamic volumes are not recognized by the operating systemNext Topic: Unable to Reboot VMware VM After BMR

Restoring Protected Data › How to Perform a BMR Using a Backup › Troubleshooting BMR Issues › Unable to Reboot Hyper-V VM After BMR

Unable to Reboot Hyper-V VM After BMR

If you performed BMR to a Hyper-V machine consisting of more than one disk connected to an Integrated Drive Electronics (IDE) controller and if the server does not reboot, perform the following troubleshooting procedure:

  1. Verify that the disk that contains the system volume is the master disk.

    The Hyper-V BIOS searches for the system volume on the master disk (disk 1) which is connected to the master channel. If the system volume is not located on the master disk, the VM will not reboot.

    Note: Verify that the disk that contains the system volume is connected to an IDE controller. Hyper-V cannot boot from a SCSI disk.

  2. If necessary, modify the Hyper-V settings, to connect the disk that contains the system volume to the IDE master channel and reboot the VM again.

If the problem persists, use Live Chat to contact Arcserve Support. Live Chat lets you optimize intelligent conversation between you and the Technical Support team, allowing you to address your concerns and questions immediately, while still maintaining access to the product.