Setting up an Azure target

R‑Cloud supports using an Azure target to store data in the highly available, scalable, and secure Azure cloud storage.

Prerequisites

  • An Azure service principal must be added to R‑Cloud. For instructions, see Adding an Azure service principal.

  • Only if you plan to use the HYCU Managed Service Principal (HMSP) for performing all operations on the target. An Azure resource group must be added to R‑Cloud. For instructions, see Adding an Azure resource group.

  • Only if you plan to store data to an Azure target for which immutability (WORM) is enabled. You must do the following in Azure:

    • Set the Enable version-level immutability support option at the storage account level. For details, see Azure documentation.

    • Assign the Storage Blob Data Owner role to the service principal. For a list of all the required roles, see Adding an Azure service principal.

Limitations

  • Storing data to a publicly available target is not supported. Therefore, make sure that the Allow Blob anonymous access setting is disabled in Azure.

  • Storing data to a target for which a lifecycle management policy is configured is not supported and may result in data loss.

  • Only StorageV2 (general-purpose v2) storage accounts can be set up as a target.

Considerations

  • You can set up the same target in multiple protection sets.

  • Only if you plan to store data to an Azure target for which immutability (WORM) is enabled. When backing up data, R‑Cloud sets the retention period of the immutable blob data to the retention period defined in the R‑Cloud policy.

To access the Targets panel, in the navigation pane, click Targets Targets. Alternatively, in the Dashboard panel, click the Targets widget title.

Procedure

  1. In the Targets panel, click Add Add.

  2. Select Azure, and then click Next.

  3. In the Storage Account Name field, enter the name of the Azure storage account that will store backup data.

  4. In the Size Quota field, specify the amount of storage space that should be used for storing data (in MiB, GiB, or TiB).

    Important  The specified amount represents a soft limit, therefore actual usage may exceed it.

  5. Use the Enforce quota switch to stop running backups if this target reaches its size quota. The backups will start running again after you increase the size quota of this target or assign a different policy to the entities. Such a policy must use a target with the sufficient size quota.

  6. Only if you want a service principal other than the HMSP to be used for performing all operations on the target. From the Cloud Account drop-down menu, select the Azure service principal that you want to be used for performing all operations on the target.

    By clicking Add, you are automatically redirected to the dialog box that enables you to add the preferred cloud account to R‑Cloud, if not already added.

  7. Click Grant Consent to be automatically redirected to the Azure portal where you assign the permissions for managing and using the Azure target to your Azure service principal.

    In the Azure portal, you must select the following:

    • The subscription

    • The resource group

    • Only if you selected the HMSP for performing all operations on the target. The Object ID of the HMSP

    For details, see Azure documentation.

  8. Click Save.

The target is added to the list of targets in the Targets panel. For details on managing targets, see Managing targets.