Loading...
Loading...
This article is intended for environments where the Windows-based Veeam Backup Server does not have direct internet access to automatically update the known malware extensions list (SuspiciousFiles.xml). This article documents the procedure for updating the file by manually downloading it to a machine with internet access and then placing it on the Veeam Backup Server.
This procedure is only possible for Windows-based Veeam Backup & Replication deployments.
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
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.