Hello,
I tried to calculate the CPU/RAM resources for my VMware environment.
When I follow the VBR user guide and the BP Veeam, I troubled by the rule from the BP “1 repository core per 3 proxy cores” because there is no mention of the tasks limitation in relation to this rule.
I worked with the following information:
Proxy:
• 1 CPU = 2 tasks(user guide = BP Veeam)
• 1 CPU = 2 GB RAM (user guide = BP Veeam)
Repository:
• 1 CPU = 2 tasks (user guide)
• 1 CPU = 2 GB RAM (user guide)
• 1 repository CPU per 3 proxy CPU (BP Veeam)
• 1 CPU = 4 GB RAM (BP Veeam) I do not follow this rule
For example for an all-in-one server, I want 6 concurrent tasks for the proxy role.
For the Proxy role, I can set CPU/RAM resources without difficulty.
If I apply the rule 3 proxy CPU / 1 repo CPU repo, I have the following result.
So I should limit the concurrent task for the repository role to 2 for a VM with 6 VMDK.
VMware Backup Proxy :
- Tasks = 6
- CPU = 3 (6 / 2 )
- RAM = 6
Backup Repository:
- Tasks = 2
- CPU = 1 (3 / 1)
- RAM = 2
I guess I will be limited by the repository with 4 pending tasks for the proxy?
VBR 12 set the option “use per-machine backup files” for the repository role by default.
My understanding and that this option change:
• Backup Chain Formats : a separate backup file for every machine in the job
• How the repository tasks are managed (job vs VM disk)
If I understand correctly, this difference is essential for task management and therefore for the CPU/RAM resources of the repository role. In this case, the "3 proxy processors / 1 repository processor" rule makes no sense?
Task Limitation for Backup Repositories
The number of tasks that Veeam Backup & Replication creates during data protection or disaster recovery jobs depends on the type of backup chains stored on the backup repository:
• For regular backup chains, Veeam Backup & Replication creates 1 task per job.
• For per-machine backup chains, Veeam Backup & Replication creates 1 task per every VM disk (that is, a disk of a VM added to the job).
Would it be better to have the same concurrent task limit for both roles and allocate resources accordingly?
Note: I know each role need minimum CPU/RAM resources and I know the bandwidth impact the performance.
I read the user guide, BP and the forum but the product has evolved and perhaps the answers have too.
vmware-vsphere-f24/repository-tasks-cal ... 73244.html
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
veeam-backup-replication-f2/concurrent- ... 62605.html
I tried to calculate the CPU/RAM resources for my VMware environment.
When I follow the VBR user guide and the BP Veeam, I troubled by the rule from the BP “1 repository core per 3 proxy cores” because there is no mention of the tasks limitation in relation to this rule.
I worked with the following information:
Proxy:
• 1 CPU = 2 tasks(user guide = BP Veeam)
• 1 CPU = 2 GB RAM (user guide = BP Veeam)
Repository:
• 1 CPU = 2 tasks (user guide)
• 1 CPU = 2 GB RAM (user guide)
• 1 repository CPU per 3 proxy CPU (BP Veeam)
• 1 CPU = 4 GB RAM (BP Veeam) I do not follow this rule
For example for an all-in-one server, I want 6 concurrent tasks for the proxy role.
For the Proxy role, I can set CPU/RAM resources without difficulty.
If I apply the rule 3 proxy CPU / 1 repo CPU repo, I have the following result.
So I should limit the concurrent task for the repository role to 2 for a VM with 6 VMDK.
VMware Backup Proxy :
- Tasks = 6
- CPU = 3 (6 / 2 )
- RAM = 6
Backup Repository:
- Tasks = 2
- CPU = 1 (3 / 1)
- RAM = 2
I guess I will be limited by the repository with 4 pending tasks for the proxy?
VBR 12 set the option “use per-machine backup files” for the repository role by default.
My understanding and that this option change:
• Backup Chain Formats : a separate backup file for every machine in the job
• How the repository tasks are managed (job vs VM disk)
If I understand correctly, this difference is essential for task management and therefore for the CPU/RAM resources of the repository role. In this case, the "3 proxy processors / 1 repository processor" rule makes no sense?
Task Limitation for Backup Repositories
The number of tasks that Veeam Backup & Replication creates during data protection or disaster recovery jobs depends on the type of backup chains stored on the backup repository:
• For regular backup chains, Veeam Backup & Replication creates 1 task per job.
• For per-machine backup chains, Veeam Backup & Replication creates 1 task per every VM disk (that is, a disk of a VM added to the job).
Would it be better to have the same concurrent task limit for both roles and allocate resources accordingly?
Note: I know each role need minimum CPU/RAM resources and I know the bandwidth impact the performance.
I read the user guide, BP and the forum but the product has evolved and perhaps the answers have too.
vmware-vsphere-f24/repository-tasks-cal ... 73244.html
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
veeam-backup-replication-f2/concurrent- ... 62605.html
Statistics: Posted by StephKT — May 12, 2025 3:00 pm
