#1 Global Leader in Data Protection & Ransomware Recovery

How to Manually Update Suspicious File List

KB ID: 4514
Product: Veeam Backup & Replication | 12.1
Published: 2023-12-05
Last Modified: 2024-01-19
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Intended Audience

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.

Purpose

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.

Solution

  1. Download the latest SuspiciousFiles.xml using a machine with internet access.
  2. Transfer the file to the Veeam Backup Server.
  3. Replace the existing SuspiciousFiles.xml found in:
    C:\Program Files\Veeam\Backup and Replication\Backup\
    
  4. Restart the Veeam Data Analyzer Service.

 

Download SuspiciousFiles.xml

https://vbr.butler.veeam.com/malware-extensions-list

Do Not Modify SuspiciousFiles.xml
The SuspiciousFiles.xml is signed; any modification to the file will invalidate it.

More Information

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
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.