Google Cloud VMware Engine

You can deploy Commvault to protect workloads running in Google Cloud VMware Engine. The vCenter and hosts reside on high-performance servers in the Google Cloud 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.

VMware Engine operates in the same way as an on-premises deployment of VMware, except that Google Cloud does not provide access to hosts.

  • vSAN is used as a shared datastore.

For best results, deploy your libraries in a Google Cloud bucket.

For more information, see Google Cloud VMware Engine and Google VMware Engine IAM roles and permissions.

Commvault Deployment and Configuration

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


Commvault Version 11, Feature Release 22 and later, supports the following features with VMware Engine:

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

  • Changed block tracking (CBT)

  • Full, incremental, 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 GCP

  • Replication from streaming or IntelliSnap backups


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

    • Live VM recovery using vMotion

    • Live mount

  • Only HotAdd transport mode is supported. SAN and NBD transport modes do not work with VMware Engine.

  • 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.

For more information, see Google Cloud VMware Engine documentation.