Start with a system that can handle your expected 6-month workload.
With this configuration, you can protect 50 TB of front-end client data without requiring additional resources. To support a 100 TB solution, deploy a second MediaAgent with the same specifications.
Note
Commvault defines a front-end TB (FETB) as a TB of written client data, prior to Commvault compression or deduplication. The term "front-end" refers to the location of the data when measured, because FETB is measured at the client to be protected, before Commvault handling.
For custom sizing, contact your local Commvault account representative.
Trial Server Requirements
Review the following requirements for large environments:
-
Microsoft Windows Server 2019 (all editions) or 2016 (all editions)
-
12 CPU/vCPU cores
-
64 GB RAM
-
300 GB disk space for CommServe SQL Server database (E:\) and logs (F:\)
This server can handle up to 2500 physical servers, 5000 virtual machines, and 10,000 laptops.
MediaAgent Requirements
You need at least one MediaAgent to perform backup and restore operations from backup media, such as disk, cloud, or tape libraries.
To provide resiliency when one MediaAgent is unavailable, deploy a second MediaAgent. For more information, see Hardware Specifications for Deduplication Mode.
Install the MediaAgent on a separate computer with the following specifications:
-
12 CPU/vCPU cores
-
64 GB RAM
-
400 GB disk space for Commvault software (E:\)
-
1.2 TB disk space for deduplication database (DDB) (F:\)
-
1 TB disk space for index cache (G:\)
Note
Review the I/O requirements for the deduplication database and index cache drives in Hardware Specifications. These I/O requirements are mandatory and directly impact the performance of your backup solution.