System Requirements for the Virtual Server Agent with Google Cloud Platform (GCP)
The following requirements are for the Virtual Server Agent with GCP.
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 VSA proxy directly to Feature Release 20.
Virtual Server Agent Proxies
- The Virtual Server Agent can be installed on GCP instances running the following operating systems:
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2
- CentOS Linux 7 or 8
- Red Hat Enterprise Linux (RHEL) 7.6 or 8
- The VSA proxy must reside in the Google Cloud and must be connected to a GCP project. You can designate one VSA proxy 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 VSA proxy for every GCP region.
Important: You must enable the Cloud Resource Manager API. If you do not enable the API, all backup jobs will fail (including backup jobs for clients that were created in a previous release).
Important: You can define discovery rules by a project parameter in addition to region and zone parameters.
If an environment has discovery rules that are defined using zone or region parameters, then the following are true:
- Multiple projects can fall within a region or a zone.
- All instances in those multiple projects are backed up.
In this situation, backups might include instances that do not need to be backed up, and so incur unnecessary costs. Review all rules to ensure that only instances that need to be backed up are backed up.
Tunnel ports (for example, 8400 and 8403) must be opened in the security group for the instance to enable installation of the Virtual Server Agent to GCP instances and communication with the CommServe system.
If you deploy a CommServe host in an environment with firewalls, create a persistent route from the CommServe host to the VSA proxy, as documented in Setting Up Proxy Connections Using a Predefined Network Topology.
Specify the RESTRICTED setting for connections from the CommServe host to the VSA proxy and the BLOCKED setting in the CommServe node settings for the proxy. See Restricting or Blocking Connections for more information.
If a firewall proxy is installed, configure Internet options for the firewall proxy machine. On the HTTP Proxy tab of the Internet Options dialog box, enter the user name and password for the firewall proxy machine, using only the user name and not including the domain name with the user name.
Configuring a Firewall to Install the Virtual Server Agent on a Cloud VM or Instance
To deploy the Virtual Server Agent (VSA) or MediaAgent on a cloud VM or instance when other components (such as the CommServe host) are on premises , configure a Commvault firewall connection between the on premises components and the cloud VM or instance.
For information about hardware requirements for the Virtual Server Agent, see Hardware Specifications for Virtual Server Agent.
Third-party maintenance (minor) releases or feature releases that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or feature releases. In some cases, these minor releases or feature releases affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or feature releases. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or feature releases are compatible with the Commvault software.
Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.
Last modified: 9/3/2020 7:36:00 PM