The Recovery Toolkit operates from a Linux environment and there are several unsupported recovery scenarios:

•  BMR recovery cannot be performed onto any hardware platform that requires Windows-only drivers. Examples of this would be any system using an unsupported motherboard RAID adapter. (Dell PERC S3xx series, Intel Cxxx controllers, and HP SmartArray B120/B320, as well as most white-box motherboard RAID controllers are examples of unsupported adapters.) 
•  The Recovery Wizard cannot recover systems with multiple Windows volumes on a single physical disk. (e.g. C: and E: on Disk 0). If it is necessary to perform a recovery of multiple volumes onto a single disk, refer to the Manual Partition Recovery section of the Recovery Toolkit and Guide. 
•  The new Destination disk *MUST* be at least as large or larger than the original disk. 
• The size of any partition or volume cannot be changed before or during the recovery process.

1. To perform a recovery directly from a locally-accessible appliance or vault BDR device onto your recovery system, select Recover from Local Appliance or Vault from the Bare Metal Recovery Wizard.

Note: You can't use the Bare Metal Recovery Wizard to connect to a remote vault over the internet. The connection for a remote vault must be done on the local LAN.

Click the Next button to continue.

2. In the Replibit Server Connection screen, enter the IP address, username and password of the appliance or vault you are connecting to.

Click the Next button to continue.

3. In the Protected System Selection screen, select the protected system that should be recovered:

• From the Chose Protected System to restore drop-down box, select the protected system you would like to recover.
• In the Choose Snapshot to Restore section, select from the following options:
  • From a list of recent snapshots
  • From a specific date

Click Next to continue.

4. In the Snapshot Selection screen, select the snapshot that should be used as the recovery point:

• Select the recovery point date and time that you would like to use for recovery of the protected system.
• If an encryption passphrase was configured when the agent was installed on this protected system, enter the Encryption password.

Click the Next button to continue.

5. The Recovery Wizard will now initialize iSCSI services, export the selected recovery point on the appliance or vault, and attach the disk volumes. 

Verify that the iSCSI operations completed successfully, and that no errors are reported.

Click the Next button to continue.

6. In the Drive Mapping screen, select the drive volume(s) you wish to recover:

• Check the checkboxes next to the appropriate drive volumes.
• For each volume being recovered, choose a disk to restore it to by selecting from the dropdown list.

Click Next to continue.

Regardless of the recovery method you have selected, the data recovery process will now begin.

You will now monitor the overall job progress from the Recovery Wizard status window.

Continue to STEP 3. Disk Recovery Operation in the instructions below for more information on how to proceed.

1. To perform a recovery from an exported virtual disk image, select Recover from Exported Virtual Disk from the Bare Metal Recover Wizard.

Click Next to continue.

2. Attach a USB disk containing the exported virtual disk image you wish to restore to the recovery system.  A popup should appear showing that the device has been mounted. 

3. Cancel or close the popup and return to the Bare Metal Recovery Wizard.

4. On the Drive Mapping page, click the Browse button and select the Source Virtual Disk. 

Locate the mounted USB drives at /media/axcient/<label> (where <label> is the volume label name of the mounted drive).

Browse to and select the VHD, VHDX or VMDK file you wish to recover from.

Click Open to continue.

5. Once you have selected a disk, map it to the appropriate Target Disk.

Click Add to save it to the list. 

Repeat the above steps to map additional virtual disks to local physical disks for recovery, if necessary.

Click Next to continue.

Map a network share

6. If your virtual disk image is located on a network share, you will have to manually mount that share onto the running live CD environment.

Click the Start menu and select QTerminal from the System Tools Menu.

Elevate the command prompt to the root user by executing:

sudo su

Mount the Windows share using the following command syntax:

mount -t cifs -o username=”<user name>”,domain=”<domain name>” //<Windows Server Name>/<Share Name>    /<Mount location>

For example: 

Server name is Server2012

Share name is Files

To login as the user Administrator for domain MyDomain and mount it at /mnt use:

Mount -t cifs -o username=”Administrator”,domain=”MyDomain” //Server2012/Files    /mnt

Note: If you have issues connecting by server name, you may use the IP address instead.

If you need to mount multiple shares, create folders for each mount point using mkdir

mkdir   /mnt/Share1

Regardless of the recovery method you have selected, the data recovery process will now begin.

You will now monitor the overall job progress from the Recovery Wizard status window.

Continue to STEP 3. Disk Recovery Operation in the instructions below for more information on how to proceed.

Recover using a disk-to-disk Copy Wizard

1. To perform a simple disk-to-disk copy operation for system recovery, troubleshooting or diagnostics, select Disk to Disk Copy Wizard from the Bare Metal Recovery Wizard.

Click Next to continue.

2. Select a source disk.

3. Select a target disk.

4. Click Add to add them to the list.

Repeat if necessary, to add additional disks to be copied.

Click Next to continue.

Regardless of the recovery method you have selected, the data recovery process will now begin.

You will now monitor the overall job progress from the Recovery Wizard status window.

Continue to STEP 3. Disk Recovery Operation in the instructions below for more information on how to proceed.

1. Mount the volume containing the C: drive of the protected system using Disk Manager.

2. From the Recovery Tools menu, click to launch the Driver Injector.

3. The Replibit BMR Driver Injector screen displays.

Note: If you have not mounted a disk volume that contains a valid Windows installation folder, you will receive a warning that the Driver Injector could not locate the offline Windows installation. 

Configure the target settings:

• The Dropdown selector Offline Windows Operating System should automatically discover the mounted system. If not, make sure the volume containing the C: drive is mounted and click Refresh.
• Click Browse and select the location containing the Windows drivers you would like to install.  To use the basic set of Windows drivers that has been included on the Recovery ISO, select the /root/Windows-Drivers.
• If you would also like to scan the native Windows driver library on the recovered system, click to select Also Scan the System32\DriverStore\FileRepository Directory for Drivers.

You can leave all other settings at their default values.

Click Next to continue.

4. In the Please wait while we analyze this system...  screen, wait for the Driver Injector to read through the provided driver files. It will make matches against the hardware installed within the running system.

When the Finished message appears, click the Next button to continue.

5.  When the table of discovered devices appears, verify that the driver matches have been located for all critical hardware, such as storage controllers. 

• To manually add specific drivers into the offline Windows installation, regardless of whether or not the hardware is physically present on the running system, click AddDrivers.
• From the Add Drivers dialog box, click Add and browse to the .inf driver file you would like to add.  Repeat as necessary to add additional drivers.

Note: No validation is performed on the drivers being selected. Please ensure that you are selecting a valid Windows driver file for the correct operating system and architecture.

• When you are finished adding drivers, click the Close button.
• Click the Next button to continue. 

6. The previously discovered and manually selected drivers will now be installed. Click Finish when the installation process has completed.