Hi
In proxmox we almost always use 1 socket and n cores. Veeam deploys workers by default with n sockets 1 core (n being the number of vCPUs configured for the worker in veeam).
At least since v13 this is reconfigured on each backup/restore operation for the worker used, so a manual change of the worker vm is not persistent.
In "C:\Program Files\Veeam\Plugins\PVE\Service\appsettings.json"
There is a setting under Workers:
"VcpuSocketsOverrideToCores"
which, when set to true, switched the behaviour - now the workers are configured to 1 socket n cores by veeam.
This setting is not documented and was not provided by veeam, but it's our desired configuration and from my limited testing does exactly what it says.
-
vitami
- Influencer
- Posts: 21
- Liked: 5 times
- Joined: Oct 28, 2021 2:30 pm
- Contact:
-
Mildur
- Product Manager
- Posts: 11155
- Liked: 3080 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Worker Sockets vs Cores
Hi Vitami,
In general, we don’t document configuration parameters, as the default settings are designed to work for all deployments. Any changes should only be made if requested by a Veeam support engineer in a case or if a KB article provides instructions for specific scenarios.
The good news is that the socket/core situation will be addressed in one of the upcoming updates, where the default value of this parameter will be set to “True”.
Thank you,
Fabian
In general, we don’t document configuration parameters, as the default settings are designed to work for all deployments. Any changes should only be made if requested by a Veeam support engineer in a case or if a KB article provides instructions for specific scenarios.
The good news is that the socket/core situation will be addressed in one of the upcoming updates, where the default value of this parameter will be set to “True”.
Thank you,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 2 guests