Rapid Recovery 6.1.2 - User Guide

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:

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.

NOTE: The recovery point used must be part of a complete recovery point chain. For more information about recovery point chains, see the topic Recovery point chains and orphans.

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

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

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

NOTE: In a configuration involving replication, the Core shown represents the target Core. If you have replication set up between two Cores (source and target), you can only export data from the target Core after the initial replication is complete.

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.

NOTE: For Azure, export and eventual deployment creates a VM using the classic VM management, not the newer resource manager model. Working with Azure involves aspects unique to that cloud service provider. For more information, see Before virtual export to Azure.