Scheduler and activity periods
The two main features of CodeTwo Backup which are backing up and restoring the data are ran as so called jobs. Jobs, once configured can be executed either manually or automatically taking an advantage of a built-in scheduling feature. In both of the above scenarios Jobs work the same way with the only difference being their execution type. However, jobs can be also divided based on their continuity scenario. CodeTwo Backup supports One-time backup or restore Jobs and Continuous incremental backup Jobs. A complete backup or restore operation is called a Cycle and the time during the Job is supposed to work is called Activity Period.
One-time Jobs, once started perform one Cycle of the defined task (either backup or restore) and stop when finished. If you stop such a Job manually while it is working, the next time this particular job is started again, the software will rescan the mailbox and already backed up or restored content to compare both and perform the defined task on modified items again. Unchanged and already backed up or restored items will not be processed again, the software will resume the Job where it finished before.
Continuous Jobs run in multiple Cycles and are limited to backup tasks. They differ from One-time Jobs in terms of what happens when the Cycle is finished. All backup Jobs in CodeTwo Backup are incremental, that means they can be ran many times on a mailbox, recognize changes in already backed up items and back those changes up again, each time the Job finds one. Continuous Jobs give users the ability to have the desired mailbox scanned constantly. In this type of a job, as the software finishes backing up a mailbox it pauses for the user-defined idle time and scan the mailbox for changes again starting a new Cycle. If any changes or new items are found, the Job backs them up. If this kind of a Job is manually stopped, once restarted it will proceed in similar manner as One-time Job i.e. only new or changed items will be backed up again, aside from this the software will just picks where it left off previously.
As mentioned before, Jobs can be ran automatically using the built-in scheduling feature. CodeTwo Backup Scheduler works in a similar manner to a Windows Scheduler, allowing an admin to plan and execute the desired Job without the need for user attendance. When configuring the Scheduler, a user defines so called Activity Periods which can be considered time slots for Jobs. When the Activity Period starts, the Scheduler executes the defined Jobs. When the Activity Period is over the Scheduler force-stops any still active Jobs, even if they are still in the middle of a Cycle. It is as simple as that. Jobs that were stopped before they actually finished will resume in the next Activity Period, if more then one were defined. Such resumed Jobs will proceed exactly the same way as if they were stopped and restarted manually - Jobs ran by the Scheduler work exactly the same and the same rules apply to them as for manually operated ones. Keep in mind Jobs started or stopped by the Scheduler can always be overrode, allowing a user to e.g. stop a Job executed by the Scheduler or to start one outside its usual Activity Period.
|Fig. 1. Backing up items after the job is stopped and started again.|
|Fig. 2. Running multiple job cycles.|
Scheduling backup jobs - this section describes how to enable and configure each activity pattern in the Scheduler.