Share on Facebook0Share on Google+0Share on LinkedIn0Share on Reddit7Tweet about this on Twitter0

From medium to large companies, the backup window is most of the time critical. Usually, we expect that most of the backup jobs are completed in the night to not impact the production. The other constraint is the backup order. Some backup jobs must not run simultaneously. So, you have to choose at which time the first backup job starts and then make an assumption of the backup duration to start the second job after the first is finished. Because of these two constraints, sometimes it is complicated to plan the backup job and to keep an effective backup window.

Chain backup job

Veeam Backup & Replication can help you to reduce the backup window and to sort backup job thanks to chaining. You can configure a backup job to start just after the previous is finished. Thanks to this feature, you don’t have to make an assumption about the backup job duration. So, you save time between backup job and you reduce the backup window.

In the below example, you can see three backup jobs that are not chained. For each job, the assumption is a duration of 1 hour. But each job is finished before and so time is wasted.

wp-image-8620

Below you can find the same example as above but by chaining job:

  • Backup Job 1 duration: 40mn
  • Backup Job 2 duration: 30mn
  • Backup Job 3 duration: 20mn
  • Total time: 90mn

wp-image-8621

As you can see, compared to not chaining job, you have saved 50mn which is really huge. This is why I always recommend to customer to chain backup job either for small company or large company. Now in the next section, we will see how to chain backup job.

StarWind Virtual SAN eliminates any need for physical shared storage just by mirroring internal flash and storage resources between hypervisor servers. Furthermore, the solution can be run on the off-the-shelf hardware. Such design allows StarWind Virtual SAN to not only achieve high performance and efficient hardware utilization but also reduce operational and capital expenses.
Learn more about ➡ StarWind Virtual SAN.

Configure a backup job to start after one

In the following example, I have two backup jobs. One backup domain controllers and the other standard servers such as WSUS, Remote Desktop Service and so on. Now I want to configure the job Hyper-V – Standard Servers to start just after Hyper-V – Domain Controllers.

wp-image-8622

Edit the properties of the backup job and navigate to Schedule tab. Select After this job and choose the backup job.

wp-image-8623

Now when I look at Next run, I see that the job will start after the job Hyper-V Domain Controllers.

wp-image-8624

Now if I manually start the job Hyper-V – Domain Controllers, I’ll have the following warning. That means that each chained job will be run just after this one will be finished. SO, now be careful to not run all the backup during the working hours 😊

wp-image-8625

Conclusion

If you are using Veeam in production and you need to reduce your backup window, you can definitely implement this feature. It will not break your production and you just have to be careful when you start a job manually.

Views All Time
2
Views Today
4
Appreciate how useful this article was to you?
1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5
5 out of 5, based on 1 review
Loading...
Back to blog
The following two tabs change content below.
Romain Serre
Romain Serre
Senior consultant at Exakis
Romain Serre works in Lyon as a Senior Consultant. He is focused on Microsoft Technology, especially on Hyper-V, System Center, Storage, networking and Cloud OS technology as Microsoft Azure or Azure Stack. He is a MVP and he is certified Microsoft Certified Solution Expert (MCSE Server Infrastructure & Private Cloud), on Hyper-V and on Microsoft Azure (Implementing a Microsoft Azure Solution).