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

Booting the NetVault Bare Metal Recovery Client with the Windows® PE-based Plug-in Offline Client

To boot from a standard Plug-in Offline Client CD:

Power down the NetVault Bare Metal Recovery Client, and insert the Plug-in Offline Client CD (if connected through a USB port, the port must use the 2.x protocol or earlier).

On reboot, the NetVault Bare Metal Recovery graphical user interface (GUI) appears.

When the BMR Network Configuration dialog box appears, select the applicable option:

•

Use DHCP (recommended): To use the Dynamic Host Configuration Protocol (DHCP) to configure the network interface, select this option.

•

Use Static IP Address: To enter specific IP addresses, select this option, and enter the addresses in the IP Address, Subnet Mask, and Default Gateway fields.

To submit the information, click Config, and then click OK when the confirmation message appears.

To close the BMR Network Configuration dialog box and start the NetVault Bare Metal Recovery Agent, click Exit.

After the network configuration is completed, the agent is started and the initialization process is finished. The NetVault Bare Metal Recovery Client is now prepared for backup or restore.

You can use the list above the Run button to output information related to the NetVault Bare Metal Recovery GUI when you issue the Run command.

Also, the information displayed in the text window is automatically exported to the “x:\dellbmr\bmr_gui.log” file.

Loading drivers dynamically

In some cases, Windows® PE might recognize the hardware attached to the target machine.

To load drivers without having to restart Windows PE:


	NOTE: These steps are based on targeting a network adapter. For other types of hardware, some steps might not be required.

Prepare a device, such as a CD, that contains the files needed for the driver, including the “*.inf” file.

Use the Plug-in Offline Client CD to start the NetVault Bare Metal Recovery Client.

When the BMR Network Configuration dialog box appears, click Exit to close it.

To open a DOS prompt, click Launch CMD.

Insert the device created in Step 1, which contains the driver files.

To load the driver, type the following at the command prompt, and press Enter:

drvload <pathToDriverINFfile>

Example:

drvload a:\netadm.inf

To access the BMR Network Configuration dialog box, type the following at the command prompt, and press Enter:

qnet

From the Network Adapters list, select the item that you just added, and then continue from Step 2 under Booting the NetVault Bare Metal Recovery Client with the Windows® PE-based Plug-in Offline Client.

Injecting drivers and restarting drdaemon to facilitate storage controller recognition

In some cases, Windows® PE might recognize the hardware attached to the target machine.

To load drivers without having to restart Windows PE:

Prepare a device including the “*.inf” file.

Examples of devices include a USB device that uses the 2.x protocol or earlier, or a network location that contains the files needed for the driver.

Use the Plug-in Offline Client CD to start the NetVault Bare Metal Recovery Client.

When the BMR Network Configuration dialog box appears, do one of the following:

•

If the system detects the adapter and displays it in the Network Adapters list, select the item, and then complete Step 2 and Step 3 under Booting the NetVault Bare Metal Recovery Client with the Windows® PE-based Plug-in Offline Client

•

If the system does not detect the adapter, complete the steps outlined under Loading drivers dynamically.

To open a DOS prompt, click Launch CMD.

Insert the device created in Step 1, or map to the applicable network drive.

To load the driver, type the following at the command prompt, and press Enter:

drvload <pathToDriverINFfile>

Example:

drvload a:\cpqcissm.inf

To start the Windows Task Manager, type the following at the command prompt, and press Enter:

taskmgr

In the Windows Task Manager screen, select the Processes tab, right-click drdaemon, select End Process, and close the Task Manager.

To restart the drdaemon, type the following at a command prompt (if necessary, click Launch CMD again), and press Enter:

drdaemon

Injecting drivers into the Plug-in Offline Client image

If you do not, or cannot, use a device such as a USB device (2.x protocol or earlier) to load a driver after Windows® PE has started, use the following process to add the driver to the Plug-in Offline Client image and then re-create the Plug-in Offline Client image with the added driver. To complete this process, you must have Windows ADK for Windows 8 installed, the applicable “*.inf” file, a program capable of extracting an ISO image, and a method for repackaging the ISO as a bootable image or bootable CD. The following steps are based on Windows 7; these steps might differ depending on your environment.

Download the Windows ADK for Windows 8 from: http://www.microsoft.com/en-us/download/details.aspx?id=30652

Install the Windows ADK on a Windows Server 2008 R2, Windows Server 2012, Windows 7, or Windows 8 system.

You can use the default directory (C:\Program Files (x86)\Windows Kits\8.0) or a different directory of your choosing.


	IMPORTANT: Installation of Windows ADK also installs Microsoft® .NET Framework if it is not already installed. After .NET Framework is installed, the system is automatically restarted.

Extract the “NetVault Bare Metal Recovery ISO Builder for Plug-in Offline Client for Windows” file to the Windows ADK machine.

This step creates two files, “nvbmrisocreate.exe” and “nvbmriso.pkg.”

Verify that the path to where you intend to create the ISO image exists.

If the directory does not exist when you run the next step, the ISO image is not created.

To create the Windows PE ISO image, navigate to the directory that contains the extracted “nvbmrisocreate.exe” file, type the following at the command prompt, and press Enter:

The following list describes what you can specify for each option:

•

/TYPE: If you are working with an earlier version of the Plug-in Offline Client, enter WAIK for Windows Automated Installation Kit (AIK). If you are using version 6.1 or later, you can enter ADK.

•

/PKG: Enter the full path and filename for the Plug-in Offline Client .pkg file that you downloaded separately.

•

/DIR: Enter the full path to the location of the Windows AIK or ADK directory.

•

/OUT: Enter the path where the bootable ISO image should be created.

•

/ADDDRV: Enter the full path where the downloaded device drivers are stored.

•

/BIT:32: If you need to create a backwards-compatible version of VaultOS for use with a 32-bit version of Windows PE, enter this option.

Example:

nvbmrisocreate /TYPE:ADK