Virtual Disk Image - BMR (Bare metal restore)

Written By Tami Sutcliffe (Super Administrator)

Updated at August 25th, 2022


Our x360Recover Bare Metal Restore Wizard offers several options for performing different types of recovery, depending on where your data is located:


Perform bare metal restore from a virtual disk image

An alternative method of recovering your protected system involves using an exported virtual disk image. You can use bare metal recovery to restore your target system, directly from that image.  This is useful when you do not have a local cache configured for your Direct-to-Cloud (D2C) system, or in other situations where you may have already exported your protected system to a virtual disk image. 


How to perform BMR from a virtual disk image

STEP 1. From the main bare metal recovery (BMR) wizard menu, select Recover from Virtual Disk Image(s) and then click Next to continue.


STEP 2. Connect your drive or map your network share

2a. If your virtual disk image is on a USB drive, ensure that the USB device is connected to this recovery system and click Next to continue.

2b. If your virtual disk image is on a Windows server or NAS device, map the network share by providing the user credentials and UNC path. Then click Next to continue.

2c.  If your virtual disk image is on a Linux server or SAN using NFS shares, map the network share by providing the network path to the share and click Next to continue. 

Note: Be sure to enable permissions for this machine to access the NFS export on the Linux server or SAN.

STEP 3. Select the desired virtual disk image file and map it to a local drive by clicking Add.

You can add as many disk maps as you require to recover all protected system volumes.

Virtual disk images located on a network share:

/media/axcient/VirtualDisks

Virtual disk images located on an attached USB drive:

/media/axcient/<USB Volume name>

STEP 4. Use the browse tool to select the virtual disk image file.  



Map to local drives

Linux uses a different disk nomenclature than Windows:

Windows uses 
Disk0, Disk1, etc. 

Linux uses devices in this form

 /dev/<device

The Linux <device> is typically a 3-leter acronym:

  • First letter is the type of drive controller (S for Scsi/Sata or H for IDE/PATA)
  • Second letter is typically D for Drive
  • Third letter is an alphabetical designation for drive order, starting with A

Examples of Linux devices:

 /dev/sda 
 /dev/sdb 
 /dev/hda 

Partitions on the Linux device are then designated with a number.  

For example, the first partition on the first disk might be 

/dev/sda1


  • Third-party device names

Some third-party RAID controllers (notably HP) may use a different device naming scheme. 

  • HP RAID controllers typically use cciss as the device type.
  • This is followed by a number indicating the device order.  
  • Partitions are designated as  -p<x>

Example: The first partition on the first disk would be /dev/cciss1-p0

For purposes of drive mapping in these instructions, we will specify full disks. 

For example, we might map the original Windows Disk0 to the local disk /dev/sda.


  • Disk ordering 

Linux may enumerate disks in a different order than Windows, especially if multiple storage controllers are present on the system. 

Typically, you should examine the size of the local disk to ensure you are matching protected system disks to the correct local disk for recovery.



Data Adaptive Mode vs Failsafe Mode

What are the available recovery modes and which should I choose?

Data Adaptive Mode is the default (recommended) recovery mode. Recovery is performed partition by partition, using filesystem-specific cloning tools. Blank spaces will be skipped for efficiency and only in-use disk blocks will be copied.

Failsafe Mode is triggered if you de-select the default Data Adaptive Mode. Failsafe mode performs a raw disk dump of the entire drive in one pass.   Failsafe mode may be slower than Data Adaptive Mode if substantial segments of the drive are empty, as these empty spaces will be copied and not skipped.

When would I choose Failsafe Mode?

  • If your protected system contains Windows dynamic disks, or you experience unrecoverable errors trying to use Data Adaptive Mode, you should select Failsafe mode for the recovery instead.
  • Depending on your data configuration, Failsafe Mode might be faster.

Note: You can choose to use Failsafe mode for only for the specific disks that meet these criteria.   If your system has multiple disks, you can use Data Adaptive Mode for some and Failsafe mode for others where necessary.

Data adaptive mode
  • Copies each partition, one by one, using filesystem-specific copy tools in the most efficient manner. 
  • Blank spaces are skipped 
  • Only in-use disk blocks are copied
Failsafe mode 
  • Copies the entire disk in a single pass, regardless of file system types. 
  • Provides maximum reliability
  • May be slower when the disk volume contains large, empty spaces.
  • Avoids any file system-related errors

Once you have completed your drive mapping selections, click Next to continue.

The recovery progress window will be displayed.

Recovery progress will continue to be displayed as each disk and volume is processed.  

Progress, elapsed time, and estimated completion is displayed for each disk and/or volume being processed.  

Once the recovery is completed, click Finish to close the wizard.

 


ADDITIONAL RESOURES:  x360Recover bare metal restore (BMR)



 SUPPORT | 720-204-4500 | 800-352-0248

1202  |  1225  |  1269