Comment configurer les exclusions antivirus pour empêcher l'interaction avec Veeam Backup & Replication

Third-Party Antivirus Exclusion References

• Microsoft: Recommended antivirus exclusions for Hyper-V hosts
  

Security Software on Linux

Due to the high variability in how each Security solution operates and may be configured, some Linux Administrators may find that no exclusions are needed. Yet others may find that their security policies may necessitate specific exclusions. With that in mind, we strongly encourage Linux administrators to review their security software's logging closely when issues occur and adjust rules/policies accordingly.

Veeam Support has observed that the most common issues occur when Antivirus has been configured to tightly secure the /tmp/ directory, which in turn causes conflicts with Veeam's use of the path /tmp/Veeam/ . For example,  a Veeam Agent for Linux backup job may display the error "POSIX: Failed to open file [/dev/veeamimage1]." This error can be misleading at first as the path shown in the error does not appear related to /tmp/Veeam/, but in fact,/dev/veeamimage is symlinked to /tmp/Veeam/{guid}/

Below is a preliminary list of folders and executables that Veeam Support has identified:

• /dev/veeamimage*
• /etc/veeam/*
• /opt/veeam/*
• /tmp/veeamagent*
• /tmp/veeam/*
• /tmp/veeam/{*}
• /usr/bin/veeamconfig
• /usr/sbin/veeam*
  Specific executables:
  • veeam
    
  • veeamagent
  • veeamjobman
  • veeammount
  • veeampsqlagent
  • veeamservice
  • veeamsupporttool
• /var/lib/veeam/*
• /var/log/veeam/*