Respository Server : High CPU Usage And Hang state.

[hoon0715]

Running the backup job increases the cpu usage of the repository server to 100% and enters the Hang state.
Backup job is successful after repository server reboot.

Repository Server currently has 32 vCPUs.
One backup job has usually five or six vm


https://www.veeambp.com/appendix_a_sizing

According to the sizing guide on the link above, Repository Server need one core per "job", is "job" mean one VM?

Even if it was one VM per job, I didn't run many jobs.
How can I solve this problem?

[HannesK]

Hello,

How can I solve this problem?

in general: by asking Veeam support. what is the case number?

32 vCPU for a repository sounds pretty much for me except you have thousands of VMs and hundreds of TB of data. But then, the design with a virtual repository is strange.

Who much RAM does the machine have? 128 GByte?

One job means one backup job / backup copy job / whatever job. But this is not for the repository server. That's for the backup server.

Best regards,
Hannes

[foggy]

According to the sizing guide on the link above, Repository Server need one core per "job", is "job" mean one VM?

1 core per task actually, where a task is a VM disk during backup and either job or VM (in case per-VM backup chains are enabled) during synthetic operations.

[hoon0715]

I'm sorry all.
I was mistaken.
CPU 100% is proxy server, not repository server.
I added more resource to repository server VM, it works well.
(vcpu 2 / ram 4 -> vcpu 8 / ram 16)

[foggy]

So, do you still have issues with the proxy server then? How many concurrent tasks is this proxy configured to handle?