Skip to main content
Question

Does SP42 ThreatScan require configuration from Threat Analysis?

  • March 6, 2026
  • 1 reply
  • 13 views

Hello Commvault Community, 
 

The ThreatScan mechanism has changed between SP40 and SP42.
 

The old mechanism from SP40 is currently deprecated and renamed as Threat Analysis. Articles describing sizing, settings, and descriptions of Eicard test files are still available but only for Threat Analysis, not for ThreatScan:

Commvault Threat Scan Requirements
https://documentation.commvault.com/11.42/software/commvault_threat_scan_requirements_01.html

Software, Hardware, Requirements for Restore Worker VMs
https://documentation.commvault.com/11.42/software/software_hardware_and_other_requirements_for_restore_worker_vms_02.html


Troubleshooting - Threat Analysis for Virtual Server Agent
https://documentation.commvault.com/11.42/software/troubleshooting_threat_analysis_for_virtual_server_agent.html#need-to-test-threat-analysis-for-virtual-server-agent-and-file-system

 

> Does a new ThreatScan configuration on a Linux ThreatScan server require editing the lvm.conf file?
 

> Does ThreatScan SP42 address the other issues discussed in the ThreatAnalysis documentation for this configuration to function correctly?

Thanks in advance!

Kind Regards,
Kamil

1 reply

Forum|alt.badge.img+15
  • Vaulter
  • March 7, 2026

Hi ​@Kamil ,

Editing the /etc/lvm/lvm.conf file is not a standard requirement for all new ThreatScan configurations on a Linux ThreatScan server. However, you may need to update the lvm.conf file in specific scenarios, such as:

  • If your ThreatScan operations involve mounting or scanning Logical Volumes (LVM), and the default LVM filter or configuration does not recognize the relevant devices (e.g., NVMe, SATA SSDs, or other storage types).
  • If you encounter issues where logical volumes are not being detected, activated, or reported correctly in Commvault (e.g., volumes appear offline in Command Center or are not available for scan/restore).