Before you can begin the process of performing a bare metal restore for a Windows machine, you must ensure that the following conditions and criteria exist:
- A 64-bit central processing unit (CPU). The Rapid Recovery boot CD includes the Win PE 5.1 operating system. Rapid Recovery BMRs are not compatible with x86-based CPUs. You can only perform a BMR on a 64-bit CPU.
This requirement is new as of 6.0.
- Backups of the machine you want to restore. You must have a functioning Rapid Recovery Core containing recovery points of the protected server you want to restore
- Hardware to restore (new or old, similar or dissimilar). The target machine must meet the installation requirements for an agent; for details, see the Dell Data Protection | Rapid Recovery Installation and Upgrade Guide.
- Image media and software. You must have a blank CD or DVD and disk burning software, or software to create an ISO image. If managing machines remotely using virtual network computing software such as UltraVNC, then you must have VNC Viewer.
- Compatible storage drivers and network adapter drivers. If restoring to dissimilar hardware, then you must have compatible storage drivers and network adapter drivers for the target machine, including RAID, AHCI, and chipset drivers, as appropriate.
- Storage space and partitions, as appropriate. Ensure that there is enough space on the hard drive to create destination partitions on the target machine to contain the source volumes. Any destination partition should be at least as large as the original source partition.
- Compatible partitions. Windows 8, Windows 8.1, Windows 10, Windows Server 2012, and Windows Server 2012 R2 operating systems that are booted from FAT32 EFI partitions are available for protection or recovery, as well as are Resilient File System (ReFS) volumes. UEFI partitions are treated as simple FAT32 volumes. Incremental transfers are fully supported and protected. Rapid Recovery provides support of UEFI systems for BMR including automatic partitioning GPT disks.
A bare metal restore for Windows requires a boot image referred to as the boot CD, which you create by defining parameters in the Rapid Recovery Core Console. This image is tailored to your specific needs. You will use the image to start the destination Windows machine. Based on the specifics of your environment you may need to transfer this image to physical media such as a CD or DVD. You must then virtually or physically load the boot image, and start the Windows server from the boot image.
The first step when performing a bare metal restore (BMR) for a Windows machine is to create the boot CD file in the Rapid Recovery Core Console. This is a bootable ISO image which contains the Rapid Recovery Universal Recovery Console (URC) interface, an environment that is used to restore the system drive or the entire server directly from the Rapid Recovery Core.
The boot CD ISO image that you create is tailored to the machine being restored; therefore, it must contain the correct network and mass storage drivers. If you anticipate that you will be restoring to different hardware from the machine on which the recovery point originated, then you must include storage controller and other drivers in the boot CD. For information about injecting those drivers in the boot CD, see Understanding driver injection in a boot CD.
The boot CD image requires storage drivers to recognize the drives of the server, and network adapter drivers in order to communicate with the Rapid Recovery Core over the network.
A generic set of Windows 8.1 x64 storage controller and network adapter drivers are included automatically when you generate a boot CD for Windows. This satisfies the requirements of newer Dell systems. Systems from other manufacturers or older Dell systems may require you to inject storage controller or network adapter drivers when creating the boot CD. If you discover the boot CD you created does not contain the drivers necessary to complete the restore, you can also load drivers on to the target machine using the URC. Fore more information, see Loading drivers using the Universal Recovery Console.
When creating the boot CD, driver injection is used to facilitate the operability between the recovery console, network adapter, and storage on the target server.
Data restored from the recovery point includes drivers for the hardware previously in place. If performing a bare metal restore to dissimilar hardware, then you must also inject storage controller drivers into the operating system being restored using the URC after the data has been restored to the drive, This allows the restored operating system to boot using the new set of hardware. After the OS is booted after the restore, you can then download and install any additional drivers needed by the OS to interact with its new hardware.
A boot CD is the term Rapid Recovery uses to refer to the portable storage location of the ISO image reserved for performing a bare metal restore (BMR). The image includes the Rapid Recovery Universal Recovery Console (URC).
To perform a BMR on a machine, you must start the machine from the boot CD, which launches the URC. The URC is what makes it possible to connect the BMR target to the location of the recovery point you want to use to complete the restore.
- From the Rapid Recovery Core Console where the server you need to restore is protected, in the icon bar, click the More menu, and then click Boot CDs.
- On the Boot CDs page, click Create Boot CD.
The Create Boot CD dialog box displays.
- In the Create Boot CD dialog box, in the Output path text box, enter the location where you want to store the boot CD ISO image.
The file extension must be .iso. When specifying the path, use only alphanumeric characters, the hyphen, the backslash (only as a path delimiter), and the period (only to separate host names and domains). The letters a to z are not case sensitive. Do not use spaces. No other symbols or punctuation characters are permitted.
- Under Connection Options, do one of the following:
- To obtain the IP address dynamically using Dynamic Host Configuration Protocol (DHCP), select Obtain IP address automatically.
- To specify a static IP address for the URC, select Use the following IP address, and then enter the following information:
- IP address
- Subnet mask
- Default gateway
- DNS server
You must specify all four of these fields.
- If you require remote access to the recovery console, and you have UltraVNC installed, under UltraVNC Options, complete the following steps:
UltraVNC lets you manage the URC remotely while it is in use. You cannot log on using Microsoft Terminal Services while using the boot CD.
- Select Add UltraVNC.
- Enter your UltraVNC password.
- Enter the UltraVNC port. The default port is 5900.
The UltraVNC Options are only available if you already have UltraVNC installed. To make these options available, go to http://www.uvnc.com/downloads/ultravnc/
to download UltraVNC version 184.108.40.206 or later for x64 architecture. Install it and save the winvnc.exe file to C:\Program Files\AppRecovery\Core\BootCdKit\UltraVnc_x64\.
- If you plan to restore to dissimilar hardware, inject the appropriate storage controller and other drivers for your target system by completing the following steps:
- Download the drivers from the server manufacturer’s Web site and unpack them.
- Compress each driver into a .zip file using an appropriate compression utility (for example, WinZip).
- In the Create Boot CD dialog box, in the Drivers pane, click Add an Archive of Drivers.
- Navigate through the filing system to locate the compressed driver file, select the file, and then click Open.
The injected driver file appears in the Drivers pane of the Create Boot CD dialog box.
- Repeat Step c and Step d, as appropriate, until you inject all necessary drivers.
Not all versions of Windows are compatible with automatic driver injection. If your operating system is not compatible, manually save drivers to C:\Program Files\AppRecovery\Core\BootCdKit\Drivers\.
- Click Create Boot CD.
Rapid Recovery creates the boot CD and saves it with the file name you provided.
- To monitor the progress of this task, go to the icon bar and click the Events icon.
When the ISO image creation is complete, a record of the image appears on the Boot CDs page, which you can access from the More menu in the icon bar.
To access the ISO image, you can navigate to the output path you specified or click the link on the Boot CDs page to save the image to a location from which you can then load it onto the new system, such as a network drive.