Host-based backup of VMware vSphere VMs.
Post Reply
JWester
Service Provider
Posts: 63
Liked: 7 times
Joined: Apr 04, 2011 8:56 am
Full Name: Joern Westermann
Contact:

Proxy CPU usage

Post by JWester »

Hi,

currently we use one backup proxy (VM) for each vSphere cluster.
Each proxy has 8 vCPUs.
While tracking down a high cpu usage on this proxy I noticed that all 8 cpus are used equally even when only one backup job is running (checked through Windows task manager).
Is it really possible that one backup job is spread on 8 cpus? I would have expected only 1 or 2 cpus to be used.

Many thanks!
Joern
Vitaliy S.
VP, Product Management
Posts: 27377
Liked: 2800 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Proxy CPU usage

Post by Vitaliy S. »

Hi Joern,

Well... yes, why not? How many Veeam processes do you see running in the Task Manager?

Thanks!
JWester
Service Provider
Posts: 63
Liked: 7 times
Joined: Apr 04, 2011 8:56 am
Full Name: Joern Westermann
Contact:

Re: Proxy CPU usage

Post by JWester »

Hi Vitaliy,
Vitaliy S. wrote: Well... yes, why not? How many Veeam processes do you see running in the Task Manager?
4x veeamagent.exe - which is correct since the proxy is configured for 4 simultaneous backup tasks.

Running one backup only one process has a high cpu usage, e. g. 60%. But I see this cpu usage also as a 60% overall usage at the "Performance" tab and the 60% graphically on _all_ 8 cpu cores. Does this mean that the process is split in 8 threads all doing the same task?
I'm more a Linux expert so I perhaps misinterpret the Windows cpu values.
Thanks!
Joern
Vitaliy S.
VP, Product Management
Posts: 27377
Liked: 2800 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Proxy CPU usage

Post by Vitaliy S. »

JWester wrote:Is it really possible that one backup job is spread on 8 cpus? I would have expected only 1 or 2 cpus to be used.
I have just talked to our dev team leader and he told me that this is absolutely expected, as each Veeam process started on the Windows machine has multiple threads belonging to this process, and its operating system scheduling that gives access to system resources to these threads, so what you see is the normal behavior. Hope this helps!
Post Reply

Who is online

Users browsing this forum: No registered users and 14 guests