Protect Azure Virtual Machines

Commvault provides protection and recovery for Microsoft Azure Virtual Machines. It uses Azure-native APIs to create VM snapshots, protect Azure VM resources, and restore data at the file, disk, or VM level.

You can protect Azure workloads by using Commvault-hosted infrastructure or self-managed infrastructure. Azure VM protection supports policy-based automation, immutable storage options, cyber resilience workflows, and recovery across subscriptions and regions.

What's supported

Supported configurations

  • Azure Resource Manager (ARM) deployments

  • Windows and Linux VMs

  • Trusted Launch, Standard, and Confidential VMs

  • Generation 1 and Generation 2 VMs

  • Azure Disk Encryption (ADE)

  • Server-side encryption (SSE)

  • Encryption at host

Protected resources

Commvault protects the following Azure VM resources:

  • Azure VMs

  • Managed disks

  • Network interface cards (NICs)

  • Assigned identities

  • Availability zone information

  • Azure Proximity Placement Groups (PPGs)

  • VM extensions

  • Elastic SAN volumes (requires manual configuration and must be available when the VM is running)

Supported for in-place restores

In-place restores can recreate the following Azure networking resources:

  • Virtual networks (VNets)

  • Subnets

  • Network security groups (NSGs)

  • Route table associations

  • NAT gateway associations

  • DDoS protection associations

  • Service endpoints

  • Subnet delegations

  • Network interface cards (NICs)

What's not supported

The following Azure VM resources and configurations aren't supported:

  • Shared or network-mounted drives

  • Temporary disks

  • Azure Bastion

  • VNet peering

  • Azure Firewall

  • Azure Network Manager

  • Private endpoints

Restore limitations

Review the following restore limitations when planning Azure VM protection:

  • Guest file restore isn't supported for:

    • VMs that use Azure Disk Encryption (ADE)

    • Unix VMs that use Ultra Disks or Premium SSD v2 disks

  • Confidential VMs that use customer-managed keys (CMKs) can't be restored to a different Azure subscription or Azure geography.

  • Confidential VMs can't be restored to a different region from a snapshot copy. To restore confidential VMs to a different region, use a backup copy or streaming copy.

Platform limitations

The following Azure platform limitations can affect backup and restore operations:

  • Azure currently supports only crash-consistent snapshots for confidential VMs.

  • Azure snapshot restrictions for Ultra Disks and Premium SSD v2 disks can affect backup and restore operations.

  • Virtual Machine Scale Sets (VMSS) that use Uniform orchestration mode have Azure platform limitations that can affect backup and restore operations. For full compatibility, use Flexible orchestration mode.

×

Loading...