Bare metal restore from local cache - x360Recover D2C

x360Recover Direct-to-Cloud

Written By Tami Sutcliffe (Super Administrator)

Updated at September 7th, 2021

Bare metal restore is the process of recovering an entire protected system, directly from backup data, onto a new or recently wiped system. 

Bare metal restore is most often used with hardware devices but can be applied to virtual machines as well.

Prepare the bare metal restore boot media

Bare metal restore is performed from within a live CD, which provides a platform from which to boot a bare hardware system and run recovery utilities.

STEP 1. First, download the x360Recover Recovery Toolkit from

STEP 2. Once you have downloaded the ISO file, refer to this  article for instructions on creating a bootable USB drive.

Boot the bare metal restore environment

STEP 1. Insert your bootable USB media into the hardware system and boot from it.  

You may need to make a selection on startup to choose boot device or edit the system BIOS settings to direct the system to boot from USB media. Refer to your hardware manual for assistance configuring your bare metal system to boot from USB.

STEP 2. Once booted, the Axcient x360Recover Recovery Toolkit will load. This live CD provides a Linux graphical desktop environment very similar to Windows, with desktop shortcuts and Start-menu-like application launcher.  

STEP 3. Locate the Recovery Wizard icon on the desktop and double click it to launch the bare metal Recovery Wizard.

Perform a bare metal recovery from local cache

When launched, the Recovery Wizard presents several options for performing a bare metal recovery.  

STEP 1. Select Recover from Local Cache and click Next.

STEP 2. Select the location of your local cache data.

If your local cache data is located on a USB drive, connect the USB drive to the system being restored and it should automatically be mounted in the /media folder. 

Linux will make a folder (located within /media), based on the disk volume label of the USB drive (i.e. /media/LocalCache etc.)

Click the Browse button and navigate to the folder containing your local cache repository files.

Use a network-attached local cache

If your local cache is located on a network share, you must first mount the network share within the Recovery Toolkit environment.  

This requires running several simple shell commands.

STEP 1. Open QTerminal by double clicking the icon on the desktop.

STEP 2. Complete the following changes:

a) Elevate the user account to root.  
Type: sudo su and press Enter
b) Create a folder to mount the network share.  
Type: mkdir /media/nas and press Enter
c) Mount the network share.  
Type: mount -t cifs -o username=<User> //<Server>/<Share> /media/nas
d) Replace <User> with the username you wish to login to the NAS with
e) Replace <Server> with the IP address of the NAS
f) Replace <Share> with the Share name on the NAS

When you have completed these steps, press Enter. 

You will be prompted for the password of the User you provided above.  

Type the password and press Enter.

STEP 3. Once the network share is mounted, browse to your local cache folder at

/media/nas/<some folder path>

If you’ve chosen a valid path to a local cache repository, the protected system dropdown should populate with available protected systems whose data is stored there.

STEP 4. Choose the protected system to recover and click Next.

The IP address of the vault should automatically be populated from the local cache metadata.  Enter either the vault admin user and password, or the client user and password and click Next.

Note: In this preview edition, only local vault user credentials are supported. 

 x360Portal and Recover Manager credential support will be added in a later release.

STEP 5. Select the snapshot you wish to recover from and click Next.

STEP 6. At this point, the iSCSI service will construct the protected system disk volumes for recovery. 

  • Hash file data for each volume must be downloaded from the vault. 
  • Please allow several minutes for this download to complete.  
  • Note: In this preview edition, there is limited progress information being displayed on this page of the Wizard.  If the disk volumes are very large, it may take some time to complete the download of the hash files.

Once the process is complete, the Next button will become available.  

Click Next to continue.

STEP 7. From the Drive Mapping page, select which of the available physical disks you wish to recover and map them to a local disk for recovery.

IMPORTANT NOTE: The disk on the LOCAL MACHINE must be as large (or larger) than the original protected system disk.

Known issue:  If there is only a single disk in the system, this page can be confusing. When you click the disk dropdown, the selection overlaps the widget. Click once to open the dropdown, then click a second time to select the disk.

Click Next to continue.

Note: While Windows refers to physical disks as Disk1, Disk2, etc, Linux uses device names that designate both the controller type and physical order.
  • SDx devices are SATA/SCSI controllers
  • HDx devices are IDE controllers.
  • ‘x’ is a letter (a-z) designating the disk order.  
Generally speaking, Windows Disk1 would align with Linux disk ‘sda’ and so on.  
For additional comparison, physical disk sizes are shown to help ensure you are assigning correct and compatible devices.
IMPORTANT NOTE: The disk on the LOCAL MACHINE must be as large (or larger) than the original protected system disk.

STEP 8.The drive cloning process will begin.

Note: x360Recover agent 2.x does not capture the System Reserved (Boot) partition into the local cache.  

This volume will be retrieved over the WAN from the vault and file recovery progress will be relatively slow. (Typically, it may take 15-20 minutes to complete recovering this partition.)

The remaining volumes should be stored in the local cache and recovery should proceed at wire speed.

STEP 9. Once all disk Volumes have been cloned, click Finish to close and exit the Bare Metal Recovery Wizard.

If you are recovering this protected system to new hardware, it may be necessary to run the driver injector to install critical storage controller drivers into the recovered system.

For complete details on performing bare metal recovery, other Recovery Toolkit utilities, and the Driver Injector, refer to the Recovery Toolkit User Guide.

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