-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 09, 2024 8:28 pm
- Full Name: Joshua H
- Contact:
Task Count Question
Is there a connection between the job count of the main B&R server and the proxies? We have three proxies for one of our VMware environments and all the policies for that environment is setup to use those. The B&R server is setup to run 16 tasks, and the proxies are set to run 16 each (48 total) but the jobs never seem to go over 16.
-
- Service Provider
- Posts: 595
- Liked: 146 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
Re: Task Count Question
maybe your repository is set to 16?
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 09, 2024 8:28 pm
- Full Name: Joshua H
- Contact:
Re: Task Count Question
I was just about to update that our repo doesn't have a limit set currently.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Sep 12, 2024 8:43 am
- Full Name: Julian Luciano Hauser
- Contact:
Re: Task Count Question
The limit of concurrent tasks is based on the CPU and RAM.
vSphere Proxy:
2 cores + 1 vCPU for 2 simultaneously running jobs
2GB RAM + 1GB for simultaneous job
VBR:
4GB RAM + 500MB for each concurrent job
The highest number of concurrent task which you can select is determined by the VM resources
Additionally you can check the Job Logs you determine a possible Bottleneck in your infrastructure
vSphere Proxy:
2 cores + 1 vCPU for 2 simultaneously running jobs
2GB RAM + 1GB for simultaneous job
VBR:
4GB RAM + 500MB for each concurrent job
The highest number of concurrent task which you can select is determined by the VM resources
Additionally you can check the Job Logs you determine a possible Bottleneck in your infrastructure
-
- Veeam Software
- Posts: 2721
- Liked: 628 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Task Count Question
Hi jhol,
When you say the jobs never go above 16, can you elaborate a bit? You see that only 16 total tasks are started, or can you maybe show what you're seeing?
I'm not confident based on the description that this is about concurrent tasks, you should have plenty available. There are a few other environmental items that may be affecting this, but it's best to open a Support Case and let Veeam Support review the environment. Be sure to include logs for Support to review. (Use the 1st radio button, ctrl+click or shift+click to select the affected jobs, and proceed with the log export)
But if there are no limitations on the repository tasks, then it's best to let Veeam Support review the jobs and determine why further tasks aren't being started. Please share your case number once created.
Thanks!
When you say the jobs never go above 16, can you elaborate a bit? You see that only 16 total tasks are started, or can you maybe show what you're seeing?
I'm not confident based on the description that this is about concurrent tasks, you should have plenty available. There are a few other environmental items that may be affecting this, but it's best to open a Support Case and let Veeam Support review the environment. Be sure to include logs for Support to review. (Use the 1st radio button, ctrl+click or shift+click to select the affected jobs, and proceed with the log export)
But if there are no limitations on the repository tasks, then it's best to let Veeam Support review the jobs and determine why further tasks aren't being started. Please share your case number once created.
Thanks!
David Domask | Product Management: Principal Analyst
-
- Veeam Software
- Posts: 1839
- Liked: 661 times
- Joined: Mar 02, 2012 1:40 pm
- Full Name: Timothy Dewin
- Contact:
Re: Task Count Question
As David said, best to open a support case. I will add that "RTS.ResourcesUsage.log" is an interesting log on the VBR server to see task consumption and to confirm your suspicions (https://www.veeam.com/kb4463 to understand where the log location is).
Who is online
Users browsing this forum: No registered users and 35 guests