Chat now with support
Chat mit Support

Rapid Recovery 6.6 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings 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 Snapshots and recovery points Managing privacy Encryption Credentials Vault 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

Managing exports

If your Core has continual export set up, the configuration parameters for each virtual export appear as a row on the Virtual Standby page. From here you can view the status of established continual exports, 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 from your Core Console.

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 one-time export operation.

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 Rapid Recovery 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 134: 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.
    VM Status This column shows for each virtual standby definition whether continual export has been initiated.
    Destination The virtual machine and path to which data is being exported.
    Export Type This column shows the type of virtual machine platform for the export, such as vCenter/ESXi, VMware Workstation, Hyper-V, VirtualBox, or Azure.
    Hypervisor Status This column displays the availability of the hypervisor host.
    Last Export This column shows 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] (More options) 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.
    • Start VM. Starts an already-exported virtual machine.

      NOTE: New data cannot be written to the virtual standby machine when the VM is started.

    • Stop VM. Stops an already-exported virtual machine.
    • Network Adapters. Lets you add or modify virtual network adapters.
    • Deploy Virtual Machine. For Azure continual export only, this option converts the exported files in your Azure account to a bootable VM.
    Table 135: 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. These options include:

    • Cancel. Cancel the current one-time virtual export.
    • Settings. Lets you update the maximum concurrent exports setting.
    Status indicator Shows as a percentage the status of the current export. When no one-time exports are queued, this column has no value.
    Machine Name The name of the source machine.
    Destination The virtual machine and path to which data is being exported.
    Export Type This column shows the type of virtual machine platform for the export, such as vCenter/ESXi, VMware, Hyper-V, VirtualBox, or Azure.
    Schedule Type Click on [Info icon] to see the schedule type. This shows the type of export as either One-time or Continuous.
  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 deploy a VM to Azure, select Deploy Virtual Machine and complete details in the Deploy to Azure Wizard.
    Data from the most recent virtual export saved to your Azure account is deployed within your associated Azure account as a bootable VM.
  5. 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.
  6. To cancel a one-time or continual export currently listed in the Export Queue, select the export, and then click Cancel.
  7. To add a new virtual standby export, you can click Add to launch the Export Wizard. Completing the resulting wizard results in a continual export for the selected protected machine. For further information about setting up virtual standby for a specific virtual machine, see one of the following topics:

     

Restoring data

This section describes how to restore data from recovery points saved to your repository using Rapid Recovery Core.

Topics include:

About restoring data with Rapid Recovery

The Rapid Recovery Core can instantly restore data or recover machines to physical or virtual machines from recovery points. The recovery points contain agent volume snapshots captured at the block level. These snapshots are application aware, meaning that all open transactions and rolling transaction logs are completed and caches are flushed to disk before creating the snapshot. Using application-aware snapshots in tandem with Verified Recovery enables the Core to perform several types of recoveries, including:

  • Recovery of files and folders
  • Recovery of data volumes, using Live Recovery
  • Recovery of data volumes for Microsoft Exchange Server and Microsoft SQL Server, using Live Recovery
  • Bare metal restore, using Universal Recovery
  • Bare metal restore to dissimilar hardware, using Universal Recovery
  • One-time on demand and continual export to virtual machines

NOTE: When you restore data or perform virtual export, 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.

Understanding Live Recovery

Live Recovery is a feature of restoring data in Rapid Recovery Core. If your protected machine experiences data failure of a non-system Windows volume, you can restore data from a recovery point on the Rapid Recovery Core. Selecting Live Recovery in the Restore Machine Wizard allows users to immediately continue business operations with near-zero downtime. Live Recovery during restore gives you immediate access to data, even while Rapid Recovery continues to restore data in the background. This feature allows near-zero recovery-time, even if the restore involves terabytes of data.

Rapid Recovery Core uses unique block-based backup and recovery technology that allows full user access to target servers during the recovery process. Requested blocks are restored on-demand for seamless recovery.

Live Recovery applies to physical and virtual machines protected by Rapid Recovery Agent, with the following exclusions:

  • Live Recovery is accessible to Windows volumes, excluding system volumes. The C:\ drive and the system-reserved partition cannot be restored using Live Recovery.
  • Live Recovery is accessible to Windows-based volumes using the Rapid Recovery Agent. Agentless volumes or Linux volumes cannot take advantage of Live Recovery.

Live Recovery lets you instantly restore physical or virtual servers directly from the backup file. When a non-system volume is being restored, Rapid Recovery presents the volume metadata to the operating system instantly, making that data available on demand. For example, if the database volume of Microsoft Exchange is corrupt, Live Recovery can restore the volume, database, and Exchange services in minutes.

This feature provides the fastest method of recovering large quantities of data with minimal downtime. Users can immediately continue business operations.

Once Live Recovery begins, the restored volume and its contents become instantly available. Rapid Recovery Core continues to restore the data in the background, even though the volume, its data, applications and services are already back in production. If specific data is requested, the background process prioritizes the restoration of this data immediately. This powerful functionality allows even the most stringent service-level agreement to be met.

Once you start Live Recovery, metadata (directory structure, security descriptors, NTFS file attributes, free space map, and so on) of the target volume is quickly restored on the protected machine. Thereafter, the volume and its contents become available to the system. The Rapid Recovery Agent begins restoring data blocks from the Rapid Recovery Core server, writing the blocks to the target volume.

Requests for data that has not yet been restored are immediately answered, with the requesting program or system unaware that the blocks were just restored.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen