OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 383 days ago.
This article is intended for environments where the Veeam Backup Server does not have direct access to the internet to be able to update the known malware extensions list (SuspiciousFiles.xml) automatically. This article documents the procedure for updating said file by manually downloading it on a machine with internet access and placing it on the Veeam Backup Server.
Download the latest SuspiciousFiles.xml using a machine with internet access. Transfer the file to the Veeam Backup Server. Replace the existing SuspiciousFiles.xml found in: C:\Program Files\Veeam\Backup and Replication\Backup\ For the embedded Veeam Backup & Replication deployment included with Veeam Recovery Orchestrator, the path is: C:\Program Files\Veeam\Orchestrator\Backup\ Restart the Veeam Data Analyzer Service.
SuspiciousFiles.xml XML Signature Check Because the SuspiciousFiles.xml contains a signature, if the file is altered or corrupted (e.g., bad download), the Veeam Data Analyzer Service will refuse to load it. You can verify if the Veeam Data Analyzer Service has accepted the file by checking the latest entries in: C:\ProgramData\Veeam\Backup\Svc.VeeamDataAnalyzer.log An altered or corrupted SuspiciousFiles.xml will cause the following errors to appear in the log: [CLocalFileSignaturesStorage] XML signature check result: Signed by Veeam=True, Valid chain=True, Correct file signature=False A successfully validated SuspiciousFiles.xml will result in: [CLocalFileSignaturesStorage] XML signature check result: Signed by Veeam=True, Valid chain=True, Correct file signature=True
