V11 - New feature - Prioritize primary backup job - why and how it works

Userlevel 7
Badge +9

While updating our VCSP stack with V11-RTM, I just stumble again onto this small but fine new feature to prioritize your primary backup jobs:

More than once I had customers request several jobs to be finished with priority.

You could of cause concatenate jobs with the schedule option “After this job:”. But this is not recommended as it does not use the ressources of your backup system accordingly. Valuable proxy/repo slots would linger out-of-work for quite a while.

Overlapping jobs would lead to the second job jumping in with the first one still running, so saturating ressources. But this might easily oversteer and thus delay the first job.

With the new option this problem can be solved by just the click of a checkbox.

Prioritized jobs get a nice little flag in the job list.


So how does it work?

The Veeam scheduler runs all its tasks according to priorities:

  • 800: Restore jobs — restores are obviously the most important jobs
  • 700: Continuous data protection jobs — new CDP ist also considered very important
  • 600: SnapshotDeleter jobs — no snapshot shall linger longer than needed
  • 500: Quick backup jobs
  • 400: High priority jobs — Option is available for backup jobs, replication jobs, agent jobs (managed by backup server) and file share backup jobs.
  • 300: Regular backup and replication jobs
  • 200: Backup copy jobs
  • 100: Archive jobs

The higher the number, the more priority a task will be assigned. The new high priority option fits in just above the regular backup jobs and makes sure they are run with higher priority by the task scheduler. Quick backup jobs can still beat them though.



This icon isn’t the best - being red it makes it look like there is a problem in the list.

Userlevel 7
Badge +22

Very interesting information thanks Michael!

The priority setting is going to help enormously.

As for the “You could of cause concatenate jobs with the schedule option “After this job:” I was always scared of this option as I believe that if something happened to one of the initial jobs and it did not run then the others after it also would not run. I think I may have seen this happen but my memory is blurred. Has anyone ever seen that happen when using “ run after this job”

Userlevel 7
Badge +13

There is also a different icon for high-priority jobs:

Running job looks like any other backup jobs.

Userlevel 7
Badge +1

thank you for your sharing :blush:

Userlevel 6
Badge +1

Thanks for the wonderful share!

Userlevel 7
Badge +13

Great list, thanks for sharing !

Userlevel 7
Badge +8

Thanks for the sharing and priorities for the scheduler. It’s always make more sense when you know what is behind and not just a click on GUI :cowboy:

Userlevel 7
Badge +11

A nice post for a nice feature!

Veeam B&R and our community hub have something in common…

It's always getting better!

Userlevel 7
Badge +14

Great information; thank you very much for sharing!

Userlevel 7
Badge +17

Hey, this list is very useful. Thank you @Michael Melter 

Userlevel 7
Badge +21

Thanks for sharing that list, extensive!