Add an option to delay job start until the previous job has finished

[Spencer Simpson]

(Support case #04021174)

This can apply to any type of job, but it might be needed most in this type of job.

I had a very large full initial backup that had to be copied out to object storage. The copy job is linked to the disk backup job as a secondary target.

Because of its size, the backup to disk, plus the time it then took to copy to object storage, ran in to the time of the next backup.

Instead of waiting, the next instance started, causing the copy of the initial full backup to fail. The workaround was to disable the schedule and re-run the copy job, then re-run the schedule.

After the workaround worked, I wanted to do a health check of the backup. But again, this ran in to the time of the next backup, and was canceled as failed.

Backup windows were suggested, but these require knowing how long every instance of the job is supposed to take, and they only block jobs from running, when that block may not be necessary.

A scheduling option to delay a job start until the previous job has finished, or until the involved backup is no longer busy, seems sensible to me.

[sfirmes]

Have you tried using a SOBR with a Capacity Tier instead of a backup copy job? This might help since the offload to the Capacity Tier will happen as soon as the initial backup completes.