Rapid Recovery 6.1.3 - User Guide

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

3.	From the row representing the virtual standby machine you want to deploy, click and from the drop-down menu, select Deploy Virtual Machine.

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.   NOTE: Microsoft Azure subscriptions have default limits on the number of cloud services (typically 25). Ensure that you do not exceed your subscription limits.
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.   NOTE: Type a name between 3 and 63 characters, using only lowercase letters, numbers, and hyphens.
Destination container	Enter a name for the container to hold your VM.   NOTE: Type a name between 3 and 63 characters, using only lowercase letters, numbers, and hyphens.

Table 139. Virtual machine options

Option	Description
Virtual machine name	Enter a name for the virtual machine.   NOTE: Type a name between 3 and 15 characters, using only lowercase letters, numbers, and hyphens.
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.

NOTE: You can monitor the progress of the deployment by viewing tasks on the Events page.

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.

1.	On the Core Console, in the icon bar, click (Virtual Standby).

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:

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.