Hello,
I have a little configuration question:
We backup daily our SQL servers. Due to reverse incremental and the size of data (around 60TB, and Read 3,2TB), the backup job takes a long time compared to forward incremental (around 10hrs).
Starting in the morning, the backup is usually still running, which currently is blocking any other job from starting (which is generally fine, because we want to jobs to go in sequence).
Though, we have a job that we manually start as needed. The problem is, if the SQL backup job is still running, the manual job is pending and remains so until SQL job finishes. The manual job is however in comparison small and could be done in parallel.
We have limited our Scale-Out Repo to Max 4 concurrent tasks and Backup Proxy to 8 concurrent tasks.
The SQL job takes up all 4 concurrent tasks leaving no available tasks for the small pending job.
If we up the Repo tasks to 6, SQL job will take 6... etc.
Is it possible somehow to configure Veeam to allow the smaller job to run parallel to the SQL job, even if it's not yet completed? It would have thought that it might be possible to set the SQL job to backup only 3 VMs at the same time, but that option is not available as far as I can see.
Any suggestions?
Thanks
Kosta
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jun 12, 2024 6:41 am
- Contact:
-
- Veeam Software
- Posts: 3807
- Liked: 640 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Concurrent jobs
Hello and Welcome to Veeam R&D Forums!
I would try to assign a high priority to the "manual" job. Look at this wizard step.
Thanks!
I would try to assign a high priority to the "manual" job. Look at this wizard step.
Thanks!
Who is online
Users browsing this forum: No registered users and 22 guests