If you are using the Linux-based Plug-in Offline Client and you are migrating a physical server to a virtual environment in which the Client is Windows-based, install the disk drivers on the OS before you back up the machine. The restored VM does not boot up because the restored image contains SCSI/IDE drivers for the source physical machine. The restored VM does not have the drivers for the target VM’s SCSI/IDE controller. This issue causes a blue screen error and the boot fails, as it cannot find any disks.
The solution is to create the “.inf” file that informs the Windows installer to load the appropriate drivers to the system and make correct registry entries every time Windows boots. Installation of the “.inf” file is required prior backing up the physical machine so that after the restore, the correct driver is loaded and detects the VMware IDE/SCSI controller.
Quest provides the following device driver “.inf” files:
• |
“vm_ide_2012.inf”: IDE device driver for Windows Server 2012 and later |
• |
“vm_lsi_2012.inf”: SCSI device driver for Windows Server 2012/2012 R2 and later |
NOTE: The device driver must be installed on the source (physical) machine, but the type of device driver must match the target (virtual) machine. For example, to migrate a Windows Server 2012 physical machine with a SATA driver to a VM with a SCSI driver, install “vm_lsi_2012.inf” on the physical machine. For all supported configurations, see Supported physical to virtual configurations. |
You can download the device driver “.inf” files from the Quest website.
1 |
Copy the required device driver, for example, “vm_ide_2012.inf,” to the physical machine. |
2 |
Locate the file on the physical machine, right-click it, and select Install from the menu. |
3 |
The following configurations are currently supported for Windows Server 2012 (32/64-bit) and later.
In some instances of using the Windows PE-based Plug-in Offline Client, the logical unit numbers (LUNs) of a Fibre Channel card are identified as drives by the Windows Disk Manager. As a result, NetVault might also interpret the LUNs as drives, display them on the NetVault Selections page, and attempt to include them in a backup job if they are selected. The VSS Backup job then fails because of this issue. To work around this issue, you can edit the “nvdrw.cfg” file to prevent the LUNs from appear on the NetVault Selections page.
1 |
Locate and open the “nvdrw.cfg” file in a text editor. |
4 |
For the Plug-in Offline Client, complete the following steps to restart the drdaemon: |
b |
In the Windows Task Manager screen, select the Processes tab, right-click drdaemon, select End Process, and close the Task Manager. |
c |
To restart the drdaemon, type the following at a command prompt; if necessary, click Launch CMD again; and press Enter: |
5 |
For the Plug-in Live Client, access the Windows Task Manager on the NetVault Bare Metal Recovery Client, select the Processes tab, right-click nvdrw, select End Process, and close the Task Manager. |
6 |
Access the NetVault Selections page of the NetVault Backup window, and verify that the changes are reflected. |
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center