I have a number of backup jobs, some of which are content that changes regularly, so need to run every day.
Others are ‘large’ sets of data, that rarely change. I have these set to run once per week.
It would be good if it were possible to define the ‘priority’ of a backup job, and if a job of a higher priority were added to the queue while a low priority just were running, the low priority job would ideally be moved to the tail of the queue, allowing the higher priority jobs to run. An acceptable alternative would be for the low priority job to be stopped and removed from the queue.
This would enable the ‘frequent’ backup jobs to still be processed daily, even if a longer term backup job were running on a large data set.
Is this something that could be considered?