Chat now with support
Tchattez avec un ingénieur du support

Rapid Recovery 6.3 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings Managing privacy Encryption Protecting machines
About protecting machines with Rapid Recovery 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 Enabling application support Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Credentials Vault Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore BMR Windows and Linux Understanding boot CD creation for Windows machines Managing a Linux boot image Performing a bare metal restore using the Restore Machine Wizard Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Verifying a bare metal restore
Managing aging data Archiving Cloud accounts Core Console references REST APIs Glossary

Performing a BMR from an archive

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

NOTE: This topic applies to Windows machines. If you want to restore a Linux machine from an archive, see performing a BMR for a LInux machine from a Linux archive.

The following tasks are prerequisites for this procedure.

From the Universal Recovery Console (URC) on a Windows-based BMR target machine, you can perform a bare metal restore from a recovery point stored in a Rapid Recovery archive. The URC lets you reach this archive whether it is on a local drive, a network share, or a cloud account.

NOTE: This procedure assumes you have an archive from which to restore, and a boot CD ISO image; and that you have started the BMR target machine from the boot ISO image.

  1. From the Universal Recovery Console of the BMR target machine, click Restore from Archive.

    The Restore from Archive tab displays the Location page, and shows the remaining steps required to restore from an archive.

  2. From the Location type drop-down menu, select the location of your archive. You can choose from the following options.
    • Local
    • Network
    • Cloud
  3. Based on the location type selected in the previous step, enter the credentials described in the following table.
    Table 146: Location type credentials options
    Location Type Option Description
    Local Local path

    The current location of the archive.

    For example, D:\work\archive.

    Network Network path

    The current location of the archive.

    For example: \\machine\shared_folder\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:
    • Microsoft Azure
    • Amazon S3
    • Powered by OpenStack
    • Rackspace Cloud Files
    • Google Cloud
    • Microsoft Azure Resource Management
  4. If you selected a cloud type, complete the credentials that pertain to your cloud provider.
    • For Microsoft Azure, complete the following steps:
      1. Enter the following credentials:
        • Storage Account Name
        • Access Key
      2. For the Container name, from the drop-down list, select a container.
      3. For the Cloud path, from the drop-down list, select the path to the archive.
    • For Amazon S3, complete the following steps:
      1. Enter the following credentials:
        • Access key
        • Secret key
      2. For the Container name, from the drop-down list, select a container.
      3. For the Cloud path, from the drop-down list, select the path to the archive.
    • For Powered by OpenStack or Rackspace Cloud Files accounts, complete the following steps:
      1. Enter the following information:
        • Region
        • User
      2. Select one of the following options:
        • Password
        • API Key
      3. In the text box, enter the information based on your selection in Step c.
      4. Enter the following information:
        • Tenant ID
        • Authentication URL
      5. For the Container name, from the drop-down list, select a container.
      6. For the Cloud path, from the drop-down list, select the path to the archive.
    • For Google Cloud accounts, complete the following steps:
      1. Upload the certificate file
      2. Enter the following credentials:
        • Private key
      3. Enter the following information:
        • Project ID
        • Service account email
      4. For the Container name, from the drop-down list, select a container.
      5. For the Cloud path, from the drop-down list, select the path to the archive.
      6. If prompted for the Bucket name, from the drop-down list, select the appropriate bucket.
  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.
      1. In the left table, verify that the appropriate volumes are listed and are selected.

        NOTE: Typically for a BMR, you should restore, at minimum, the system reserved volume and the system volume (usually, but not always, the C:\ volume). You must select at least one volume to perform a BMR.

      2. In the right table, select the disk or disks to which you want to map volumes on the target machine.
    • From the Volume Mapping drop-down list, select Manual.

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

       

      NOTE: If no volumes exist on the drive of the machine on which you are performing a bare metal restore (BMR), you cannot see this option or manually map volumes.

    • 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.

    NOTE: To ensure that your destination has sufficient free space, divide the total mount volume capacity by 1,024. For example, using the formula (Mount volume total capacity) / 1024 = Free space, then 1 TB / 1024 = 1 GB.

  10. Click Restore.
    The URC maps the volumes to the new disk or disks.
  11. Click Restore.
    The URC restores the data to the target machine. You can view the progress on the Restore progress tab.
  12. After the restore is complete, remove the boot CD.
  13. To boot the BMR target machine into Windows, restart the machine.

Loading drivers to the operating system

This procedure describes how to load drivers to the operating system on a bare metal restore (BMR) target. You can use this procedure to troubleshoot driver conflicts for the restored machine.

After performing a BMR, you can load or inject additional drivers to the OS of the restored machine from the URC. You must have the drivers accessible in a compressed format.

  1. From the URC of the BMR target machine, click Existing Windows driver management.

    The Existing Windows driver management tab of the console appears.

  2. From the drop-down list, select an operating system.
    The URC searches for available drivers.
  3. To load additional drivers, click [Force Load] Force Load.
  4. Navigate through the filing system to locate the compressed driver file, and then select the file.
  5. Click OK.
    The URC loads the driver into the operating system you selected.
  6. Repeat step 3 through step 5 for each additional driver you need to load.
  7. Restart the BMR target machine.
    The BMR is complete. If you experience an issue when you restart, see Repairing boot problems.

Performing a bare metal restore for Linux machines

In Rapid Recovery, you can perform a Bare Metal Restore (BMR) for a protected Linux machine, including a restore of the system volume. BMR functionality is supported for Linux using the Restore Machine Wizard from the Core Console, and also using the command line local_mount utility.

Caution: Rapid Recovery supports ext2 partition types only if the kernel is version 3.10 and above. If using an earlier kernel, convert any ext2 partitions to ext3, ext4, or XFS before you begin protecting and backing up the machine.

 

Caution: When you boot a restored Linux machine for the first time after a BMR, Rapid Recovery Core first attempts to capture an incremental snapshot of the restored machine. If incremental capture is not possible due to the amount of data and the state of the machine, then Rapid Recovery Core captures a base image of the restored 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.

Managing Linux partitions

When performing a BMR, the destination drive onto which you will be restoring data must have the same partitions as in the recovery point you are restoring. You may need to create partitions to meet this requirement.

You can launch the restore from the command line using the local_mount utility, or you can launch the restore from the Rapid Recovery Core Console. If restoring using the user interface, you must first mount the partitions.

Managing Linux partitions is a step in Performing a bare metal restore for Linux machines.

You can perform the following tasks:

Documents connexes