Chatta subito con l'assistenza
Chat con il supporto

NetVault Bare Metal Recovery 14.0 - User Guide for Plug-ins

Introducing NetVault Bare Metal Recovery Plug-ins Deploying NetVault Bare Metal Recovery Using the Plug-in Offline Client
Plug-in Server: an overview Installing and removing Plug-in Server Configuring Plug-in Server for use with Plug-in Offline Client Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client Backing up data with Plug-in Offline Client Restoring data with Plug-in Offline Client
Using NetVault Bare Metal Recovery Plug-in Live Client
Plug-in Live Client overview Configuring Plug-in Server for use with Plug-in Live Client Installing and removing Plug-in Live Client Backing up data with Plug-in Live Client Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client Restoring data with Plug-in Live Client
Using NetVault Bare Metal Recovery Plug-in Live Client for Linux
Plug-in Live Client for Linux: an overview Installing and removing Plug-in Live Client for Linux Generating a DR image for use with Plug-in Live Client for Linux Creating the required bootable CD for use with Plug-in Live Client for Linux Recovering a DR image for use with Plug-in Live Client for Linux
NetVault Bare Metal Recovery physical-to-virtual (P2V) recovery  Troubleshooting

Installing SCSI and IDE device drivers on a physical machine

The processes for recovering from a physical machine to a virtual machine apply only to Windows operating systems.

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
When the Hardware Installation warning message is displayed, click Continue Anyway.
4
Reboot the system for the new settings to take effect.

Supported physical to virtual configurations

The following configurations are currently supported for Windows Server 2012 (32/64-bit) and later.

 
Table 1. Supported configurations
Source (physical)
Target (VM)

IDE

IDE

IDE

SCSI

SATA

IDE

SATA

SCSI

SCSI

IDE

SCSI

SCSI

 Troubleshooting

 Troubleshooting
•
Excluding LUNs from the NetVault Selections pages
•
Performing a restore in which Disk Numbers are different from the backup
•
Access denied during MBR recovery
•
VMware ESX and ESXi Server 4.x and earlier not supported with Windows PE
•
Attaching a restored VMDK image to a VM fails to power on the machine
•
VMDK restore job to remote ESXi 6.0 fails with failure to clone error

Excluding LUNs from the NetVault Selections pages

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.

To update the file
1
Locate and open the “nvdrw.cfg” file in a text editor.
For the Plug-in Offline Client, this file is located in \\Windows\System32\. For the Plug-in Live Client, this file is located in \\NetVault\config\. If the file does not exist, you can create it.
2
Update the file to include a section similar to the following; replace the applicable segments with the information for your card:
[Disk Vendor:Product]
IgnoreDisk=LSI, Universal Xport
3
Save and close the file.
4
For the Plug-in Offline Client, complete the following steps to restart the drdaemon:
a
On the NetVault Bare Metal Recovery Client, start the Windows Task Manager by typing the following at a command prompt, and pressing Enter:
taskmgr
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:
drdaemon
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.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione