The Microsoft® Azure™ interface is subject to change.
Complete the steps in this procedure to create a container in an Azure storage account.
2. |
3. |
From the All resources pane, click the name of the storage account in which you want to store data from your Rapid Recovery virtual exports. |
4. |
5. |
6. |
7. |
From the New container pane, from the Access type drop-down menu, select the appropriate container type, which defines whether the container can be accessed publicly. Use the following as guidance. |
This option allows public read access for Binary Large Objects (Blobs). | |
This option allows public read and list access to the entire container. |
8. |
The Blob service page refreshes, with the new container name displayed in the list.
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:
Other than costs for the required storage, exporting by itself does not incur any Azure fees.
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.
For information about performing a one-time export to Azure, including deployment, see the topic .
For information about setting up continual export to Azure, excluding deployment, see the topic .
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy