| Content Previous Next |
Topic Content | |||||||||
|
| ||||||||
This option defines when task starts. | |||||||||
|
| ||||||||
| Regardless of the time of task activation, task will start strictly according to specified schedule. | ||||||||
| When activated (either automatically or manually), task immediately starts to perform designated actions (that is file copying, monitoring, etc). Defined schedule is overridden at this stage.
When task is completed (for example, when file copying has been finished), it will enter into a 'sleep' state waiting for the next scheduled event (for example, 8.00 PM next day) or another instance of deactivation-activation (whichever is the earliest).
Examples when this mode may be suitable include:
Please also read how task starts when a snapshot of Source has to be made at the Activation stage. | ||||||||
|
| ||||||||
Certain tasks require a considerable amount of time to complete. While task is being performed, a new start event may occur. In this situation AnyFileBackup will continue performing task (it will not interrupt task to start it again) but will remember that conditions for task start have been satisfied and will start task immediately after it has completed the last action in the Task Scenario.
If a start event occurs more than once when performing task (for example, task is set to start every 2 minutes), AnyFileBackup will act in the same way (that is start task immediately after it has completed the last action in the Task Scenario) -- it will NOT queue these start attempts to start task a number of times equivalent to start events that have occurred when task has been performing. | |||||||||
| Task starts at regular intervals defined by user. The interval may be set in minutes, hours, days, months, week days or any combination of these. | ||||||||
Example No.1:
That means that task will start every 2nd of August at 22.45. | |||||||||
Example No.2:
That means that task will start every Friday which is the 2nd day of a month (for example, 2nd of August 2013 which was Fr): at 00.00, 00.15, 00.30, 00.45, and then again at 04.00, 04.15, 04.30, 04.45, and again at 08.00, 08.15 and so on. | |||||||||
'Advanced mode': this mode allows to use a UNIX style time format (CRON). All time intervals need to be entered manually. For more details about advanced time format see the CRON time format topic. | |||||||||
Example No.1 in CRON:
| |||||||||
Example No.2 in CRON:
| |||||||||
| Task starts every week at particular time on selected day. Task may run several times a day. Number а scheduled runs is unlimited.
Example:
To add a scheduled run do the following:
A new line will appear at the table and the '+' (plus) symbol shows on which days of the week task will start.
To delete a line, select it and press the 'Delete' button.
To remove all entries in the table, press the 'Clear' button.
To undo all changes, press the 'Undo' button at the bottom right corner of the Task Properties window. | ||||||||
| Task starts only when you press the 'Start Task Manually' button at the Main Window. | ||||||||
| Task starts when it receives a command from another AnyFileBackup task. Thus, there may one so-called a 'Master task' which launches a 'Dependent task' (linked task) depending on the circumstances.
If a linked tasks, when already being performed, receives a new start request from another task, it will finish its current activity and will start again immediately after that (in other words, it will remember this new start request).
Example: if Master Task fails, launch 'Dependent task-1'; if 'Master Task' partly successful, launch 'Dependent task-2'. | ||||||||
| Task starts every time changes occur in Source (for example, when a new file has been created). In this mode AnyFileBackup constantly monitors Source.
A delay between the changes and task start is 2 seconds minimum (999 seconds maximum). This is to ensure that a new file is not blocked by other application. This mainly happens if a large file is being downloaded or saved which normally takes some time.
Limitations of this schedule type:
| ||||||||
|
| ||||||||
Sometimes in addition to standard schedule rules it is necessary to make a task start conditional upon existence (or non-existence) of some file or directory, or a value of system variable.
This option is designed to achieve this. If any condition (that is either A or B) is satisfied, task will start. If there is no match at all (that is both conditions are not satisfied), task will not start. If any of the fields left blank, then this condition is not considered by AnyFileBackup.
In other words, task will only start if and only if:
| |||||||||
| The first condition is existence or non existence of a file or folder.
Examples:
| ||||||||
| The second condition is the value of environment variable. An environment variable is a value which may be used by both other AnyFileBackup tasks and third party software for quick access to certain information (for example, a working path, a filename, Task ID to start).
Environment variables may be viewed here:
| ||||||||
| Content Previous Next |