Rapid Recovery 6.4 - User Guide

Loading drivers in the Universal Recovery Console using portable media

1. On an internet-connected machine, download the drivers from the manufacturer’s website for the server and unpack them.
2. Compress each driver into a .zip file using an appropriate compression utility (for example, WinZip).
3. Copy and save the .zip file of drivers onto a portable media device, such as a USB drive.
4. Remove the media from the connected machine and insert it into the BMR target machine.
5. On the target server, load the boot CD ISO image from removable media and start the machine.
   The Quest splash screen appears.
6. To start the URC, click the (Start URC) button.
   The URC opens to the Boot CD driver manager tab.
7. Expand the Other devices list.

   This list shows the drivers that are necessary for the hardware but are not included in the boot CD.

8. Right-click a device from the list, and then click Load Driver.
9. In the Select driver load mode window, select one of the following options:
   • Load single driver package (driver will be loaded without verification for device support)
   • Scan folder for driver packets (drivers for selected device will be searched in selected folder)
10. Expand the drive for the portable media device, select the driver (with file extension .inf), and then click OK.
    The driver loads to the current operating system.
11. In the Info window, click OK to acknowledge that the driver successfully loaded.
12. Repeat this procedure as necessary for each driver you want to load.

Loading a driver in the URC using Chromium

1. On the target server, load the boot CD and start the machine.
   The Quest splash screen appears.
2. To start the URC, from the buttons at the top of the screen, click (Start URC).
   The URC opens to the Boot CD driver manager tab.
3. From the buttons at the top of the screen, click (Open useful tools), and then click Chromium.
   The Chromium browser opens.
4. Using Chromium, navigate to a website where you can download the necessary driver.
5. Download the driver or drivers to your location choice, such as a local folder or a network file share.
   If you do not specify a download location, by default Chromium downloads files to the path Boot (X:)\Program Files\Chromium.
6. Expand the Other devices list.

   This list shows the drivers that are necessary for the hardware but are not included in the boot CD.

7. Right-click a device from the list, and then click Load Driver.
8. In the Select driver load mode window, select one of the following options:
   • Load single driver package (driver is loaded without verification for device support)
   • Scan folder for driver packets (drivers for selected device are searched in selected folder)
9. Navigate to the location where you saved the driver, select the driver, and then click OK.
   The driver loads to the current operating system.
10. In the Info window, click OK to acknowledge that the driver successfully loaded.
11. Repeat this procedure as necessary for each driver you want to load.

Selecting a recovery point and initiating a BMR

1. In the Rapid Recovery Core Console, from the list of protected machines (or attached archives, if relevant), click the name of the protected machine you want to restore.
   The Summary page for the selected machine appears.
2. Click Recovery Points.
3. Next to the recovery point you want to use for the BMR, click the drop-down menu, and then click Restore.
   The Restore Machine Wizard appears.
4. Select Recover to any target machine using a Boot CD.
5. Select I already have a Boot CD running on the target machine.
   The authentication text boxes appear.
6. Enter the information about the machine you want to restore as described in the following table.

   Table 147: Target machine information

   Text Box	Description
   IP Address	The IP address of the machine to which you want to restore. This is identical to the IP address displayed in the URC.
   Authentication Key	The specific password to connect to the selected server. This is identical to the Authentication Key displayed in the URC.

7. Click Next.

   If the connection information you entered matches the URC, and if the Core and the target server can identify each other properly on the network, then the volumes for the selected recovery point are loaded, and the Disk Mapping page appears. In this case, your next step is to map volumes.

8. Proceed to About disk mapping for a bare metal restore to learn about your disk-mapping options.

About disk mapping for a bare metal restore

After you connect to the Universal Recovery Console, you need to map volumes between those listed in the recovery point and the volumes existing on the target hardware.

Rapid Recovery attempts to automatically map volumes. If you accept the default mapping, then the disk on the destination machine is cleaned and re-partitioned and any previously existing data is deleted. The alignment is performed in the order the volumes are listed in the recovery point, and the volumes are allocated to the disks appropriately according to size, and so on. Assuming there is enough space on the target drive, no partitioning is required when using automatic disk alignment. A disk can be used by multiple volumes. If you manually map the drives, note that you cannot use the same disk twice.

For manual mapping, you must have the new machine correctly formatted already before restoring it.

The destination machine must have a separate partition for each volume in the recovery point, including the system reserved volume. For more information, see Using the Universal Recovery Console for a BMR.

As of Rapid Recovery Core release 6.4, you can use automatic mapping when performing BMR for LVM and software-based RAID volumes on Linux machines without first creating the partitions.

Complete the procedure for one of the following disk-mapping options:

• Automatically mapping disks for a BMR
• Manually mapping disks for a BMR

This task is part of the process for Using the Universal Recovery Console for a BMR.

If performing a BMR for a Linux machine from the Core Console, then this task is also a step in Performing a bare metal restore for Linux machines. It is part of the process for Launching a bare metal restore for Linux.