Manage System Service — AnyFileBackup

Topic Content

This option defines action properties for controlling Windows system services. It may be necessary to launch the Task Processor with system administrator's permissions to execute this action.

System Service

▪	Service name

A name of a Windows system service that will be managed by AnyFileBackup. Use drop-down list to find a service currently installed in your system.

▪	Service list

Click the 'Refresh' button to update the service list (see above).

▪	Service action

A type of command that will be sent to a selected system service. the following options are available:

▪	'Start': a selected service will be started. If it is already started nothing will happen, and if it is disabled this will be considered as an error.

▪	'Stop': a selected service will be stopped. If it is already stopped or disabled, nothing will happen. Please note, that some services cannot be stopped.

▪	'Pause': a selected service will be paused. If it is already paused, stopped, or disabled, nothing will happen.

▪	'Resume': a selected service will be resumed. If it is already started, stopped, or disabled, nothing will happen. Please note, that some services cannot be paused -- they can only be stopped.

▪	Connect through

▪	'--': you connect to a services directly.

▪	'Remote account': access to a services 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 services 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.

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.

▪

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