Verify that your environment meets the system requirements for an on-premises Commvault backup gateway.
Operating System
The Commvault backup gateway supports installation on both Microsoft Windows and multiple Linux distributions. Ensure that your operating system is running a supported version as listed below.
Supported Microsoft Windows Server Editions
-
Microsoft Windows Server 2025 Standard
-
Microsoft Windows Server 2025 Datacenter Editions
-
Microsoft Windows Server 2022 Core Editions
-
Microsoft Windows Server 2022 Standard Editions
-
Microsoft Windows Server 2022 Datacenter Editions
-
Microsoft Windows Server 2019 Editions
-
Microsoft Windows Server 2019 Core Editions
-
Microsoft Windows Server 2016 Editions
For more information, see Considerations for Microsoft Windows Server 2016.
-
Microsoft Windows Server 2012 R2 Editions
For more information, see Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8.x.
-
Microsoft Windows Server 2012 Editions
For more information, see Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8.x.
-
Microsoft Windows 11 Pro
Tape libraries/drives are not supported.
-
Microsoft Windows Client 10 Editions
Tape libraries/drives are not supported.
*Tape is not supported because the operating system is not Long Term Supportable (LTS).
Supported Linux Distributions
-
AlmaLinux 9.x
-
AlmaLinux 8.x
-
Amazon Linux 2023 AMI (all major/minor versions)
-
Amazon Linux 2 AMI (HVM) - Kernel 5.10, SSD Volume Type
-
Debian 12.x
-
OpenSuSE 13.2
-
Oracle Linux 9.x
-
Oracle Linux 8.x
-
Oracle Linux 7.x
-
Red Hat Enterprise Linux 10.x
-
Red Hat Enterprise Linux 9.x
-
Red Hat Enterprise Linux 8.x
-
CentOS 8.x Linux
-
Red Hat Enterprise Linux/CentOS 7.x
-
Rocky Linux 10.x
-
Rocky Linux 9.x
-
Rocky Linux 8.x
-
SuSE Linux Enterprise Server 15 SP5
-
SuSE Linux 12 (Initial Release/SP1/SP2/SP3/SP4/SP5)
-
SuSE Linux Enterprise Server 15 SP6 & SP7
-
SuSE Linux Enterprise Server 15 SP3
-
SuSE Linux Enterprise Server 15
-
Ubuntu 24.04 LTS
-
Ubuntu 22.04 LTS
-
Ubuntu 20.04 LTS
-
Ubuntu 19.04
-
Ubuntu 18.04 LTS
-
Ubuntu 16.04 LTS
-
Ubuntu 14.04 LTS
Hardware
You can install the Commvault backup gateway on a virtual machine or a physical server in an on-premises datacenter. To reduce network latencies and performance degradation, place the Commvault backup gateway adjacent to the data source.
The following hardware sizing guidelines are for the initial deployment of the Commvault backup gateway.
Note
-
If a Linux backup gateway is used to protect your environment, then select the size of the environment during the VMware backup gateway deployment wizard.
-
For environments larger than 50 TB of data, see the KB article Commvault Cloud Backup Gateway Sizing Guidelines for On-Premises Environments for guidelines.
-
For cloud backup gateways, see the following KB articles for guidelines:
|
Component |
Size |
|---|---|
|
Back-end storage size (BET)1 |
Up to 50 TB Note For environments larger than 50 TB of data, see the knowledgebase article Commvault Cloud Backup Gateway Sizing Guidelines for On-Premises Environments for guidelines. |
|
CPU |
2 vCPUs |
|
RAM |
16 GB |
|
Operating system disk (SSD recommended) |
50 GB |
|
Dedicated SSD data disk This is the disk where you will install the backup gateway software. The data disk is used for program files, deduplication, indexing, and logs. |
200 GB (minimum) Increase the size of this disk as you reach usage thresholds. |
|
Network bandwidth |
1 Gbps (minimum) |
Footnotes:
-
Back-end storage size (BET) requirements approximately range from 1.0–1.6 times of the front-end data size (FET). This factor will vary directly in proportion with the amount of retention required and the amount of daily change rate for the front-end data. For example, if the data is retained for lower number of days, then it reduces the predicted amount of back-end storage requirement. Whereas, if the extended retention rules are applied to a larger portion of the managed data, then it can increase the back-end storage consumption. The FET estimate can be used in the storage policy design to help size the appropriate resources to support the use-case.
The following are examples of commonly used settings for the backup retention.
Example 1:
-
80% VM/File data
-
20% Database data
-
Daily change rate 2%
-
Compression rate 50%
-
Daily backups are retained for 30 days
Factoring in these parameters, the back-end storage size requirements can range from 1.0 - 1.2 times the front-end data size.
Example 2:
-
80% VM/File data
-
20% Database data
-
Daily change rate 2%
-
Compression rate 50%
-
Daily backups are retained for 30 days
-
8 weekly backups are retained for 1 year
-
9 monthly backups are retained for 1 year
-
1 yearly backup is retained
Factoring in these parameters, the back-end storage size requirements can range from 1.4 - 1.6 times the front-end data size.
-
-
Please contact your software vendor for assistance with more advanced design cases.
Network
The on-premises Commvault backup gateway must be able to connect to the Commvault backup service and must be able to access the servers that need to be backed up:
-
TCP 443 outbound must be open to access the following:
-
Commvault backup service (*.metallic.io)
-
Commvault storage (*.blob.core.windows.net)
-
Azure services (*.cloudapp.azure.com)
-
If applicable, your storage location in AWS (*.s3.amazonaws.com)
-
-
TCP 8400 and TCP 8403 must be open between the backup gateway and any on-prem data sources that you want to protect. Depending on the operation, either the client or the backup gateway can open a connection.
-
To back up a VMware environment running an on-prem or cloud application, such as, VMware Cloud on AWS (VMC), Azure VMware Solution (AVS), Oracle Cloud VMware solution, or Google Cloud VMware Solution, the backup gateway must be able to access the following:
-
vSphere vCenter server: Port for web service (default: 443) must be opened. If vCenter is configured to use non-default ports, the non-default ports must also be opened.
-
vSphere ESX server: Ports for web service (default: 443) and TCP/IP (default: 902) must be opened for the vStorage APIs for data protection.
The backup gateway can be a Windows physical machine or a VMware VM or a Linux OVA deployed machine. For more information, see Protect VMware vSphere VMs.
-
-
To back up Hyper-V virtual machines (VMs), the Commvault VM proxy must be able to access the backup gateway on the port for the web service (default: 443).
-
Tenant computers must be able to connect to the following URLs (all URLs support HTTPS and can be accessed on port 443):
-
cloud.commvault.com (download software to install, update, or upgrade client computers)
-
downloadcenter.commvault.com (download software to install, update, or upgrade client computers)
-
https://time.akamai.com (fetch Akamai server time to generate Akamai token)
-
*.mapbox.com (provide location of the client or laptop, and fetches data such as city name)
-
*.skyhookwireless.com (provide location of the client or laptop, and fetches data such as city name)
-