Data Collector Service spikes CPU on SQL server

[withanh]

I'm just getting around to reinstalling/reconfiguring the Veeam Monitor. After installing, I noticed that the sqlservr.exe service on the remote SQL server is spiking up to 100%. I have positively determined it is the Veeam Data Collector Services. When I start the service on <serv1> the sqlservr.exe service on <sql01> spikes up, when I stop the Veeam DCS, the spike drops. I let it run for a bit thinking it was just sorting things out and doing an initial collection, but after about 15 minutes I started getting worried that it wasn't going to stop, so I killed the Veeam DCS.

Not sure if this matters or not, but there is also Veeam Business View and Veeam Reporter installed on the same (<serv1>) box.

Thanks!

Darhl

[Vitaliy S.]

Hello Darhl,

Having Reporter and BV database on the same server cannot cause such misbehavior. I wonder what information is in Veeam Monitor log files, can you drop an email to our support team with the reference to this topic?

Thanks.

[withanh]

Will do Vitaliy, thanks!

*edit* Which logs should I send in?

d

[withanh]

Case # 5145911

[Ubuntop]

Was there ever a resolution to this? I have a similar issue.
sqlserver is 100% which can be tracked to the following query.
IF EXISTS( SELECT * FROM VwEvent WHERE ABS( DATEDIFF( ms, time, @i_Time) ) < 5 AND @i_HostId = host_id AND internal_id = @i_InternalId )

As soon as I stop the collector service, CPU goes back to averaging 2%.

[Vitaliy S.]

Based on Darhl's support case, it appears that our latest hot-fix and database recreation did the trick, so please contact our support team for assistance wit this issue directly.

[withanh]

I apologize for not posting that result, but Vitaliy is correct.

h

[CamiloTN]

I have the current Veeam one 11 version and I have the same Issue, does the Hot-fix work with the new Veeam One 11 too?

[wishr]

Hi Oscar,

This is a pretty old thread and I'm sure that issue was fixed quite a while ago, so please open an independent support case for investigation. In general, we merge most of the private fixes to the closest new product version.

Thanks