Start Application

 Content Previous Next

Topic Content


Additional File Filter




This option defines action properties for launching external applications (both executable and non-executable). It may be necessary to launch the Task Processor with system administrator's permissions to execute this action.




Run file

A full path and application file that will be executed by AnyFileBackup. Executable applications (that have EXE, COM, or BAT extensions) will be launched as usual; non-executable files (for example, DOC, TXT, etc) will be opened with an associated default application (default application can be set manually in Windows).


A command line parameter that will be added after the file name. Only application-specific (that is application that is launched) parameters, macros, and commands (if any) are permitted in this field.

Run in

A local or LAN folder (but not FTP or cloud) where an executable application will be launched (not required for non-executable files). This is particularly necessary when a command line parameter (see above) is a file located in a folder other than the executable application's installation folder (otherwise it will be necessary to include a full path to that file as a command line parameter; when you specify 'Run in' folder it is enough to specify filename only as a command line parameter).


If left blank, the application will run in the folder set in the 'Run file' field above. If there is no path in the 'Run file' field, then it will run in AnyFileBackup current installation location.

Connect through
'--': you connect to a file directly.


'Remote account': access to a file requires a remote computer address, username, and password. Please read below how to select, access, and configure your account on a remote computer.
Account name

If you connect to a file located on a remote computer, here you may select your pre-configured remote account. If there is none, or you need to create a new one, access remote account properties as described below.

Account properties

Click the 'Edit' button to access the Remote Accounts manager where you can create and configure your remote accounts. Detailed information about this can be found here.



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.





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 an executable application is closed (that is unloaded from system memory) or, in case of a non-executable file, until a file is no longer opened with an application that has been used to open it.


Please use this option with caution because it may significantly delay task performance if some application does not work correctly and remains running for a long time. To eliminate this risk please consider using the 'Timeout' option (see below).


A time limit in seconds for waiting a file to be closed as described in the 'Wait until completion' section (see above). Upon expiration of this time limit task will continue as usual despite that a file may still be running or opened. 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 a file to be closed.


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

Verify settings

Press the 'Start' button to direct AnyFileBackup to immediately launch this action. This will verify whether all above settings were entered correctly; all errors, if any, will be displayed in a log window.


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.


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