VeeamDCS.exe Huge memory consumption

[sabicao]

Hi.

Today my Backup Copy jobs started failing with weird messagens that led me to believe I had no memory available at my Veeam Backup Server (which also hosts Veeam ONE).

It is a ProLiant server, 12 cores, 64GB RAM, I found it at 98% RAM consumed, with VeeamDCS.exe consuming a whopping 52GB.

Tried to restart the service, didn't respond to it, rebooted the server, VeeamDCS now shows 374MB RAM usage.

The box was provisioned 31 days ago, any comments at why this happened? Should I expect such a behavior sporadically in the future?

Cheers,
Fernando

[RomanK]

Hello Fernando,

The root cause of memory leaks could be anything and it is hard to say why this happened.
It would be better to open a support case, collect all the additional details, and investigate it accordingly.

Please share the support case # in this thread as well.

Thanks

[jorgedlcruz]

Hello Fernando,
As Roman mentioned, a support ticket always helps us to track the issues, and see if any hotfix is required.

One quick question, as it seems the server was deployed recently, what version of Veeam ONE are you using? Latest one?

Thank you, looking forward for that support ticket id

[sabicao]

Yes, latest version.

[chris.childerhose]

We have noticed this, too even on VONE v12 with the latest patch and a hotfix. Going to watch this thread.

[jorgedlcruz]

Hello Chris,
You followed the procedures support mentioned and still the memory consumption is high? Do you have any support ticket, please?

Thank you

[chris.childerhose]

Hi Jorge,

Yes we have a case open - Case #07002301

Thanks,
Chris

[jorgedlcruz]

Appreciated Chris, we are on top of this, we will let you know soon.

Appreciated it

[RomanK]

Hello Chris,

Thanks for the case #. I've pinged support management and RnD team as well. The case has a long troubleshooting history but I'm confident our support engineers will find the cause of this issue. Also feel free to escalate the ticket (talk to manager button within the support portal), if you are not satisfied with the quality or time of response.

Meanwhile, I would like to underline, that the root cause for the leaks could differ from case to case. For example, some of them are already fixed in 12.0.1.2591 P20230314. It is always better to open a dedicated support case, if the issue is already known support should detect and provide a solution pretty fast.

Thanks

[chris.childerhose]

Thanks, guys. I will just patiently wait for a response and solution, hopefully.

[mats.jansson]

Hi Chris
We have the same mem problem, our problem started after we added our 365 server to Veeam One.
We will open a case after our vacations.

[chris.childerhose]

All cases will help us get a fix so definitely submit one.

[jorgedlcruz]

Hello Mats,
Yes please, as Chris said, please open a ticket, share it with us if you like please.

I am aware of a few workarounds for some specific scenarios but support will confirm and send everything.

Thank you

[chris.childerhose]

The latest update today is that RnD is still working on this one to determine the issue; still in a holding pattern until further testing/changes are required.

[jorgedlcruz]

Hello Chris,
I can see new logs bundle have been uploaded, thank you so much for the continue support on this topic. As soon as any information, or conclusion appears, you will be the first receiving it through the case.

Thank you.

[ricardo.simoes]

Hi everybody
We have the same mem problem, our problem started after we added our 365 server to Veeam One.
After restarting the service it goes back to normal but then it grows again until it takes up a lot of server memory resources.
So far I haven't created a ticket because I've been regularly monitoring the server's memory and I've been following this thread.

Let's wait for news

Best regards

[RomanK]

Hello ricardo,

our problem started after we added our 365 server to Veeam One.

I would strongly recommend opening a dedicated support case. As far as I know, there were no support cases with the aforementioned root cause and the support cases above are not about VB365 infrastructure.

Thanks

[ricardo.simoes]

Hi, Roman,

Thanks. We only noticed that this started happening in version 12 and when we added the VBO365 server to Veeam ONE. We got that "feeling" but we're not completely sure. Therefore, I will create a ticket with support.

[chris.childerhose]

I look forward to hearing about VB365 and see if that is part of the problem. We are still waiting on our case for this issue and RnD to get back.

[RomanK]

Hi all,

@ricardo.simoes please do not forget to share the case ID in this thread.

Thanks in advance.

[ricardo.simoes]

Hi,

Case # 07007212

Best regards

[RomanK]

Hello ricardo,

Thanks for the case #
I already notified our support team about this thread and parallel troubleshooting in all other cases.

Thanks