Add a Google Cloud Platform (GCP) hypervisor to support data protection operations for all instances hosted or managed by the hypervisor.
Caution: For a new Commvault deployment with Service Pack 18 or a more recent feature release, Indexing Version 2 is enabled by default, and new GCP virtualization clients automatically use Indexing Version 2 for VM-centric operations. You can continue to use a GCP virtualization client that was configured before Service Pack 18. The client will continue to use Indexing Version 1. However, beginning with Feature Release 19, backups of any GCP virtualization client that was configured before Service Pack 18 are disabled. To avoid gaps in coverage, you must create new GCP virtualization clients in a recent feature release. These new clients will automatically use Indexing Version 2 for VM-centric operations. Before creating your new GCP clients, if you are running an environment that was configured before Service Pack 18, upgrade your CommServe server and access node directly to Feature Release 20.
Before You Begin
To back up and restore GCP instances, you must create a GCP service account, and then download the JSON file for GCP service account authentication. You will need this file when you add a GCP hypervisor to your environment.
For more information, see Creating a Google Cloud Platform Service Account.
The access node must reside in the Google Cloud and must be connected to a GCP project. You can designate one access node to back up instances from multiple projects (to which access rights are provided in your GCP service account). For faster backups and restores, designate at least one access node for every GCP region.
You can install the Virtual Server Agent (VSA) package on other instances to create one or more additional access nodes for a GCP project.
From the navigation pane, go to Protect > Virtualization.
The Virtual machines page appears.
On the Hypervisors tab, click Add hypervisor.
For Select vendor, select Google Cloud Platform.
For Client name, type a descriptive name for the hypervisor.
For Service account ID, type the GCP service account ID.
For JSON file path, select the JSON file for service account authentication that you downloaded when you created the GCP service account for the associated project.
Note: Starting with Feature Release 22, when you add a new GCP hypervisor to your environment, you must use a JSON file for service account authentication. GCP hypervisors that were created prior to this release use the P12 private key for service account authentication. You can edit these hypervisors to use a JSON file for authentication as well. For more information, see Editing Hypervisor Information.
From the Access node list, select a previously deployed access node.