IntelliSnap with Microsoft Azure Snapshot Configuration

To use the Microsoft Azure Snap engine, perform the following configuration.

Note

You can run application-consistent disk snapshots for Azure Premium SSD v2 and Ultra Disk types. When the system mounts snapshots of these disk types it does not wait for the Azure clone copy operation to finish. This allows you to run multiple backup copy operations simultaneously by avoiding the significant time delays associated with clone copies of these disk types.

On Azure Linux VMs, turn the LVM metadata cache daemon off.
On the Azure portal, complete the following configuration:
- Enable the Managed Identity feature for the Azure VM. This enables the Commvault software backup and restore processes to use the token-based authentication.
- Assign the contributor role access to the Azure VM at the Azure Resource Groups scope that manages the VM and associated disks. This role access enables the Commvault software backup and restore processes that run in the VM to perform the operations create, attach, and detach on Azure snapshots.
- If the Azure VM is used as the backup copy proxy VM or as the restore target VM, ensure the following:
  - At the Azure Resource Groups scope that manages the VM and the snapshots, assign the contributor role to the Azure VM.
  - Free enough data disk slots to attach the Azure disk snapshots. For example, if the number of backup snapshots is 3, then the backup copy VM must have 3 free data disk slots to attach the Azure disk snapshots.
- If the Azure VM operations take a long time to complete, increase the wait time for the Azure API requests. For more information, see KB article 59831.