Chat now with support
Chat with Support

NetVault Bare Metal Recovery 13.1.1 - 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
NetVault Bare Metal Recovery physical-to-virtual (P2V) recovery  Troubleshooting

Injecting drivers and restarting drdaemon to facilitate storage controller recognition

Sometimes, Windows PE might recognize the hardware attached to the target machine. To load drivers without restarting Windows PE, perform the following steps.

1
Prepare a device including the “*.inf” file.
Examples of devices include a USB device that uses the 3.0 protocol or earlier, or a network location that contains the files needed for the driver.
2
Use the Plug-in Offline Client CD to start the NetVault Bare Metal Recovery Client.
3
When the BMR Network Configuration dialog box is displayed, 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.
4
To open a DOS prompt, click Launch CMD.
5
Insert the device created in Step 1, or map to the applicable network drive.
6
To load the driver, type the following at the command prompt, and press Enter:
drvload <pathToDriverINFfile>
Example:
drvload a:\cpqcissm.inf
7
To start the Windows Task Manager, type the following at the command prompt, and press Enter:
taskmgr
8
In the Windows Task Manager screen, select the Processes tab, right-click drdaemon, select End Process, and close the Task Manager.
9
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

Injecting drivers into the Plug-in Offline Client image

If you do not, or cannot, use a device such as a USB device, 3.0 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.

1
Download the Windows ADK for Windows 8 from: http://www.microsoft.com/en-us/download/details.aspx?id=30652
2
Install the Windows ADK on a Windows Server 2012 R2 or later 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.
3
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.”
4
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.
5
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 must create a backward-compatible version of VaultOS for use with a 32-bit version of Windows PE, enter this option.
Example:
nvbmrisocreate /TYPE:ADK
/PKG:"<pathToFile>\nvbmriso.pkg"
/DIR:"C:\Program Files (x86)\Windows Kits\8.0"
/OUT:"C:\temp\bmr.iso"
/ADDDRV:"C:\Program Files\Down Load Drivers\"
6
Insert a blank CD in the writable drive.
7
Create a CD with CD-generation software using the “bmr.iso” file generated in Step 5.

Booting the NetVault Bare Metal Recovery Client from a LiveCD

If you are booting the NetVault Bare Metal Recovery Client from a LiveCD, perform the following procedure. If you are booting the NetVault Bare Metal Recovery Client from a standard VaultOS CD, proceed to Booting the NetVault Bare Metal Recovery Client with the Windows PE-based Plug-in Offline Client.

The following items are required for this procedure:

•
A LiveCD containing the desired OS.
Note the following important points:
•
The LiveCD must mount the loop-back device to perform backup and restore with NetVault.
•
Some LiveCDs automatically mount all partitions for devices, which can lead to restore failure if the file system is mounted before a backup or restore job. If you boot with a LiveCD, ensure that the file system is unmounted before performing a backup or restore.
•
Some LiveCDs automatically use the swap partition for swap operations, which can lead to restore failure if the swap partition is used before a backup or restore job. If you boot with a LiveCD, ensure that the LiveCD does not use the swap partition before performing a backup or restore.
•
A Rescue device — see Creating a rescue device for use with a LiveCD.
•
A USB port, for a Rescue USB device, that uses the 3.0 protocol or earlier, or a secondary CD drive, for a Rescue CD, on the target system. If the drive is connected through a USB port, it must use USB 3.0 protocol or earlier.
•
If you are using a Rescue CD, you need two CD drives on the target system — one for the LiveCD and one for the Rescue CD. If connected through USB ports, the drives must use the USB 3.0 protocol or earlier.
 
* 
IMPORTANT: When using Windows PE-based VaultOS with NetVault SmartDisk, the Connect ports for devices option in NetVault uses twice as many ports as there are partitions. For example, if you are restoring to a disk that contains seven partitions, the device connection uses 14 ports.

To boot the client, perform the following steps.

1
Insert the LiveCD in the CD drive — if connected through a USB port, the port must use the 3.0 protocol or earlier — on the target system, and reboot the machine.
2
After the OS starts, plug in the device, 3.0 protocol or earlier, or load the Rescue CD.
Usually, the LiveCD automatically mounts the USB/CD drive and shows an icon on the desktop.
3
If the LiveCD automatically mounted the USB/CD drive, use the “mount -l” command to find the path where the device is mounted.
Example:
# mount -l
...
/dev/sdb1 on /media/disk type ext2 (rw,nosuid,nodev)
4
If the LiveCD does not automatically mount the USB drive, mount it manually:
 
* 
NOTE: To use a Rescue CD by mounting a CD instead of a USB device, follow the same procedure.
a
To find the USB devices on the system, use the “ls -l /dev/disk/by-id/usb*” command.
Example:
# ls -l /dev/disk/by-id/usb*
root 9 2007-09-26 8:16 /dev/disk/by-id/usb-JetFl -> ../../sdb
root 10 2007-09-26 8:16 /dev/disk/by-id/usb-JetFl-part1_-> ../../sdb1
root 10 2007-09-26 8:16 /dev/disk/by-id/usb-JetFl-part2 -> ../../sdb2
b
Mount the first partition on the device.
Example:
# mount /dev/sdb1 /mnt/usb
5
To start drdaemon, run the “vaultdr_client.sh” command.
Example:
# cd /mnt/usb
# sh vaultdr_client.sh
6
If you configured NetVault Bare Metal Recovery to use a port other than the default “10000,” exit the NetVault Bare Metal Recovery Daemon dialog box, and enter the new port number manually.
a
To exit the NetVault Bare Metal Recovery Daemon dialog box, press <Ctrl+C>.
b
At the command prompt, type the following command, and press Enter:
drdaemon -p port_number
where port_number is the port you specified in Adding a NetVault Bare Metal Recovery Client to the Plug-in Server or Editing an existing NetVault Bare Metal Recovery Client.
 
* 
NOTE: If you want to restart NetVault Bare Metal Recovery Daemon from the command prompt without changing the port number, type drdaemon and press Enter.
7
If you want to enable multipath support, type the following at a command prompt, and press Enter:
drdaemon -o mpath
 
* 
NOTE: You can enter the -o mpath and -p port_number options together.

Backing up data with Plug-in Offline Client

Backing up data with Plug-in Offline Client

The Plug-in Server lets you back up full systems. In addition, the plug-in provides detailed backup capabilities that let you select individual disk partitions for backup. This plug-in includes the following items:

•
OS
•
Applications
•
Specific User Information

From the NetVault Selections page, you can select the following Plug-in Server items for backup:

•
Disk Partitions: All (or individual) partitions can be selected for backup.
 
* 
IMPORTANT: If you are targeting large-sector — 4K — Windows drives for backup, the EFI partition size must be larger than 256 MB. For more information, see https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions.
•
Mounted Volumes (Linux and UNIX): All of which are backed up as individual partitions.
 
* 
NOTE: The Master Boot Record (MBR) and the Partition Table items are backed up automatically when a partition (all or individual) is backed up using the Plug-in Server. Therefore, these items are not available to select for a backup.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating