Bare Metal Recovery

With CloudBerry Backup, you can create a recovery USB drive or ISO image file for an emergency "bare metal" recovery in case of a system or hardware crash.

Configuring BIOS Settings

When booting from a recovery disk, you might need to customize some of the BIOS settings to make sure that the recovery disk configuration matches that of both the current PC and source PC on which the recovery disk was created, so that the recovery disk is able to load its operating system.

For example, you might not be able to restore a disk image unless the SATA configuration of the current PC matches that of a computer on which the recovery disk was created.

CloudBerry Boot Menu

Booting from a recovery USB device or ISO disk image file opens the CloudBerry Boot Menu.

This menu provides the following options:

  • Bare Metal Recovery Runs CloudBerry Backup where you can start the recovery process.
  • CloudBerry Remote Assistant This option is available when CloudBerry Remote Assistant is installed on the recovery disk. It enables you to allow remote control over the current PC or take control over another computer remotely.
  • Tools Provides various tools for configuring the restored machine. These tools include:
  • Microsoft Windows Command Prompt (enables you to use IPConfig, DiskPart and other tools to configure the target machine using the command-line interface)
  • Registry Editor
  • Save CloudBerry Backup application logs

Troubleshooting

Problem:
The boot disk cannot discover the network.

Possible solution (our favorite one):
Ensure that the network cable connecting the computer to the network is functioning.

Upon booting from a recovery disk, you can check the network access by running the IPConfig tool in the Command Prompt that is available in the Tools category of the CloudBerry Boot Menu (see the CloudBerry Boot Menu section of this document for more information).

Problem:
The recovery process fails.

Description:
Upon loading, the recovery disk creates a virtual drive in the PC memory (this drive is assigned the letter X by default). This virtual disk is used to contain a repository storing the image-related data. Every time you boot from the restore disk, this repository is created from scratch.

The virtual disk size varies depending on the operating system family. When you are required to store an increased amount of image-related information, the repository might exceed the virtual disk size, which results in an error and the failure of the recovery process.

Possible solution:
To avoid this issue, create a new recovery disk using the command-line interface (CLI) and increase the repository size by running the "createRecovery" command with the "-ss (-scratch-space)" parameter. You can use this parameter to increase the repository size to 256 or 512 MB.

See the Make bootable drive (createrecovery) to learn more about using the CLI for recovery disk creation.

Problem:
When restoring a disk image from Amazon S3, the following error occurs: "The clock is not synchronized."

Solution:
On the CloudBerry Boot Menu, switch to Tools and press T to synchronize the local and network clocks.

Problem:
The disk image is not found.

Possible solution:
Try changing the backup prefix to make it match the name of a computer on which the disk image was created.

Problem:
When trying to log in to the CloudBerry agent, the following error occurs: "The remote name could not be resolved: ' mspbackups.com'"._

Possible solution:
This error may occur if the IP address configuration is missing, for example when the machine is located in a network without a DHCP server. See the following Knowledge Base article for more information: KB 1082.

Problem:
On an attempt to restore a disk image using a recovery USB device, the following error occurs: "A connection to the deployment share could not be made. The following networking device did not have a driver installed."

Possible solution:
The reason for this error may be a missing network device driver or some failure during the import of drivers. See the following Knowledge Base article for more information: KB: 1081.