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.
1. |
2. |
In the Virtual Standby pane, identify the machine in your Rapid Recovery Core that is set up for continual export to Azure. |
3. |
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. |
7. |
8. |
On the Destination page in the Export Wizard, in the Export to a virtual machine drop-down menu, select ESX(i). |
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. |
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. |
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.
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.
| |||||||||||||
Click on | |||||||||||||
Click on | |||||||||||||
The virtual machine and path to which data is being exported. | |||||||||||||
The
|
| |||||
Click on | |||||
Click on | |||||
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. |
◦ |
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. |
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: |
This section describes how to restore backed up data.
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:
• |
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy