-
- Enthusiast
- Posts: 34
- Liked: 4 times
- Joined: Feb 10, 2022 1:16 pm
- Full Name: david lopez
- Contact:
Sequential execution
Hello,
The scenario is as follows: We make a backup of 5 domain controller machines and backup is made according to the order that we have indicated in the task. It can be specified not to process a machine until the previous one has been backed up. That is, make a machine-to-machine backup. We have seen that it can be limited in the proxy or in the repository but that does not help us since there are other backup tasks that also need to be executed.
Thank you.
The scenario is as follows: We make a backup of 5 domain controller machines and backup is made according to the order that we have indicated in the task. It can be specified not to process a machine until the previous one has been backed up. That is, make a machine-to-machine backup. We have seen that it can be limited in the proxy or in the repository but that does not help us since there are other backup tasks that also need to be executed.
Thank you.
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Sequential execution
Backup processing is always done in a parallel way.
You define the Task Slots for Repository and Proxy and Veeam will start as many backup in parallel as we can to optimize backup window.
The rule is VMs within same job get priority over additional jobs that start.
AD Server backup with our Veeam Guest Processing can be done in parallel and there should not be any side effects for the application.
Maybe let´s discuss first why you want to do the backup in that specific way so that I can maybe guide you to some workaround.
You define the Task Slots for Repository and Proxy and Veeam will start as many backup in parallel as we can to optimize backup window.
The rule is VMs within same job get priority over additional jobs that start.
AD Server backup with our Veeam Guest Processing can be done in parallel and there should not be any side effects for the application.
Maybe let´s discuss first why you want to do the backup in that specific way so that I can maybe guide you to some workaround.
-
- Enthusiast
- Posts: 34
- Liked: 4 times
- Joined: Feb 10, 2022 1:16 pm
- Full Name: david lopez
- Contact:
Re: Sequential execution
ok, the environment is:
- We have five domain controllers. One of them is the main one (it contains the roles) and the rest are secondary. We've set up a task for all five of us and left the main one running first. What happens is that a few seconds after starting the backup of the main one, the backup of the second begins to execute, then the third,... and in the end there are all five in parallel (since that is how it is defined in the concurrent tasks of the proxy and of storage). The question is whether the main one should be executed independently of the rest in case there are problems (with logs, when restoring,...), that is, the backup should not be executed in parallel to the rest.
Thanks a lot.
- We have five domain controllers. One of them is the main one (it contains the roles) and the rest are secondary. We've set up a task for all five of us and left the main one running first. What happens is that a few seconds after starting the backup of the main one, the backup of the second begins to execute, then the third,... and in the end there are all five in parallel (since that is how it is defined in the concurrent tasks of the proxy and of storage). The question is whether the main one should be executed independently of the rest in case there are problems (with logs, when restoring,...), that is, the backup should not be executed in parallel to the rest.
Thanks a lot.
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Sequential execution
Then I would just place the 5 servers in maybe 5 different jobs and schedule them for different timeslots.
If you are worried that the other jobs take too long until these jobs are finally executed you can enable the "high priority" setting:
https://community.veeam.com/blogs-and-p ... -works-554
If you are worried that the other jobs take too long until these jobs are finally executed you can enable the "high priority" setting:
https://community.veeam.com/blogs-and-p ... -works-554
-
- Enthusiast
- Posts: 34
- Liked: 4 times
- Joined: Feb 10, 2022 1:16 pm
- Full Name: david lopez
- Contact:
Re: Sequential execution
Ok, Thank you
Who is online
Users browsing this forum: Bing [Bot], Semrush [Bot] and 82 guests