Scenario 1: Granular Scheduling

This advanced scheduling technique allows for a job to be scheduled to run at different times each day. By configuring the job to run "Periodically every 1 Hour" and then using the Schedule button to assign which hours the job may start, it is possible to create a fully granular schedule.

Notes:

• If the job is still running at a time when it is scheduled to start, the job run that would have occurred is skipped.
• The time slot selected does not limit the job's run duration. It only indicates to the backend scheduler that the job is permitted to start.
• If a day of the week has a Synthetic Full or Active Full scheduled, that Full operation will only occur during the first job run on that day.
• When configuring a job to run more than once per day, changing the job's retention to a "# of days" retention model can make retention easier to understand.

Example: A company wants to configure their backup job to create a restore point every two hours during business hours, but only once a day during the weekends.

The administrator would configure the job to run every 1 hour. Then, click the Schedule button and select the time slots that align with the desired schedule.