Azure VMware Solution

Updated

You can deploy Commvault to protect workloads running in the Azure VMware Solution (AVS). The vCenter and hosts reside on high-performance servers in the Microsoft Azure datacenter.

  • The CommServe system (CS) is the machine running Commvault software.

  • The Virtual Server Agent (VSA) manages backups and restores for virtual machines.

  • The MediaAgent (MA) handles data movement.

AVS operates in the same way as an on-premises deployment of VMware, except that Microsoft Azure does not provide access to hosts.

  • vSAN is used as a shared datastore.

For best results, deploy your libraries in an Azure storage account.

For more information, see Azure VMware Solution.

Commvault Deployment and Configuration

For best results, deploy Commvault components on guest VMs on VMware Cloud. The CommServe software, VSA proxies, and MediaAgents can be installed on a single standalone VM, or on separate VMs.

Features

Commvault Version 11, Feature Release 21 and later, supports the following features with AVS:

  • Backups and restores using vStorage APIs for Data Protection (VADP)

  • Changed block tracking (CBT)

  • Full, incremental, differential, and synthetic full backups

  • Restores of full VMs, VMDKs (alone or attaching to a VM), and guest files and folders

  • Agentless file recovery

  • Application-aware backups

  • VM conversion from VMware to Microsoft Azure

  • VM conversion from Microsoft Azure to VMware

  • Live Sync replication and Live Sync Direct for snapshot-based replication

  • Replication from VMware to Microsoft Azure

Limitations

  • Because there is no access to hosts, the following Commvault features are not supported for AVS:

    • Live VM recovery using vMotion

    • Live mount

  • Only HotAdd transport mode is supported. SAN and NBD transport modes do not work with VMware Cloud on Microsoft Azure.

When you restore a VM to a different ESXi host or cluster, you must specify the resource pool and VM folder path for the restored VM.