Introducing NetVault Bare Metal Recovery Plug-ins
NetVault Bare Metal Recovery Plug-ins: at a glance
Key benefits
Feature summary
Target audience
Recommended additional reading
Deploying NetVault Bare Metal Recovery
NetVault Bare Metal Recovery components
Using the Plug-in Offline Client
Plug-in Offline Client component
Plug-in Live Client for Windows component
Plug-in Live Client for Linux component
Plug-in Server component
VaultOS component
NetVault Bare Metal Recovery deployment scenarios
Plug-in Offline Client only x86/x86-64 clients with Windows-based NetVault Server deployment
Plug-in Offline Client only x86/x86-64 Clients with Linux-based NetVault Server deployment
Plug-in Live Client for Windows withWindows-based NetVault Server deployment
Plug-in Live Client for Windows with Linux-based NetVault Server deployment
Plug-in Live Client for Linux with Linux-based NetVault Server deployment
Plug-in Live Client for Linux with Windows-based NetVault Server deployment
Plug-in Live Client for Windows and for Linux with Linux-based NetVault Server deployment
Plug-in Live Client for Windows and for Linux with Windows-based NetVault Server deployment
Plug-in Server: an overview
Installing and removing Plug-in Server
Using NetVault Bare Metal Recovery Plug-in Live Client
Prerequisites for installing Plug-in Server
Installing or upgrading Plug-in Server
Removing Plug-in Server
Upgrading Plug-in Server
Configuring Plug-in Server for use with Plug-in Offline Client
Creating a Plug-in Offline Client Boot System
Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client
Creating a Linux-based Boot System
Creating a Windows PE-based Boot System
Creating a rescue device for use with a LiveCD
Adding a NetVault Bare Metal Recovery Client to the Plug-in Server
Booting with Plug-in Offline Client
Backing up data with Plug-in Offline Client
Using a Windows Server 2012-based virtual machine with Plug-in Offline Client for Linux
Gathering NetVault Bare Metal Recovery Client network information
Booting the NetVault Bare Metal Recovery Client with the Linux-based Plug-in Offline Client
Booting the NetVault Bare Metal Recovery Client with the Windows PE-based Plug-in Offline Client
Loading drivers dynamically
Injecting drivers and restarting drdaemon to facilitate storage controller recognition
Injecting drivers into the Plug-in Offline Client image
Booting the NetVault Bare Metal Recovery Client from a LiveCD
Prerequisites for backing up data with Plug-in Offline Client
Restoring data with Plug-in Offline Client
Booting the NetVault Bare Metal Recovery Client with Plug-in Offline Client
Verifying Disk Geometry and Device Size
Backing up data with Plug-in Offline Client
Using Plug-in Offline Client to restore data to a physical machine
Prerequisites for restoring data with Plug-in Offline Client to a physical machine
Restore procedure for using Plug-in Offline Client to restore data to a physical machine
Post-restore for using Plug-in Offline Client to restore data to a physical machine
Using Plug-in Offline Client to restore data as a VMDK Image
Selecting data for a restore using Plug-in Offline Client to restore data as a VMDK Image
Setting restore options for using Plug-in Offline Client to restore data as a VMDK Image
Finalizing and submitting the job for using Plug-in Offline Client to restore data as a VMDK Image
Creating the VM from the restored VMDK Image
Using Plug-in Offline Client to recover data to a standby NetVault Bare Metal Recovery Client
Plug-in Live Client overview
Configuring Plug-in Server for use with Plug-in Live Client
NetVault Bare Metal Recovery physical-to-virtual (P2V) recovery
Creating a Plug-in Offline Client Boot System
Installing and removing Plug-in Live Client
Creating a Linux-based Boot System for use with Plug-in Live Client
Creating a Windows PE-based Boot System for use with Plug-in Live Client for Windows
Installing VaultOS on a writable CD for use with Plug-in Live Client
Adding a NetVault Bare Metal Recovery Client to the Plug-in Server for use with Plug-in Live Client
Installing or upgrading Plug-in Server for use with Plug-in Live Client
Adding Plug-in Live Clients for use with Plug-in Live Client
Installing or upgrading Plug-in Live Client
Upgrading Plug-in Live Client
Removing Plug-in Live Client
Backing up data with Plug-in Live Client
Prerequisites for backing up data with Plug-in Live Client for Windows
Performing an online backup of data using Plug-in Live Client for Windows
Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client
Restoring data with Plug-in Live Client
Restoring to a physical machine with Plug-in Live Client for Windows
Prerequisites for restoring to a physical machine with Plug-in Live Client for Windows
Restore procedure for restoring data with Plug-in Live Client
Restoring data as a VMDK Image with Plug-in Live Client for Windows
Selecting data for a restore as a VMDK Image with Plug-in Live Client for Windows
Setting restore options for a restore as a VMDK Image with Plug-in Live Client for Windows
Finalizing and submitting the job for a restore as a VMDK Image with Plug-in Live Client for Windows
Creating the VM for a restore as a VMDK Image with Plug-in Live Client for Windows
Installing SCSI and IDE device drivers on a physical machine
Supported physical to virtual configurations
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
NetVault Bare Metal Recovery physical-to-virtual (P2V) recovery
Installing SCSI and IDE device drivers on a physical machine
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 |
Supported physical to virtual configurations
The following configurations are currently supported for Windows Server 2012 (32/64-bit) and later.