VEB sql memory usage >35GB

[Without]

I've been noticing on a number of systems that VEB's sql instance is using immense amounts of ram. Today it was at 35.4GB, which sadly isn't the highest it's been.

Currently running 1.5.0.306 on Windows 7.

[Gostev]

[Mike Resseler]

Hi,

Are you running VEB in background mode or did you allow it to use as much resources as it can? (In Control Panel, the throttling activities check box)

Mike

[Without]

"Throttle backup activity when system is busy" is checked.

[Mike Resseler]

Hmmm,

Can you log a support case? I cannot recall a single instance where I worked on that used that amount of memory from the system. Please log the support case ID here and the follow-up after working with support. As you might know, support with the free version is available, but we don't deliver an SLA on it. We work on a best effort basis, but we do come back to you

Thanks
Mike

[Gostev]

I checked with QC and they said the likely cause is a misbehaving antivirus. They too advised to open a support case.

[Without]

I had tried to open a support case but was unable to do so due to site just sending me in circles instead.

[Mike Resseler]

PM me your email address and I will ask support to contact you directly so both items can be resolved at once.

I assume you tried to create the support case through the VEB UI?

[Without]

It just tells me that "email address is not registered with Veeam" though it is and I can use the same email address to login to the support portal that sent me in circles. PM'ing now.

[Without]

It allowed me to submit through the VEB UI tonight. If you did anything on the backend to allow that, it seems to have worked.

Veeam Support - Case # 02008325 - VEB sql memory usage exceeded 35GB

[Mike Resseler]

Hi,

Sometimes it takes some time before the synchronization has ran between the registration and actually being able to submit a support case. But I am glad it is working and that you have a support case now. Please continue this thread when you have more information

Thanks
Mike

PS: Ignore that PM that I just send you. I already cancelled that email to support

[Dima P.]

Hi Without,

Thanks for sharing the case ID. We will review your logs with QA team.

[Without]

Since you mentioned AV might be a cause, I tried with it disabled. Difference was >1GB on VEB service restart and >24GB after a few hours.

[Dima P.]

Thank you. What AV software are you using? Is it possible for you to test memory consumption with antivirus being uninstalled?

[Without]

Thank you. What AV software are you using?

ESET NOD32 9.0.408.0

Is it possible for you to test memory consumption with antivirus being uninstalled?

Not easily.

[Without]

Support asked me to try setting exceptions to AV per https://www.veeam.com/kb2034. On VEB service restart, it was using just over 1GB but was slowly climbing. 8 hours later it its settled back down to still just over 1GB. This is better but still very high, and should note that no backup has run yet since making these changes. I've forced a backup cycle and will check it again later.

[Without]

Update, no change long term. Memory usage up to 16GB after another 8 hours and a backup.

[Gostev]

Can you please temporarily uninstall the antivirus completely, and reboot the server to fully remove any low level drivers it may have installed? There are currently no known issues with memory consumption except those caused by certain misbehaving 3rd antiviruses...

[Without]

I don't know what happened to to my last post, but I've uninstalled ESET and I'm monitoring the sql service memory usage.

[Dima P.]

Thanks. Let us know how it goes on your side.

P.S. Could you please share the exact verion of your ESET antivirus?

[Without]

Thanks. Let us know how it goes on your side.

It's been hovering around 330MB for a day now. It might be behaving now, but this is not a workable solution and I'm reinstalling the AV now.

P.S. Could you please share the exact verion of your ESET antivirus?

ESET NOD32 9.0.408.0

[Without]

After installing ESET NOD32 10.0.369.0 and the scheduled backup started, VEB's sql service jumped to 19GB.

[Dima P.]

My bad, thanks again. Can you please upload new portion of logs from the last job run to support side?

[Without]

My bad, thanks again. Can you please upload new portion of logs from the last job run to support side?

Done.

[Without]

Update, support had me apply a config change to VEB's sql server. Since then memory usage is holding at between 3.5GB and 4.5GB. While still quite bad, this is considerably better than it was.