[Manual] Bare Metal Recovery (BMR) Procedure

Last Updated: Nov 22, 2017 11:53PM CET

Bare Metal Recovery (BMR) Procedure

Prior to creating the ISO image, the Microsoft ADK (or AIK) software must be installed on the system protected or, the process will fail.

Step 1: Create the ISO boot file
Step 2: Create the BMR backup job
Step 3: Restore of BMR backup
In Case of BMR Restore Failure
BMR Restore Logs

Step 1: Create the ISO boot file:

  1. Open and administrator CMD window on the client machine you want to create a BMR job for. Then navigate to "C:\Program Files\NovaStor\DataCenter\Hiback\vss\BMR\PE-Build" and run CreateWinPE_x64_en.vbs to create the Machine Specific Boot ISO file.
  2. Rename this ISO file to match the computer that is was create on IE: "COMPUTERNAME_USB_BOOT.ISO". Create a folder on a network share named "NBK BMR ISO Files" or similar. Move the .ISO files created on each machine to this location.

Step 2: Create the BMR backup job:

  1. Create the backup job by going to the Backup Jobs window, right click in the window and choose "New". Then select "Bare-Metal Recovery" from the menu.
  2. In the "Job Creation Windows" and configure the backup:
    1. Select the node for which the BMR backup is being created.
    2. Select the storage target (media pool).
    3. Select the schedule Select "System Partition" to backup just the OS partition or, "All Partitions" to capture all drives/partitions.

Step 3: Restore of BMR backup:

  1. Open the "Restore" section of the interface.
  2. From here you can navigate to the "OS/Machine Name/Job Name/Date of backup".
  3. Select the "Guide" button from the lower right corner.
  4. This window will give you the "Backup ID" and "Device String". These are the 2 pieces of information that will be needed during the restore process.
  5. Burn the ISO file create in step 1 for the machine you are going to restore onto a USB drive.
  6. Boot PC from this USB stick. Make sure you have a live network cable attached to the machine before booting.
  7. Select N (no) for manual network configuration. The Restore Boot will look for DHCP automatically and should not need to be manually configured if you have one available. 
  8. Unless you are restoring to dissimilar hardware you can answer "N" (no) to the additional drivers question as well then hit enter.
  9. This is where you will enter the "Backup ID" you gathered from the GUI and hit enter.
  10. You can Hit enter to skip this the next step for "commandline options" - (advanced settings).
  11. This is where you will enter the "Device String" you gathered from the GUI and hit enter.
  12. You will get a list of the Volumes available in this job and be asked to continue. Select Y(yes) when ready to begin the restore process:
From here you will see the restore proceed and data transfer increment in the header of the window. Once completed you can exit the utility, remove the usb stick and reboot the machine.
It should boot back to the OS that was just restored and you can proceed with any file level, SQL or Exchange restores needed.

In Case of BMR Restore Failure

If the restore fails **DO NOT REBOOT** the machine.
Leave the system booted to the USB so the job log can be gathered to find out the reason for failure.
This is important because you are booted into a temporary memory disk and will be wiped if reboot.
You will need to map a network location as a drive in the command line in order to copy the files from the local USB.

BMR Restore Logs

To view log information after a BMR process completes, perform the following steps:
  1. Enter the following command: x:\NovaStor\Hiback\vss>net use y: \\hostname\share /user:M domain\username
  2. Enter the password for the user connecting to the share:'sv\kurt.hjorteset' to connect to 'ag-ws-kurt':
  3. Copy the files to the network drive created in the previous step:
    X:\NovaStor\Hiback\vss>copy *.* y:\vss
    14 file(s) copied.
View the contents of the "recovery.LOG" file to see detailed information about the BMR restore job.
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found