Hi all,
I am trying the VBR 12.3.2 and I see high memory consumption (>1GB) on the Windows 2025 Server.
The process consuming the memory is Veeam.RestApiService. Please is this normal ?
I have enabled just 2 concurrent tasks and have the feeling, that the memory demand is increasing over the time even when no jobs are running...
+21That seems to be normal for this process and for some reason I have noticed on Win2025 it gets higher than Win2022. I have not fully moved my homelab to 2025 yet as there are some weird things that happen in that OS and have stayed on 2022 for now.
+12Hi
Most likely you are affected by the same issue as discussed in our RnD forum. It will be fixed in the upcoming version.
To confirm and resolve issue in your environment, please contact our customer team. They can provide you with the fully supported RTM build if required.
Alternatively, you could wait a few weeks and update to version 13.0.1 when it becomes GA to see if the problem persists.
Best,
Fabian
+21Hi
Most likely you are affected by the same issue as discussed in our RnD forum. The issue will be solved with the upcoming v13.0.1.
To confirm and resolve issue, please contact our customer team. They can provide you with the fully supported RTM build if required.
Alternatively, you could wait a few weeks and update to version 13.0.1 when it becomes GA to see if the problem persists.
Best,
Fabian
Thanks for sharing that RnD link Fabian. Did not see that one out there and looking forward to it being fixed in 13.0.1. 😎
+4Hi
This behavior is expected in VBR 12.3.x. The Veeam.RestApiService typically uses around 1–1.2 GB of RAM, even when idle.
It loads API components and keeps them ready for requests, which explains the baseline memory usage.
However, if you notice continuous growth beyond that baseline, it may be related to a known issue in 12.3.2 on Windows Server 2025. I hope so the veeam has acknowledged this and plans a fix in v13.0.1.
What you can do:
Reference: Veeam R\&D Forum discussion. [forums.veeam.com]
+21I have upgraded one server to RTM and once I get the API service running will update on consumption. Support ticket open for this. 😫
Hi all,
thanks for the comments.
I will wait for the new free release, but I must say it is (probably) not related to Win 2025, I had the same bahaviour with Win 2022.. The VBS is running in VM on top of Proxmox and after few days it consumes all the memory given from the hypervisor, regardless, how much is assigned to it (>50G). I did just picked up the RESTAPI as an example, because it had the highest memory demand in the VM, where PBS was running.
+21Happy to report that in the RTM release the API service does not use anything near 1GB+ of RAM. My server I just upgraded is running at about 100K for the API service. So a big improvement over 12.3.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
