Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.

Rapid Recovery 6.0.2 - User Guide

*** Legend Introduction to Dell Data Protection | Rapid Recovery Understanding the Rapid Recovery Core Console Working with repositories Managing Rapid Recovery Core settings Using custom groups Working with encryption keys Protecting machines using the Rapid Recovery Core Working with Microsoft Exchange and SQL Servers Protecting server clusters Exporting protected data to virtual machines Managing protected machines Understanding replication Managing events Generating and viewing reports Restoring data Understanding bare metal restore for Windows machines Retention and archiving Managing cloud accounts Working with Linux machines Understanding the Local Mount Utility Central Management Console Understanding the Rapid Recovery Command Line Management utility Understanding the Rapid Recovery PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Extending Rapid Recovery jobs using scripting Rapid Recovery APIs Glossary

Viewing a cluster or node report

You can create and view job and failure reports about Rapid Recovery activities for your cluster and individual nodes. The reports include Rapid Recovery activity information about the cluster, node, and shared volumes.

For more information about Rapid Recovery reporting, see Generating and viewing reports. For more information about the exporting and printing options located in the reports toolbar, see Using the Reports toolbar.

  1. In the Rapid Recovery Core Console, navigate to the cluster for which you want to create a report.
  2. If you want to create a report for a node under a cluster, select the node.
  3. On the Summary page for the machine, click the Reports drop-down menu, and then click one of the following options:
    • If you want to generate a report on all jobs pertaining to this protected machine, including failed jobs, click Job Report, and begin specifying your report criteria.
    • If you want to generate a list of failed jobs only pertaining to this protected machine, click Failure Report, and begin specifying your report criteria.
  4. For a Job or Failure report, from the Date Range drop-down menu, select a date range.

    If you do not choose a date range, the default option (Last 31 days) is used. You can choose from the options in the following table.

    Option Description
    Last 24 hours Reports activity for the last day, relative to the time you generate the report.
    Last 7 days Reports activity for the last week, relative to the time you generate the report.
    Last 31 days Reports activity for the last 31 days, relative to the time you generate the report.
    Last 90 days Reports activity for the last 90 days, relative to the time you generate the report.
    Last 365 days Reports activity for the last year, relative to the time you generate the report.
    All Time This time period spans the lifetime of the Core.
    Custom This time period requires you to further specify start and end dates.
    Month to date Reports activity from the first day of the current calendar month to the date you generate the report.
    Year to date Reports activity from the first day of the current calendar year to the date you generate the report.
    Note: In call cases, no report data is available before the Core software was deployed, or from before machines were protected on the Core.
  5. From the Job Types drop-down menu, select the appropriate job types.

    By default, this set of information includes all jobs for the selected protected machines. In the report parameters, you can customize the report. Use the filters to select or exclude every job in the Main Jobs category, and every job in the Other Jobs category. Or you can expand each of these categories when defining job parameters, and select only the job types from either category that you want to appear in the report. Click the checkbox for any job type to select or clear that type. You can select some or all jobs from either category.

    For more information about job types, see

  6. Click Preview to generate the report with the specified criteria.

    If the report criteria you selected is not found, the report still generates, but the report contains an empty row. For example, if there are no errors, the contents of the Error column are null in the report.

  7. Do one of the following:
    • View the generated report online.
    • Update the report dynamically by changing any of the criteria; then click Preview again.
    • Use the Reports menu to select an export format and export the report. For more information about the Reports menu, see Using the Reports menu.
    • Use the Reports toolbar to view, manipulate, or print the report. For more information about the Reports toolbar, see Using the Reports toolbar.

Was this topic helpful?

[Select Rating]



Exporting protected data to virtual machines

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


Was this topic helpful?

[Select Rating]



About exporting to virtual machines with Rapid Recovery

From the Rapid Recovery Core, you can export a recovery point from a repository to a virtual machine. This process—sometimes called virtual export—is a physical-to-virtual (P2V) process that creates a virtual machine from a recovery point. The VM is a bootable clone of a 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 represents a single snapshot in time from the information in the recovery point.
  • You can create a virtual standby. With virtual standby, the VM snapshot that you create from the selected recovery point is continually updated by the Core after every scheduled or forced snapshot captured from the source machine. This creates a high-availability resource for data recovery. If the protected machine 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.

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

Figure 1. Virtual standby deployment [Virtual standby deployment]
Note: In a configuration involving replication, the Core shown represents the target Core.

When you export to a virtual machine, the following information is exported:

  • All of the backup data from a recovery point
  • The operating system and settings from the original protected machine

You can perform virtual export of recovery points for your protected Windows or Linux machines to VMware, ESXi, Hyper-V, and VirtualBox.

Note: 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.

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.


Was this topic helpful?

[Select Rating]



Managing exports

If your Core has virtual export established, the configuration parameters for each virtual export appear as a row on the Virtual Standby page. From here you can view the status of exports that you currently have set up, and manage your virtual standby machines. You can add a virtual standby, force export, pause or resume virtual standby, or remove the requirements for continual export.

When a one-time export takes place, the job is listed in the export queue on the Virtual Standby page. During this time, you can pause, resume, or cancel the export operation.

Note: Rapid Recovery supports Hyper-V export to Window 8, Window 8.1, Windows Server 2012 and 2012 R2.

Virtual export to a virtual standby VM does not occur if the VM is powered on.

Complete the steps in this procedure to manage virtual exports.

  1. On the Core Console, in the icon bar, click [Virtual Standby] (Virtual Standby).
    The Virtual Standby page appears. Here you can view two tables of saved export settings. They include the information described in the following table.
    Table 1. Virtual standby information
    Column Description
    Select item

    For each row in the summary table, you can select the check box to perform actions from the list of menu options preceding the table.

    Status indicator

    Colored spheres in the Status column show the status of virtual standby. If you hover the cursor over the colored circle, the status condition is displayed.

    • Green. Virtual standby is successfully configured, is active, and is not paused. The next export is performed immediately following completion of the next snapshot.
    • Yellow. Virtual standby pauses, but the parameters are still defined and saved in the Core. However, after a new transfer, the export job will not start automatically and there will be no new exports for this protected machine until the status changes.
    Machine Name The name of the source machine.
    Destination The virtual machine and path to which data is being exported.
    Export Type The type of virtual machine platform for the export, such as ESXi, VMware, Hyper-V, or VirtualBox.
    Last Export The date and time of the last export.

    If an export has just been added but has not completed, a message displays stating the export has not yet been performed. If an export has failed or was canceled, a corresponding message also displays.

    Settings The [Settings] drop-down menu lets you perform the following functions:
    • Edit. Lets you edit the virtual standby settings.
    • Force. Forces a virtual export.
    • Pause. Pauses virtual export. Only available when status is active.
    • Resume. Resumes virtual export. Only available when status is paused.
    • Remove. Removes the requirement for continual export. Does not remove the exported VM most recently updated.
    Table 2. Export queue information
    Column Description
    Select item

    For each row in the summary table, you can select the check box to perform actions from the list of menu options preceding the table.

    Destination The virtual machine and path to which data is being exported.
    Export Type The type of virtual machine platform for the export, such as ESXi, VMware, Hyper-V, or VirtualBox.
    Schedule Type The type of export as either One-time or Continuous.
    Status The progress of the export, displayed as a percentage in a progress bar.
  2. To manage saved export settings, select an export, and then click one of the following:
    • Edit. Opens the Virtual Machine Export Wizard to the VM Options page. Here you can change the location of the exported VM, change the version of the VM type, or specify RAM or processors for the export. To immediately start the VM export, select Perform initial one-time export.
    • Force. Forces a new export. This option could be helpful when virtual standby is paused and then resumed, which means the export job will restart only after a new transfer. If you do not want to wait for the new transfer, you could force an export.
    • Pause. Pauses an active export.
    • Resume. Resumes the requirement for continue export at the next scheduled or forced snapshot.
  3. To remove an export from the system, select the export, and then click Remove.
    The export configuration is permanently removed from the system. Removing the virtual standby configuration does not remove any virtual machine exported as a result of the configuration.
  4. To manage the number of exports that run at the same time, do the following:
    • Under Export Queue, click Settings.
    • In the Maximum Concurrent Exports dialog box, enter the number of exports you want to run simultaneously. The default number is 5.
    • Click Save.
  5. To cancel a one-time or continual export currently listed in the Export Queue, select the export, and then click Cancel.
  6. To add a new virtual standby export, you can click Add to launch the Export Wizard. For further information about setting up virtual standby for a specific virtual machine, see one of the following topics:

Was this topic helpful?

[Select Rating]



Related Documents