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

Understanding the Summary report

The Summary report is available for one or more Cores. This report is not available from reports for a protected machine. The Summary report includes information about the repositories on the selected Rapid Recovery Core and about the machines protected by that core. The information appears as two summaries within one report.

For information on how to generate a Summary report, see Generating a report from the Core Console.

Report parameters for this report type include:

When you generate a Summary report, report details include selection criteria for the report, as well as information about repositories and protected machines.

Core information

The Core portion of the Summary Report includes data regarding the Rapid Recovery Core being reported. This information includes:

The current version of the Rapid Recovery Core software

Repositories summary

The Repositories portion of the Summary Report includes data for the repositories located on the selected Rapid Recovery Core. This information includes:

Protected machines summary

The Protected machines portion of the Summary report includes data for all machines protected by the selected Rapid Recovery Core or Cores. This includes a chart and a summary table.

The chart shows protected machines by the ratio of successful jobs (of any type), compared to failed jobs. (Canceled jobs are not considered for these statistics.)

The X or horizontal axis shows the number of protected machines. The Y or vertical axis shows tiers of success. Specifically, the Y axis shows, by protected machine, how many had:

Below the chart, information appears about protected machines. This information includes:

Understanding the Repository report

The Repository report includes information about the repositories on the selected Rapid Recovery Core and about the machines protected by that core. The information appears as two summaries within one report.

For information on how to generate a Repository report from the Core, see Generating a Core report on demand.

Report parameters for this report type include only repositories.

When you generate a Repository report, report details for each repository includes a summary list of repositories on the Core.

VM export

This section describes how to export a recovery point to create a virtual machine.

Exporting to virtual machines using Rapid Recovery

From the Rapid Recovery Core, you can export a recovery point of a Windows or Linux machine from a repository to a virtual machine (VM). If the original machine protected on the Core fails, you can boot up the virtual machine to quickly replace it temporarily, allowing you time to recover the original protected machine without substantial downtime. This virtual export process results in a VM with all of the backup information from a recovery point, as well as the operating system and settings for the protected machine. The VM becomes a bootable clone of the protected machine.

You can perform a virtual export from the Virtual Standby page in the Core Console, or by selecting VM Export from the [Restore] Restore drop-down menu on the button bar.

When you perform a virtual export from Rapid Recovery Core, you have two choices:

You can perform a one-time virtual export, which creates a bootable VM representing a single snapshot in time from the information in the selected recovery point. The export job is queued immediately, and when it completes, the cloned VM exports to the location you specified. The configuration information used for a one-time export is not saved.
You can set up continual export. This process creates a bootable VM from the original recovery point you specified, saving the VM in a location you specify. The configuration information for performing that virtual export is saved in the Virtual Standby page in the Core Console. Subsequently, each time a new snapshot of the protected machine is captured, the Core queues a new virtual export job, and the bootable VM is refreshed with the updated information. Because this creates a high-availability resource for data recovery, this feature is also called virtual standby.

In between the time a virtual export job queues and is completed, the job is listed on the Export Queue pane of the Virtual Standby page in the Core Console.

The following diagram shows a typical deployment for exporting data to a virtual machine.

Figure 5. Virtual standby deployment

[Virtual standby deployment]

Compatible VM hypervisors include vCenter/ESXi, VMware Workstation, Hyper-V, VirtualBox, and Azure.

For ESXi, VMware Workstation, or Hyper-V, the virtual machine version must be a licensed version of these virtual machines, not the trial or free versions. VirtualBox Version 4.2.18 or higher is supported. Exporting to Azure requires you to have an account on Azure, with other prerequisites.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating