Chat now with support
Chat with Support

Rapid Recovery 6.1.3 - User Guide

Introduction to Rapid Recovery Core Console Core settings Repositories Encryption keys Protecting machines
About protecting machines with Rapid Recovery Support for dynamic and basic volumes Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Viewing the recovery progress Starting a restored target server Troubleshooting connections to the Universal Recovery Console Repairing boot problems Performing a file system check on the restored volume
Managing aging data Archiving Cloud storage accounts The Local Mount Utility The Central Management Console Core Console references Command Line Management utility PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Scripting REST APIs About us Glossary

Using the Universal Recovery Console for a BMR

About the Universal Recovery Console tools
Loading drivers using the Universal Recovery Console
Selecting a recovery point and initiating a BMR
About disk mapping for a bare metal restore
Performing a BMR from an archive
Loading drivers to the operating system

Before launching a bare metal restore (BMR) for a Windows machine, the following conditions are required:

•
To restore a recovery point saved on the Core, you must have the appropriate hardware in place. For more information, see Prerequisites for performing a bare metal restore for a Windows machine.
•
The BMR destination Windows machine must be started using the boot CD image. For more information, see Understanding boot CD creation for Windows machines.

A BMR initiates a machine using a recovery point you select. The recovery point includes drivers from the previous hardware. If restoring to dissimilar hardware, then you must inject storage controller drivers into the operating system being restored using the URC after the data has been restored to the drive, This lets the restored operating system start using the new set of hardware. After the OS starts, you can then download and install any additional drivers the OS needs to interact with the new hardware.

To launch a BMR from the Rapid Recovery Core Console, perform the following tasks.

•
Selecting a recovery point and initiating a BMR
•
About disk mapping for a bare metal restore
•
Loading drivers using the Universal Recovery Console

This process is a step in Performing a bare metal restore for Windows machines.

About the Universal Recovery Console tools

The Universal Recovery Console (URC) includes access to tools that may assist you with completing a bare metal restore (BMR).

You can find the following tools by clicking the center icon at the top of the Quest splash screen on a BMR target that is booted into the URC:
•
Far Manager. This tool is similar to Windows Explorer. It provides a way to browse for files on the server until you complete the BMR and install an operating system with its own browsing function, such as Windows Explorer.
•
Chromium. This open-source browser lets you access the Internet on a server that has a network controller loaded through the URC.
•
PuTTY. This tool is an open-source terminal emulator. In the context of a Rapid Recovery BMR, it lets you connect to a NAS storage device that does not include a user interface. This capability may be necessary if you want to restore from an archive and the archive is on a NAS.
•
Notepad. As in a Windows operating system, this tool lets you type unformatted notes and view log files.
•
Task Manager. As in a Windows operating system, this tool lets you manage processes and monitor the performance of the server while the restore is in progress.
•
Registry Editor. As in a Windows operating system, this tool lets you change the system registry of the BMR target.
•
Command Prompt. This tool lets you perform commands on the BMR target outside of the URC until you install a user interface.

Loading drivers using the Universal Recovery Console

Loading drivers in the Universal Recovery Console using portable media
Loading a driver in the URC using Chromium

This feature lets you add any drivers that were not included in the ISO image but are required for a successful bare metal restore.

This task is a step in Performing a bare metal restore for Windows machines. It is part of the process for Using the Universal Recovery Console for a BMR.

When creating a boot CD, you can add necessary drivers to the ISO image. After you boot into the target machine, you also can load storage or network drivers from within the Universal Recovery Console (URC).

If you are restoring to dissimilar hardware, you must inject storage controller, RAID, AHCI, chipset, and other drivers if they are not already on the boot CD. These drivers make it possible for the operating system to operate all devices on your target server successfully after you restart the system following the restore process.

Complete the steps in one of the following procedures to load drivers using the URC:

•
Loading drivers in the Universal Recovery Console using portable media
•
Loading a driver in the URC using Chromium

Loading drivers in the Universal Recovery Console using portable media

The following tasks are prerequisites for this procedure.

•
Creating a boot CD ISO image
•
Transferring the boot CD ISO image to media
•
Loading the boot CD and starting the target machine

Complete the following procedure to use a portable media device to load drivers in the Universal Recovery Console (URC).

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 boot target server.
5.
On the target server, load the boot CD and start the machine.
The Quest splash screen appears.
6.
To start the URC, click the Quest icon.
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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating