Veeam8 high CPU usage on Veeam manager server?

[christiankelly]

Has anyone seen an issue with the Veeam management server high CPU usage? After upgrading to v8 every job that runs has a process "Veeam.Backup.Manager.exe" which takes about 18-20% CPU. Needless to say after about 5 jobs my 4 core server is maxed out. To be clear this is a "management server" only, it's not running any proxies or repositories it's just kicking the jobs off etc... With v7 on the same server I had 8+ jobs running with hardly any CPU usage and now 4 or 5 maxes it out. I opened a case but support didn't really know what was going on.

[AlainRussell]

We've noticed our backups are slower on v8 (from 55-60 mins to 90+ mins now), looking at our Veeam Monitor we can see CPU started to get a lot higher the day we upgraded which I assume is related. Is this expected behaviour, or is anyone else seeing this?

[AlainRussell]

Sorry - forgot to load image https://www.dropbox.com/s/471my105cpyhwvm/veeam-v8.png

[stefanbrun]

See Topic in Vsphere Forum: http://forums.veeam.com/vmware-vsphere- ... 24031.html

[Vitaliy S.]

Has anyone seen an issue with the Veeam management server high CPU usage? After upgrading to v8 every job that runs has a process "Veeam.Backup.Manager.exe" which takes about 18-20% CPU. Needless to say after about 5 jobs my 4 core server is maxed out. To be clear this is a "management server" only, it's not running any proxies or repositories it's just kicking the jobs off etc... With v7 on the same server I had 8+ jobs running with hardly any CPU usage and now 4 or 5 maxes it out. I opened a case but support didn't really know what was going on.

Hi Christian,

What is your case ID so we could take a look at this situation with the QC team?

Thanks!

[foggy]

We've noticed our backups are slower on v8 (from 55-60 mins to 90+ mins now), looking at our Veeam Monitor we can see CPU started to get a lot higher the day we upgraded which I assume is related. Is this expected behaviour, or is anyone else seeing this?

Alain, do you mean Veeam backup server CPU? Does your backups server also act as a proxy server?

[christiankelly]

What is your case ID so we could take a look at this situation with the QC team?

00667400

[AlainRussell]

Alain, do you mean Veeam backup server CPU? Does your backups server also act as a proxy server?

Yes - higher CPU on the Veeam server, and yes - it also acts as a Proxy.

[veremin]

Hi, Alain,

I have merged your post into existing discussion that talks about similar issue. Can I ask you to open a ticket with our support team and provide them with required logs? Having those at hand should help us to pinpoint a problem.

Thanks.

[Gostev]

Through troubleshooting the issue in Christian's environment (thank you!), we have found extra CPU load to be caused by disabled parallel processing. We highly recommend that parallel processing is enabled (there is usually no reason not to have it enabled), and this is the default setting starting B&R v7 anyway. That said, we are working on a hot fix for those who have a legitimate scenario that requires parallel processing to be disabled. Thanks!

[AlainRussell]

I have parallel processing enabled - support opened a case for me (00679061) and I've loaded log files for the last 2 weeks from our Backup server.

[christiankelly]

I can confirm that with the patch I received that the CPU is back down to under 10% with 6 jobs running!

Thanks,

[Gostev]

I have parallel processing enabled - support opened a case for me (00679061) and I've loaded log files for the last 2 weeks from our Backup server.

Alain, what are the top CPU consuming processes in your case (as per Task Manager)?

[AlainRussell]

During current backup job varies between:

VeeamAgent
Veeam.Backup.Service
SQL Server Windows NT 64 Bit
Veeam.Backup.Manager
Service Host: Local System (15)

Thanks.

[Gostev]

Well, instant CPU usage does not really show much. You should add and look at "CPU time" column (showing total CPU time) on Details tab.
1. Reboot the server.
2. Start some large job immediately after reboot.
3. Collect CPU times right after the job finishes executing.