Starting with Rapid Recovery 6.1, you can perform continuous (Virtual Standby) virtual export to Microsoft Azure.
Unlike virtual export for other platforms, virtual export for Azure is comprised 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 directly uses 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 otherwise incur 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. Since the deployed VM is a copy of the exported files, the deployment process also doubles the amount of storage space used in Azure for that virtual export.
When establishing virtual standby for a protected machine on Azure, to avoid use of extra storage space and VM charges, you can simply define the export process. The result is an initial virtual export to Azure which is continually updated. Each time a snapshot is captured on the Core, the exported files are refreshed in your Azure account with updated information. Before the virtual export can be used as a bootable VM, you must deploy it, which triggers VM costs on Azure. If you do not need to convert the exported files for a protected machine to a bootable VM, no VM costs are incurred in your Azure account.
For more information on this topic, please see:
NOTE: When creating a storage container you must use Storage accounts (classic) and the Deployment model must be Classic.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center