There are limitations and known issues for protecting Microsoft Azure VMs with Commvault.
Limitations
-
VMs that have disks encrypted with Azure Disk Encryption can be backed up and recovered. However, guest files on these VMs cannot be restored.
-
Azure has certain limitations and restrictions for snapshot operations on Ultra disks and Premium V2 SSD disks. For information, see Restrictions around Ultra Disk and PremiumSSDv2 disk snapshots.
-
Unix VMs with Azure Ultra Disks or Premium V2 SSD disks can be backed up and recovered. However, guest files on these VMs cannot be restored.
-
Confidential VMs that are encrypted with customer-managed keys (CMKs) cannot be restored to a different Azure subscription or to a different Azure geography.
-
Confidential VMs cannot be restored to a different region from a snapshot copy. To restore confidential VMs to a different region, you must use a backup copy or a streaming copy.
-
Virtual Machine Scale Sets (VMSS) using Uniform orchestration create VMs that are not fully compatible with standard Azure features. These VMs don’t support some Azure APIs needed by Commvault, which limits backup and recovery.
To ensure full compatibility, use Flexible orchestration mode instead.
-
Azure currently supports only crash consistent snapshots for confidential VMs.
Known Issues
- Azure snapshots that were taken with a locked resource group cannot be deleted.
Azure does not allow snapshots to be deleted if they are stored in a locked resource group. To work around this, Commvault Cloud provides an option to select an unlocked (or alternative) resource group dedicated to store backup snapshots. This ensures snapshots can be managed and deleted when needed without affecting locked resources.