Manage Other AnyFileBackup Task

 Content Previous Next

Topic Content

Other Task

Additional File Filter

Miscellaneous

 

 

This option defines action properties for controlling another existing AnyFileBackup task.

 

 

Other Task

▪Task name

A name of an existing AnyFileBackup task that will be managed by AnyFileBackup.

▪Task command

A command that is sent to another task. The following commands are supported:

 

▪'Start task': this is an equivalent of pressing the 'Activate Task' and 'Start Task Manually' buttons on the panel in the Main Window (therefore, it is irrelevant whether another task has already been activated or not). However, if task's 'Activation type' is set to 'Disabled', this task will not start and this will be considered as an error.

 

▪'Interrupt task': another task will be stopped but will remain in an active state waiting for next start event.

 

▪'Deactivate task': this is an equivalent of pressing the 'Deactivate Task' button on the panel in the Main Window and will completely deactivate another task.

 

 

Additional File Filter

This option is visible and applies if, and only if, the action is a PART of the Backup step of the Task Scenario.

 

Additional File Filter distinguishes files by mask determining to which file(s) this particular action will or will not apply. In all other respects it is no different from the Additional File Filter that exists in every Target.

▪Included files

A list of file masks that describe files to which this particular action will apply.

 

Please note, that these masks should somehow overlap with masks specified in SOURCE > Additional File Filter > Included Files (if in use) and should not be completely excluded by masks specified in SOURCE > Additional File Filter > Included Files (if in use). Otherwise, this action will not apply to any files.

▪Excluded files

A list of file masks that describe files to which this particular action will not apply.

 

 

Miscellaneous

▪Condition

This option is visible and applies if, and only if, the action is located BELOW the Backup, Two-Way Synchronization, Monitoring, or Clean-up step of the Task Scenario.

 

This is a description of an event upon occurrence of which this action will be performed. The event relates either to Source or to task generally. The following events are covered:

 

▪'Always': action is event-neutral and will always start when AnyFileBckup reaches it at the Task Scenario.

 

▪'Success': the term 'success' refers to successful completion of either:

-- Backup stage (all files have been transferred from Source to Target(s) and other actions within Backup have been performed), or

-- Two-Way Synchronization stage (Source 1 and Source 2 have been synchronized), or

-- Monitoring stage (Source parameters that are being monitored are exceeded their threshold limits or relevant changes have occurred).

 

When any of these stages is completed properly (depending on the task type), action with this condition will perform.

 

▪'Error': action will start when task has not performed properly and produced an error. This error may occur at any previous stage of task scenario. Please note that this action will only work if task 'on error' behaviour is set to 'continue task execution' (see Task error handling for details), otherwise this action will not start. It is also recommended put action with this condition at the end of the task scenario, so it can catch any errors that have occurred in a course of task performance.

 

▪'No changes': this condition is the opposite to the 'Success'--when nothing happens at any of the stages described above: no files have been transferred between Source and Target(s), Source parameters that are being monitored are within their threshold limits or no relevant changes have occurred.
▪Wait until completion

If enabled, task will wail until another AnyFileBackup task is finished (that is when one task scenario round is fully completed, or stopped because of an error (as the case may be), and entered in into a passive state waiting for the next scheduled start).

 

Please use this option with caution because it may significantly delay task performance if another AnyFileBackup task transfers significant number of files or large files or connection speed between Source and Target is low. To eliminate this risk please consider using the 'Timeout' option (see below).

▪Timeout

A time limit in seconds for waiting another AnyFileBackup task to be finished as described in the 'Wait until completion' section (see above). Upon expiration of this time limit task will continue as usual despite that another AnyFileBackup task may still be running. It is recommended to use a time limit.

 

By default, 180 seconds timeout is applied. If left blank, AnyFileBackup will automatically insert 180 seconds as a timeout value.

 

'0' (zero) means that task will wait indefinitely for another AnyFileBackup task to be finished.

 

This option activates only when the 'Wait until completion' option is enabled.

▪Enabled

If enabled, this action is active and will be used in Scenario. If disabled, it will remain in the Task Scenario but will be completely ignored by task. To distinguish it from enabled actions, disabled actions are strokeout and coloured in gray.

▪Title

This is a custom name that will be displayed in the Task Scenario instead of the default title. Press the 'Apply' button for changes to take effect.

 Content Previous Next