Microsoft has substantial documentation on using Azure available in its documentation center.
For information on creating an Azure account, spinning up a VM for use with a Rapid Recovery or AppAssure Core, adding a storage account, and more, see the Microsoft documentation at https://azure.microsoft.com/en-us/documentation.
For example, for information on provisioning or managing Windows VMs, see https://azure.microsoft.com/en-us/documentation/services/virtual-machines/windows/.
For online videos about using Azure, see http://azure.microsoft.com/en-us/get-started/.
Some relevant articles on Microsoft websites are listed below:
Rapid Recovery lets you perform virtual export (one-time, or virtual standby) to Microsoft Azure. This feature is new in Rapid Recovery release 6.1.1.
Before you can perform a virtual export of any machine protected in Rapid Recovery, you must first associate your Azure cloud account with your Core, as described in the topic Adding a cloud account.
Unlike other forms of virtual export using Rapid Recovery, VM export for Azure includes two processes, described in detail in the topic .
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 , 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.
1. |
2. |
3. |
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. |
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. | |||
If you want to add a publish settings file, use the 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. | |||
| |||
| |||
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. |
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. | |||
| |||
Enter a name for the container to hold your VM. |
8. |
Enter a name for the virtual machine. | |||
From the drop-down menu, select an appropriate VM size.
| |||
Select from RemoteDesktop or SSH. | |||
Select from TCP or UDP | |||
Public and private ports use 3389 by default. Change if necessary. | |||
Public and private ports use 8009 by default. Change if necessary. | |||
Public and private ports use 8006 by default. Change if necessary. |
9. |
10. |
On the Volumes page, select the volumes you want to export, and then click Finish to complete the wizard and start the export. |
NOTE: You can monitor the status and progress of the export by viewing the export queue on the Virtual Standby page, or on the Events page. |
Before you can perform continual virtual export to Azure, you need the following:
1. |
◦ |
From the Core Console, in the button bar, click the |
1. |
In the Virtual Machine Export Wizard, select Continuous (Virtual Standby). |
2. |
Click Next. |
◦ |
From the Core Console, in the icon bar, click |
▪ |
2. |
On the Machines page of the Virtual Machine Export Wizard, select the protected machine that you want to export. |
3. |
4. |
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. | |||
If you want to add a publish settings file, use the 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. | |||
| |||
| |||
Specify a name for the folder within the container to store the exported virtual machine. | |||
6. |
7. |
On the Volumes page, select the volumes you want to export, and then click Finish to complete the wizard and start the export. |
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy