Operational Defect Database
BugZero found this defect 1593 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb3083
File to tape job significantly slows down due to garbage collection operations
Last update date:
4/29/2021
Affected products:
Veeam Backup & Replication
Affected releases:
11
Fixed releases:
No fixed releases provided.
Description:
Challenge
A file to tape job significantly slows down after some time of processing. The source disks and the Veeam database are under a low load, CPU is not overloaded either. Available RAM on the Veeam server is around 10% or lower.
Cause
When available RAM on the Veeam server reaches a certain threshold (by default, 10% of total RAM installed), .NET Framework activates frequent garbage collection operations. This leads to the freezing of Veeam Management processes.
Solution
Do the following to enable the Server Mode for garbage collection: Make sure no Veeam job is running. Disable Veeam services on the Veeam Backup & Replication machine. Navigate to the product installation folder. The default installation folder is C:\Program Files\Veeam\Backup and Replication\. Open the Backup subfolder. Back up the Veeam.Backup.Manager.exe.config file to avoid file corruption. Open the Veeam.Backup.Manager.exe.config file for editing. Find the <runtime> tag, create a new blank line after it and add the following element to the new empty line: <gcServer enabled="true"/> For an XML example, see the following Microsoft article.https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/gcserver-elementPlease note that RAM consumption can increase significantly if multiple jobs run concurrently. Enabling garbage collection at the server requires additional 1-2 GB RAM for every Veeam job.
