Chat now with support
Chat with Support

Rapid Recovery 6.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings
Core settings key functions Rapid Recovery Core settings Core-level tools
Repositories 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 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 Verifying a bare metal restore
Managing aging data Archiving Cloud accounts The Local Mount Utility Core Console references REST APIs About us Glossary

Performing a one-time Azure export

Before you can perform a one-time Azure export, you need the following:

You must have a protected machine with at least one recovery point in a Rapid Recovery Core that you want to export to Azure.

As described in the topic Exporting and deploying VMs for Azure, virtual export to Azure consists of two processes: exporting and deploying.

The process of exporting extracts the necessary set of files from Rapid Recovery, validates them, and uploads them to the specified container in Azure. These files include:

The deployment process combines these files into a bootable virtual machine. Deployment uses direct Azure cloud REST APIs. The original set of files placed on Azure during the export process is read-only in Azure, and consumes space but does not invoke additional Azure charges. When you deploy these files, a duplicate copy of them is created, stored in a separate container you define, and combined into a working virtual machine. From an Azure account perspective, after you deploy you are then charged fees for the VM on its servers. The deployment process also doubles the amount of storage space used in Azure for that virtual export.

For a one-time virtual export, there is no mechanism for deploying as a separate process; thus, for the export to be useful, you should deploy when you create the virtual machine on demand.

When establishing virtual standby for a protected machine on Azure, to avoid use of extra storage space and VM charges, you can export, and continually update the recovery point automatically, without the need to deploy. You can then deploy in Azure only when and if you need to use the VM. For information about deploying a virtual standby in Azure to a functioning VM, see the topic Deploying virtual standby data to a VM on Azure.

Complete the steps in this procedure to perform a one-time export to Azure on demand, including deploying to a VM.

1.
From the Rapid Recovery Core Console, click the [Restore] Restore drop-down menu, and then select VM Export.
2.
In the wizard, from the Select VM Export Type page, select One-time export and then click Next.
The Machines page of the wizard appears.
3.
On the Machines page, select the protected machine that you want to export, and then click Next.
4.
On the Recovery Points page, scroll through the list of recovery points if necessary, and select the recovery point that you want to use for the export. Then click Next.
5.
On the Destination page, from the Export to a virtual machine drop-down menu, select Azure.

Table 127. Azure credentials

Options

Description

Publish settings file

The publish settings file is an XML document generated on Azure that contains management certificates for Azure subscription information.

When prompted for this file, log into your Azure account, and download it from your VM at https://manage.windowsazure.com/publishsettings/index?client=powershell.

The file defines the AzureServiceManagement API and information about your Azure subscription, including secure credentials. This file must be defined in the Rapid Recovery Core before you can connect to your account and perform a virtual export.

For security purposes, store the file in a secure location or delete it after using it in this procedure.

Subscription

If you just added a publish settings files, then this information is automatically entered with information from the publish settings file.

If you want to use a previously added publish settings file, use the drop-down list to select a file.

If you want to add a publish settings file, use the button to open the Load Certificate window and browse for the file.

When prompted for this file, log into your Azure account, and download it from your VM at https://manage.windowsazure.com/publishsettings/index?client=powershell.

For security purposes, store the file in a secure location or delete it after using it in this procedure.

Account

Automatically entered from the subscription file, it is the Azure cloud account that has been associated with your Core.

Container name

From the drop-down menu, select the name of an appropriate container associated with your Azure cloud account if a container already exists. Or, enter a name for a new container.

Folder name

Specify a name for the folder within the container to store the exported virtual machine.

7.
On the Deploy page, enter a destination for the deployed VM, as described in the following table, and then click Next.

Table 128. Deploy to Azure options

Option

Description

Cloud service name

The Azure cloud service is a container for virtual machines using the classic management model. 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.

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.

8.
On the Virtual Machine Options page, enter the information described in the following table.

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

Following are VM options for 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.

9.
Click Next.
10.
On the Volumes page, select the volumes you want to export, and then click Finish to complete the wizard and start the export.

Setting up continual export to Azure

Before you can perform continual virtual export to Azure, you need the following:

You must have a protected machine with at least one recovery point in a Rapid Recovery Core that you want to export to Azure.

Complete the steps in this procedure to perform a continual virtual export of the selected machine to a specified container in an Azure cloud account using Rapid Recovery.

1.
In the Rapid Recovery Core Console, do one of the following:
From the Core Console, in the button bar, click the [Restore] Restore drop-down menu, and then select VM Export.
1.
2.
Click Next.
On the Virtual Standby page, click [Add] Add to launch the Virtual Machine Export Wizard.
2.
On the Machines page of the Virtual Machine Export Wizard, select the protected machine that you want to export.
3.
Click Next.
4.
On the Recovery Points page, select the recovery point that you want to use for the export.
5.
Click Next.
6.
On the Destination page, from the Export to a virtual machine drop-down menu, select Azure. .

Table 130. Azure credentials

Options

Description

Publish settings file

This option only appears if you have not yet associated your Azure subscription with your Core. If you see this option, download the file as described in the topic Obtaining the Publish Settings file for your Azure account, and associate your subscription with the Core. This association must be completed before you can connect to your Azure account from within the Core and perform a virtual export.

For security purposes, store the file in a secure location or delete it after using it in this procedure.

Subscription

If you just added a publish settings files, then this information is automatically entered with information from the publish settings file.

If you want to use a previously added publish settings file, use the drop-down list to select a file.

If you want to add a publish settings file, use the button to open the Load Certificate window and browse for the file.

Account

Automatically entered from the subscription file, it is the Azure cloud account that has been associated with your Core.

Container name

From the drop-down menu, select the name of an appropriate container associated with your Azure cloud account if a container already exists. Or, enter a name for a new container.

Folder name

Specify a name for the folder within the container to store the exported virtual machine.

Perform initial one-time export

When defining virtual standby, select this option to queue the export job immediately. Clear this option if you want the Core to wait until the next forced or scheduled backup snapshot.

8.
Click Next.
9.
On the Volumes page, select the volumes you want to export, and then click Next.
10.
On the Summary page, click Finish to complete the wizard and start the export.

The virtual standby parameters you define in this procedure cause the export of the files necessary to create a VM in your Azure account. After every snapshot (forced or scheduled), these files are updated in Azure with any new backup information. Before you can boot these files as a VM, you must deploy the VM on Azure. For steps on deploying, see Deploying a virtual machine in Azure.

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 Setting up continual export to Azure. 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 131. 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 132. 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.

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

Table 134. 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:
Related Documents