Commvault Threat Scan Requirements

Note

• Threat Scan for FreeBSD VMs are not supported.

• When Threat Scan plans are configured to use Commvault-managed storage (default configuration), the threat scanning infrastructure is fully provisioned and operated by Commvault; no additional infrastructure or deployment steps are required. If you configure a plan to scan customer-managed storage (cloud or on-premises), you must deploy new access nodes or reuse existing backup access nodes with the required components, according to the software deployment requirements shown below or reuse existing backup access nodes.

• Since the Data Cube process can overload the Threat Scan server and impact Threat Analysis job performance, follow these guidelines:

  • Do not assign the Index Server role to Threat Scan nodes.

  • Ensure the Index Store package is not installed on Threat Scan nodes.

Note

Server requirements apply only to software-managed deployments. SaaS deployments using Commvault-managed storage do not require a Threat Scan server.

Note

• File indexing and Threat Analysis processes do not recognize when backup operations are running on proxies. Because these processes are resource-intensive, they can negatively impact backup performance and delay job completion. To avoid performance issues, do not overlap proxies used for Threat Analysis jobs with those used for backup jobs. The access nodes defined at the Threat Analysis plan level should be different from the proxies configured for backups (defined at the hypervisor or VM group level).

• To scale for larger configurations, you can add additional nodes, but you must ensure that the nodes are running the same OS. For more information, see Adding a Node to the Index Server.

• The maximum size of file that can be analyzed is 50 MB.