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

Deploying a virtual machine in Azure

Before you can deploy a VM in Azure, you must have a protected machine on a Rapid Recovery Core with at least one recovery point, and you must set up continual export (virtual standby) in the Core Console. For more information about setting up continual export, see . This process also requires you to have an Azure account with sufficient storage associated with your Core.

When you set up virtual standby for a protected machine to Azure, the latest backup information is continually exported from the Core to your Azure account after every backup snapshot. This process overwrites the previous set of export files with updated backup information. Before you can boot the virtual export as a VM (for example, if your original protected machine has failed), you must first deploy from the Core Console. This process generates a bootable VM in a new container

Complete the steps in this procedure to deploy your most recent virtual standby export files to a bootable VM in Azure.

1.
From the Rapid Recovery Core Console, in the icon bar, click [Virtual Standby] (Virtual Standby).
2.
In the Virtual Standby pane, identify the machine in your Rapid Recovery Core that is set up for continual export to Azure.
The Deploy to Azure Wizard appears.
4.
On the Destination page, from the Cloud service name drop-down menu, select the appropriate cloud service name from the options available in your Azure account.
5.
Click Next.
7.
Click Next.
8.
On the Destination page in the Export Wizard, in the Export to a virtual machine drop-down menu, select ESX(i).

Table 138. Virtual machine parameters

Options

Description

Cloud service name

If you have an existing cloud service, from the Cloud service name drop-down menu, select the appropriate cloud service name. Or, in the Cloud service name field, type a unique, meaningful name for the cloud service.

The cloud service name is associated with your resource group in your Azure account. If you have Azure administrative privileges, see Azure documentation to create the appropriate account. If you do not see an appropriate cloud service account, request assistance from your Azure administrator.

Deployment name

If you selected a cloud service with existing virtual machines, this field is completed automatically. If you selected a cloud service that includes no virtual machines, then enter a name for this new deployment.

Destination container

Enter a name for the container to hold your VM.

Table 139. Virtual machine options

Option

Description

Virtual machine name

Enter a name for the virtual machine.

Virtual machine size

From the drop-down menu, select an appropriate VM size.

NOTE: For more information on Azure configurations and pricing, see the virtual machines pricing page on the Azure website. For links to other useful references on Microsoft websites, see .

Endpoint (remote access settings)

Name

Select from RemoteDesktop or SSH.

Protocol

Select from TCP or UDP

Ports

Public and private ports use 3389 by default. Change if necessary.

Transfer data server ports

Public and private ports use 8009 by default. Change if necessary.

Agent ports

Public and private ports use 8006 by default. Change if necessary.

11.
On the Disks page, select the volumes you want to export, and then click Finish to close the wizard and start the deployment.

Once the deployment completes, in your Azure account, you can see the new VM in Azure's View machines (classic) view. Once the VM is available, you are also paying fees. To avoid continuing charges, delete the deployed VM when not needed. You can always deploy a VM from the latest set of virtual export files by repeating this procedure.

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.

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.

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 140. 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.

Export Type

Click on [Info icon] to see the export type. This shows the type of virtual machine platform for the export, such as ESXi, VMware, Hyper-V, VirtualBox, or Azure.

Last Export

Click on [Info icon] to see the export type. This 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.

Destination

The virtual machine and path to which data is being exported.

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.
Deploy Virtual Machine. For Azure continual export only, this converts the exported files in your Azure account to a bootable VM.

Table 141. 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.

Export Type

Click on [Info icon] to see the export type. This shows the type of virtual machine platform for the export, such as 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.

Destination

The virtual machine and path to which data is being exported.

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.
4.
To deploy a VM to Azure, select Deploy Virtual Machine and complete details in the Deploy to Azure Wizard.
In the Maximum Concurrent Exports dialog box, enter the number of exports you want to run simultaneously. The default number is 5.
Click Save.
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 backed up data.

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:

Related Documents