지금 지원 담당자와 채팅
지원 담당자와 채팅

Rapid Recovery 6.5 - 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 Differences in bare metal restore for Windows and Linux machines 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

Understanding the Classic Summary report

The Classic Summary report provides a summary over the selected period for a variety of useful metrics for your Core.

The top portion includes three pie charts:

  • The first shows job statistics (successful, canceled, and failed jobs).
  • The second pie chart shows space consumed per repository in GB.
  • The third pie chart displays snapshot statistics (successful, canceled, and failed jobs).

Following the pie charts in the report is a trend chart showing repository usage.

Finally, the report includes a summary of protected machines.

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

NOTE: In release 6.2x, this report was known as the Core Nostalgia Report.

Report parameters for this report type include:

  • Date range
  • The Core on which you want to report

VM export

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

Topics include:

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]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 for the protected machine you specify, saving the VM in a location you designate. 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.

Virtual standby deployment

[Virtual standby deployment]

NOTE: In a continual export configuration involving replication set up between two Cores (source and target), you can export from either Core. However, you can only perform virtual export from the target Core after the initial replication is complete.

Subsequently, each time a new snapshot of the protected machine is captured, replication from a source Core queues a new virtual export job after each snapshot is captured. Replication from a target Core queues a new virtual export job after replication job.

Compatible VM hypervisors include vCenter/ESXi, VMware Workstation, Hyper-V, Oracle VM VirtualBox, and Azure. For information about supported versions of these hypervisors, see the topic " Hypervisor requirements" in the Rapid Recovery System Requirements Guide.

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. Exporting to Azure requires you to have an account on Azure, with other prerequisites.

NOTE: Working with Azure involves aspects unique to that cloud service provider. Like all other Azure features in Rapid Recovery, virtual export now uses the Azure Resource Management (ARM) deployment method. Azure setup steps and prerequisites to performing virtual export from the Rapid Recovery Core Console have changed accordingly. For details on Azure prerequisites prior to export, see Before virtual export to Azure.

Related Topics

Exporting data to an ESXi virtual machine

In Rapid Recovery, you can export data to ESXi by performing a one-time export, or by establishing a continual export (for virtual standby). Complete the steps in the following procedures for the appropriate type of export.

Topics include:

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택