I'm running into an issue where what appears to be a system default or limitation is causing a backup to be skipped. I have a weekly full backup that is occasionally running for more than 24 hours beyond the next job in line scheduled start time. This is causing that next scheduled job to be skipped. Is there a way to set the "time out" longer or to have the job simply run next, no matter how long the job infront takes?
Thanks in advance.
Solved! Go to Solution.
Increase the time window of the next job which is scheduled to run after the weekly
job. So the job will remain in queued status untill the weekly full backup is not over.
Thanks for the response. Sadly it is not that simple. The scheduling plays into our monthly off site backups.
I really need the backups to run on right after the other no matter how much time lapses.
If the issue is happening with the backup jobs that is backing up same resources then you can try creating the job using a policy and then apply template rules so that the job does not skip
I would go with the PKH answer - or increase the number of backup devices so you can run jobs in parallel to get them within the 24hour start limit.