This section describes how to restore a protected Windows machine from bare-metal similar or dissimilar hardware.
Servers, when operating as expected, perform the tasks they are configured to do. It is only when they fail that things change. When a catastrophic event occurs, rendering a server inoperable, immediate steps are needed to restore the full functionality of that machine.
Rapid Recovery provides the ability to perform a bare metal restore (BMR) for your Windows or Linux machines. BMR is a process that restores the full software configuration for a specific system. It uses the term “bare metal” because the restore operation recovers not only the data from the server, but also reformats the hard drive and reinstalls the operating system and all software applications. To perform a BMR, you specify a recovery point from a protected machine, and roll back (perform a restore) to the designated physical or virtual machine. If you are performing a restore to a system volume, this is considered a BMR. If you are performing a restore and require a boot CD, this is also considered a BMR. Other circumstances in which you may choose to perform a bare metal restore include hardware upgrade or server replacement In both of these cases, you perform a restore from a recovery point to the upgraded or replaced hardware.
Rapid Recovery supports Windows 8, 8.1 and Windows Server 2012, 2012 R2 operating systems that are booted from FAT32 EFI partitions are available for protection or recovery, as well as Resilient File System (ReFS) volumes.
Performing a BMR is possible for physical or virtual machines. As an added benefit, Rapid Recovery allows you to perform a BMR whether the hardware is similar or dissimilar. Performing a BMR on Rapid Recovery separates the operating system from a specific platform, providing portability.
Examples of performing a BMR for similar hardware include replacing the hard drive of the existing system, or swapping out the failed server with an identical machine.
Examples of performing a BMR for dissimilar hardware include restoring a failed system with a server produced by a different manufacturer or with a different configuration. This process encompasses creating a boot CD image, burning the image to disk, starting up the target server from the boot image, connecting to the recovery console instance, mapping volumes, initiating the recovery, and then monitoring the process. Once the bare metal restore is complete, you can continue with the task of loading the operating system and the software applications on the restored server, followed by establishing unique settings required for your configuration.
Bare metal restore is used not only in disaster recovery scenarios, but also to migrate data when upgrading or replacing servers.
While bare metal restore (BMR) is supported for virtual machines (VMs), it is also worth noting that it is easier to perform a Virtual Export for a VM than it is to perform a BMR as on a physical machine. For more information on performing a VM export for virtual machines, see the appropriate procedure for the supported VM:
To perform a BMR on a Windows machine, refer to the topic specific to Windows, including the prerequisites. For more information, see Performing a bare metal restore for Windows machines.
You can also perform a BMR from the Restore Machine Wizard. To do this, start with the procedure About restoring volumes from a recovery point and, when directed in that procedure, proceed to About performing a bare metal restore using the Restore Machine Wizard.
To perform a BMR on a Linux machine, see Performing a bare metal restore for Linux machines. In addition to performing a BMR using the command line local_mount utility, you can now perform a BMR from within the Core Console UI. The roadmap takes both approaches into account.
To perform a bare metal restore for Windows machines, perform the following tasks.