Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - 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

Manually mapping disks for a BMR

This procedure describes how to designate which disks should be stored in which locations on the restored machine.

To manually map disks, you must first use DiskPart on the Command Line on the BMR target machine to create and format target volumes. For more information, see DiskPart Command-Line Options (Standard 7 SP1) on the Microsoft Developer Network.

Complete the steps in the following procedure to manually select the volumes you want to recover and where to restore them.

5.
CAUTION: If you select Begin Restore, all existing partitions and data on the target drive will be removed permanently, and replaced with the contents of the selected recovery point, including the operating system and all data.

Performing a BMR from an archive

Rapid Recovery lets you restore a machine from bare metal using an archived recovery point.

The following tasks are prerequisites for this procedure.

From the Universal Recovery Console (URC), you can access the Rapid Recovery Core and retrieve a recovery point for a restore. You can also opt to restore your bare metal machine from a recovery point stored in an archive. The URC lets you reach this archive whether it is on a local drive, a network share, or a cloud account.

1.
In the URC, click the Restore from Archive tab.
2.
In the Location Type drop-down list, select the location of your archive. You can choose from the following options.

Table 150. Location type credentials options

Location Type

Option

Description

Local

Local path

The current location of the archive.

Network

Network path

The current location of the archive.

User

The user name for network share access.

Password

The password for network share access.

Cloud

Cloud Type

The provider of your cloud storage location. Select from the following options:

Rackspace® Cloud Files
5.
Click Next.
6.
On the Machines page, select the machine you want to restore, and then click Next.
7.
On the Recovery Points page, select the recovery point you want to use to restore the machine, and then click Next.
8.
On the Mapping page, select one of the following options, and then complete the corresponding steps:
From the Volume Mapping drop-down list, select Automatic.
From the Volume Mapping drop-down, select Manual.
Under Destination Volumes, from the drop-down menu, select the appropriate target volume for each volume in the recovery point.
9.
In the mount maps path text box, enter a destination for the temporary storage of mapping files.

The default location is X:\ProgramData\AppRecovery\IndexEntriesMaps.

10.
Click Restore.
11.
Click Restore.

Loading drivers to the operating system

This procedure describes how to load drivers to the operating system on a bare metal restore (BMR) target.

To inject drivers to the operating system, you have already completed the following tasks:

Created a boot CD using the Boot CD Builder in the Rapid Recovery Core Console. For more information, see Creating a boot CD ISO image.
Performed a restore using either the Restore Machine Wizard in the Rapid Recovery Core Console or an archive from the Universal Recovery Console (URC). For more information, see Performing a bare metal restore using the Restore Machine Wizard and Performing a BMR from an archive.

After you perform a Restore, the process is not complete until you inject the drivers to the operating system on the bare metal restore (BMR) target. This task is in addition to loading drivers in the URC.

5.
Click OK.
6.
Repeat Step 3 through Step 5 for each additional driver you need to load.

Performing a bare metal restore for Linux machines

In Rapid Recovery you can perform a Bare Metal Restore (BMR) for a Linux machine, including a restore of the system volume. When you restore a Linux machine, you will roll back to the boot volume recovery point. BMR functionality is supported using the command line local_mount utility and from within the Core Console UI.

CAUTION: When you boot a restored Linux machine for the first time after a BMR, Rapid Recovery takes a base image of the restored machine. Depending on the amount of data on the machine, this process takes more time than taking an incremental snapshot. For more information about base images and incremental snapshots, see Understanding protection schedules.

To perform a bare metal restore for Linux machines, perform the following tasks.

If you are using auto-partitioning for BMR within the Core Console, you do not need to mount partitions. Rapid Recovery will restore the same partitions as those included in the recovery point(s) being restored.

Related Documents