Configuring staging location for Azure Stack Hub VMs to restore from backup
The Azure Stack Hub requires you to create a container, inside your storage account, and use it as a staging location when you restore from backup images. The staging location is used to stage the unmanaged disks in the container during restores. Once the data is written to the disk, the disks are converted to managed disks. This is a requirement from the Azure Stack Hub platform. This is a mandatory configuration, before you can use Azure Stack Hub with NetBackup.
The azurestack.conf file should contain staging location details of the subscription ID, where the VMs are restored. If you plan to restore to any target subscription ID, other than the source subscription ID, then details of the target subscription ID must be present in the azurestack.conf file.
If you are using snapshot images for restore, you do not need to create this staging location.
Note:
The staging location is specific to the subscription ID, you must create one staging location for each subscription that you are using to restore VMs.
To configure a staging location for a subscription ID:
- In the CloudPoint server, navigate to:
/cloudpoint/azurestack.conf,and open the file in a text editor. This file is created, only after you have added Azure Stack Hub as a cloud service provider in NetBackup. - Add the following details in the file:
[subscription/
<subscription ID>]storage_container =
<name of the storage container>storage_account =
/resourceGroup/<name of the resource group where the storage account exists>/storageaccount/<name of storage account>For example:
/resourceGroup/Harsha_RG/storageaccount/harshastorageacc - Repeat step 2, for each subscription ID that you are using. Save and close the file.