Loading...
Loading...
This article documents how to exclude specific machines from Proactive Malware Scans (the "Perform signature-based scan when malware event appears" option). Exclusions are useful when backed-up machines have disks encrypted with BitLocker or other encryption methods, such as crypto_LUKS, VeraCrypt, etc. Disks encrypted using those methods cannot be mounted by the Mount Server, causing the automatic proactive scan to display the following warning: The proactive malware scan encountered mount errors. Please review the corresponding Scan Backup session.
Before configuring a Proactive Malware Scan Exclusion, first determine if the issue is caused by an incompatible disk configuration (e.g., disk encryption). The warning shown may also be due to an invalid configuration of the mount server for the mounted restore point. If the mount error cannot be resolved due to encrypted disks, the only remaining solution is to exclude the VMs with encrypted disks. To exclude a VM, create or modify the following custom setting: For Veeam Backup & Replication on Windows Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\Value Name: MalwareAutoScanExclusionsValue Type: Multi String Value (REG_MULTI_SZ)Value Data: (add one VM name per line) Each line will be tested against the VM Name, and if it matches exactly (case insensitive), it will be skipped from Proactive investigation in the future. For Veeam Software Appliance (Veeam Backup & Replication on Linux) Configuration file: /etc/veeam/veeam_backup_and_replication.confSection: [root]Value Name: MalwareAutoScanExclusions Each line will be tested against the VM Name, and if it matches exactly (case insensitive), it will be skipped from Proactive investigation in the future. For more information on applying custom settings on the Veeam Storage Appliance, please review: KB4779: Applying Custom Settings to Veeam Software Appliance
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.