Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4362

Antivirus Exclusions for Veeam Agent for Microsoft Windows

$
0
0

Antivirus Exclusions for Veeam Agent for Microsoft Windows

KB ID: 2034
Product: Veeam Agent for Microsoft Windows | 4.0 | 5.0 | 6.0 | 6.1
Published: 2015-05-19
Last Modified: 2024-07-03

Purpose

This article documents antivirus exclusions that may be created to reduce the impact that antivirus software has on the functionality of Veeam Agent for Microsoft Windows. These antivirus exclusions may be applied to the Windows built-in antivirus or third-party antivirus software.

Note: Antivirus will not always cause Veeam Agent for Microsoft Windows functions to fail; antivirus software may also negatively impact performance.

Limitations and Considerations
  • Given the complex nature of antivirus software, it may be necessary to add additional exclusions. Users are encouraged to review their antivirus logs or history to determine if more objects must be excluded.
  • Although these exclusions are primarily intended for antivirus software, they may also need to be applied to other security software. This includes any software that performs file scanning or access control, which could potentially block or interfere with Veeam-related processes.
  • All folder paths listed in this article include recursively all files and subfolders.
  • For folder paths containing Veeam executables (e.g., C:\Program Files\), some security software may require explicit process exclusions to be configured for the executables within those folders rather than a folder-wide process exclusion.

Antivirus Exclusions

On machine where Veeam Agent for Microsoft Windows is installed:

Folder Exclusions
  • %programfiles%\Veeam\
  • %commonprogramfiles%\Veeam\
  • %programdata%\Veeam\
  • For Veeam Agent for Microsoft Windows 5 and older:
    • %windir%\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\VeeamEndPoint\
  • For Veeam Agent for Microsoft Windows 6 and newer:
    • %programdata%\Veeam\EndpointData\
  • %windir%\VeeamLogShipper\
    This folder will only be used on SQL Servers when SQL Server Transaction Log Backup is enabled.
  • %windir%\Veeam\Backup\
  • *Either a folder level exclusion for any folders containing backup files, or a file extension exclusion of the Repository Extensions listed on KB1999
     
File Exclusions
  • For Veeam Agent for Microsoft Windows 5 and older:
    • %windir%\System32\config\systemprofile\VeeamBackup.mdf
    • %windir%\System32\config\systemprofile\VeeamBackup.ldf
  • For Veeam Agent for Microsoft Windows 6 and newer
    • %programdata%\Veeam\EndpointData\VeeamBackup.db
  • *Either a folder level exclusion for any folders containing backup files, or a file extension exclusion of the Repository Extensions listed on KB1999
     
Process-Specific Exclusions
  • C:\Program Files\Veeam\Endpoint Backup\Veeam.EndPoint.FLR.exe
  • C:\Program Files\Veeam\Endpoint Backup\Veeam.EndPoint.Manager.exe
  • C:\Program Files\Veeam\Endpoint Backup\Veeam.EndPoint.Recovery.exe
  • C:\Program Files\Veeam\Endpoint Backup\Veeam.EndPoint.Service.exe
  • C:\Program Files\Veeam\Endpoint Backup\Veeam.EndPoint.Tray.exe
  • C:\Program Files\Veeam\Endpoint Backup\x64\VeeamAgent.exe
  • C:\Program Files\Veeam\Endpoint Backup\x86\VeeamAgent.exe
Windows 11 22H2 and Bitdefender Antivirus
Veeam Support has observed a distinct increase in cases regarding Veeam Agent for Microsoft Windows backup jobs failing during the "Creating VSS snapshot" stage after upgrading to Windows 11 22H2. The majority of these cases involve the presence of Bitdefender Antivirus and are resolved by configuring the above Process-Specific Exclusions.
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.

Viewing all articles
Browse latest Browse all 4362

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>