- Veeam Support Knowledge Base
- File to tape job significantly slows down due to garbage collection operations
File to tape job significantly slows down due to garbage collection operations
| KB ID: | 3083 |
| Product: | Veeam Backup & Replication | 9.5 | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1 |
| Published: | 2020-01-09 |
| Last Modified: | 2021-04-29 |
Get weekly article updates
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
Oops! Something went wrong.
Please, try again later.
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:
For an XML example, see the following Microsoft article.
https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/gcserver-element
Please 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.
- 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-element
Please 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.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
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.
