1 Create a Hyper-V or VMware virtual machine or edit the settings of an existing VM.
• Make sure the VM’s firmware interface type (BIOS or UEFI) matches the firmware interface type of the failed client.
• Add enough memory to satisfy Microsoft’s support guidelines for the operating system being restored. The integrated bare metal recovery ISO requires at least 1 GB of memory.
• Assign the VM a virtual hard disk with enough memory for the restore. You can restore to a disk that is smaller than the original disk, but the restore fails if the disk does not have enough space for the critical volumes.
Note: After a client has failed, there is no way to determine the size of its critical volumes. You can determine the size of a client’s backup by viewing the backup details as described in To view backup details. However, the size of the critical volumes will be smaller than the total size of a full backup if it also contains non-critical volumes. If you are unsure about the size of the critical volumes, it is recommended that you restore the failed client to destination disks that are the same size as the original disks or larger.
Caution: If you are restoring to new disks, any existing data on the destination disks is overwritten or deleted during the restore, even if the disks have more than enough space. Before performing a restore, make sure you have additional copies of any data on the destination disks. If you are restoring to the original disk, only the restored volumes are overwritten. Other volumes on the original disk are not impacted by the restore.
• For a VMware virtual machine, make sure you are using the E1000 NIC.
Note: This requirement is necessary only for the restore. After rebooting the restored client, you can use a different NIC.
• Add the bare metal ISO image to the VM’s disk drive. For instructions on accessing the ISO, see Accessing the integrated bare metal recovery ISO images.
2 Proceed to Running the Integrated Bare Metal Recovery Wizard to begin the integrated bare metal recovery.