This article is intended for Veeam Backup & Replication deployments where the software cannot access the internet to automatically update the SuspiciousFiles.xml file used by the Veeam Data Analyzer Service.
In environments where the Veeam Backup Server can access the internet, the Veeam Data Analyzer Service will check for an updated SuspiciousFiles.xml file every 1440 minutes (1 day). Furthermore, if the Veeam Backup Server has access to the internet, it can be forced to check for an update by restarting the service.
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\
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
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case