# System Requirements for Google Cloud Backup Gateways

You can install a Commvault Cloud backup gateway on a Google Cloud VM to back up Google Cloud instances from one or more projects. It is recommended to have one or more backup gateways in the same region as the VM workload, for better performance. The backup gateway is deployed within your Google Cloud environment, in a VPC (Virtual Private Cloud) that you select to host the gateway and manage its network connectivity.

## Access Nodes

Planning for protection of your Google Cloud VMs with Commvault includes verifying that your environment meets the system requirements and configuring access to the resources you want to protect. This process involves setting up access nodes, which must have the Virtual Server Agent package installed, and adding a hypervisor to manage the backups. For information on how to add a hypervisor and install the access node, see Configuring Backups for Google Cloud Instances.

## Access Node Network Requirements

To back up resources from one or more Google Cloud projects, you must install at least one Commvault access node on a Google Cloud Compute Engine instance.

## Google Cloud APIs & Services

The following APIs and services are required to manage various Google Cloud resources and services:

- Identity and Access Management (IAM) API

- Compute Engine API

- Cloud Resource Manager API

- Cloud Key Management Service (KMS) API

- KMS Inventory API

- Cloud Storage

### gcloud Commands

You can activate these APIs for the Service Account performing protection. Run the following commands in an authorized gcloud shell.

- gcloud services enable iam.googleapis.com

- gcloud services enable compute.googleapis.com

- gcloud services enable cloudresourcemanager.googleapis.com

- gcloud services enable cloudkms.googleapis.com

- gcloud services enable kmsinventory.googleapis.com

- gcloud services enable storage.googleapis.com

For example:

`gcloud services enable service_name`

For information about activating APIs, see Enabling an API.

## Deployment

Commvault does not currently offer a pre-configured access node image in Google Cloud. You can deploy a Compute Engine instance from the Google Cloud Marketplace with your preferred, Commvault-supported operating system, and then install the Commvault software.

### Access Node Location

It is recommended to have at least one (1) access node per Google Cloud Region of the instances you want to protect.

### Access Node Availability

Commvault recommends deploying at least two (2) access nodes, in separate zones, to increase the availability and resilience of your Google Cloud backup and recovery operations. For information on how to set an access node group on the hypervisor, see Configuring Backups for Google Cloud Instances.

## Operating System Support

Ensure you install the Commvault Virtual Server Agent (VSA) corresponding to your CommServer version.

Access nodes for Google Cloud instances must run one of the supported operating systems listed below:

### Linux

- Install the Virtual Server Agent on a Linux machine that runs any of the following operating systems:

  - Rocky Linux 9.x, 8.x, (recommended)

  - Red Hat Enterprise Linux (RHEL) 9.x, 8.x

  - Oracle Enterprise Linux (OEL) 9.x, 8.x

- End of Life (best effort support)

  - CentOS Linux 7.9, 7.8, 7.7, 7.6, 7.5, 7.4

  - Red Hat Enterprise Linux (RHEL) 7.x, see What to know about Red Hat Enteprise Linux 7 End of Maintenance

  - Oracle Enterprise Linux (OEL) 7.x, see Extend your OS upgrade timeline: Oracle Linux 7's Extended Support with expanded coverage)

### Windows

- Commvault supports Microsoft Windows Server Standard, DataCenter, and Core editions:

  - Microsoft Windows Server 2025 x64

  - Microsoft Windows Server 2022 x64

  - Microsoft Windows Server 2019 x64

  - Microsoft Windows Server 2016 x64

## Architecture

Commvault supports the deployment of access nodes and MediaAgents on the following chipset architectures:

- Arm (recommended)

- x86-64 (Intel, AMD)

## Network Requirements

- The access node must have outbound access to the following URLs:

  - https://compute.googleapis.com

  - https://content-cloudkms.googleapis.com

  - https://kmsinventory.googleapis.com

  - https://cloudresourcemanager.googleapis.com

  - https://storage.googleapis.com

- The access node security group must have outbound access to the CommServer and MediaAgents on TCP ports 8400 and 8403.

## Network Gateway Requirements

If the access node cannot reach the Commvault Commserver or MediaAgent(s) directly, you must create one or network proxies to proxy traffic from your Google Cloud VPC to your Commvault infrastructure. To connect to the proxies and domains that are associated with your Commvault environment, see Network Connectivity.

## HTTP/HTTPS Proxy Requirements

You can access the internet by configuring the HTTP/HTTPS proxy to access Google Cloud service endpoints. See, $Using an HTTP Proxy to Access the Internet.

## Configuring a Firewall for Cloud Access Node Deployment

To deploy Commvault software to an access node in the cloud when other components (such as the CommServe) are on premises, configure a firewall to allow communication between the on-premises components and the cloud-based VM or instance. See, Configuring a Firewall for a VSA Proxy in the Cloud for Google Cloud.

Note

By default, when you set the HTTP proxy for Google Cloud, clients bypass metadata.google.internal. Google Cloud only allows metadata API calls from source VMs that make requests. Google Cloud does not allow API requests to be forwarded to the API proxy.

## Storage Requirements

Commvault requires that Google Cloud access nodes meet the following minimum specification:

Components | Extra Small | Small | Medium
--- | --- | --- | ---
CPU/RAM | 2 vCPUs/16 GiB | 4 vCPUs/24 GB | 8 vCPUs/32 GB
Front End Terabytes (FET) | 10 TiB | 25 TiB | 50 TB

Front-End Terabytes (FET) refers to the amount of file-system data written to the compute instance(s) configured for backup. Commvault recommends not exceeding the vCPU/RAM specifications of a Medium instance. Instead, scale horizontally by adding more access nodes.

## DISCLAIMER

Certain third-party software and service releases (together, "Releases") may not be supported by Commvault. You are solely responsible for ensuring Commvault’s products and services are compatible with any such Releases.

×

Loading...