Verify that the machine you want to use as the Commvault Cloud archive backup gateway meets the requirements.
Operating System
-
Microsoft Windows Server 2022 Editions
-
Microsoft Windows Server 2019 Editions
-
Microsoft Windows Server 2016 Editions
-
Red Hat Enterprise Linux/CentOS 9.x
-
Red Hat Enterprise Linux/CentOS 8.x
-
Red Hat Enterprise Linux/CentOS 7.x
-
SuSE Linux 15
-
SuSE Linux 12
-
SuSE Linux 11
-
Rocky Linux 8.x
Hardware
You can install the Commvault Cloud archive backup gateway on a virtual machine or a physical server in an on-premises data center. To reduce network latencies and performance degradation, place the Commvault Cloud archive backup gateway adjacent to the data source.
If you add a second copy of data where the primary copy is in cloud, to limit data egress charges, set up another backup gateway in cloud, adjacent to the data.
The following hardware sizing guidelines are for the initial deployment of the Commvault Cloud archive backup gateway.
Component |
Size guide |
Example size |
---|---|---|
Back-end data size (BET) |
Can be dynamically scaled |
600 TB |
CPU |
Can be scaled up/down as required |
12 vCPUs |
RAM |
Can be scaled up/down as required |
64 GB |
Operating system disk (SSD recommended) |
50 GB |
50 GB |
SSD data disk This is the disk where you will install the backup gateway software. The data disk is used for program files, indexing, and logs. |
Can be dynamically scaled |
1.2 TB SSD Class Disk Increase the size of this disk as you reach usage thresholds. |
SSD DDB disk This disk us used for deduplication. |
Can be dynamically scaled Generally, 2 GB of DDB space is required for every 1 TB BET. |
1.2 TB SSD Class Disk Increase the size of this disk as you reach usage thresholds. For Linux, the DDB volume must be configured by using the Logical Volume Management (LVM) package. |
Network bandwidth |
1 Gbps (minimum) |
1 Gbps (minimum) |
Note
-
The required back-end size depends on how well the data can be deduplicated and on retention.
-
CPU and RAM for machines can be scaled up/down as required. Archiving often requires more resources for the first jobs and can be scaled down after the first jobs.
-
SSD data disk sizes and SSD DDB disk sizes can be increased as you reach usage thresholds.
Network
The on-premises Commvault Cloud archive backup gateway must be able to connect to the Commvault Cloud service and must be able to access the servers that need to be archived.
-
TCP 443 outbound must be open to access the following:
-
Commvault Cloud backup service (*.metallic.io)
-
Azure services (*.cloudapp.azure.com)
-
Your storage location e.g.
-
Azure (*.blob.core.windows.net)
-
AWS (*.s3.amazonaws.com)
-
-
-
CIFS or NFS shares must be accessible from the Commvault Cloud archive backup gateway.
-
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)
-