| Content Previous Next |
Topic Content | |||||||||||||||||||||
|
| ||||||||||||||||||||
This option defines whether task is active or disabled and how task becomes active. | |||||||||||||||||||||
|
| ||||||||||||||||||||
A 'TRIAL MODE' heading reminds that AnyFileBackup works in a trial mode. In this mode the 'Automatic activation' option is unavailable. When AnyFileBackup is registered, this reminder will be automatically removed and the 'Automatic activation' will be fully functional. | |||||||||||||||||||||
| Task becomes active automatically, without user's intervention, on AnyFileBackup start up, user log on, or service log on (depending on the selected Working Mode). This mode is unavailable in TRIAL VERSION. Even if selected in Trial version, AnyFileBackup will work in Manual mode instead. | ||||||||||||||||||||
| Task is inactive by default but can be activated manually by pressing the 'Activate Task' button in the main window. | ||||||||||||||||||||
| Task is permanently inactive and will never start. Task cannot be activated manually from the main window. To allow task become active, change this option to 'Automatic' or 'Manual'. | ||||||||||||||||||||
|
| ||||||||||||||||||||
Task activates with a delay which ranges between 1 and 60 seconds. This option may be useful for those who have many tasks which are activated contemporaneously or tasks which require extensive system resources (for example, making a new snapshot of thousands of files located on LAN).
Example:
Activation needs certain system resources because it may need to make a snapshot of Source. If many tasks start simultaneously, system core and RAM may be loaded more than usual. By delaying activation of certain tasks you may decrease the use of system resources and prioritise your tasks without any disadvantage to your backup and synchronization. | |||||||||||||||||||||
|
| ||||||||||||||||||||
A snapshot is a status (that is file lists and file properties like size, timestamp, CRC, etc.) of Source at the time of task activation. AnyFileBackup needs to make a snapshot at least ones -- before the first task start.
Making an initial or subsequent snapshot may take a considerable amount of time. While making a snapshot, a start event may occur. In this situation AnyFileBackup will not start task but will make a record that conditions for task start have been satisfied and will start task immediately after a snapshot has been made.
If a start event occurs more than once when a snapshot is being made (for example, task is set to start every 2 minutes), AnyFileBackup will act in the same way (that is to start task immediately after a snapshot has been made) -- but it will NOT queue these start attempts to start task a number of times equivalent to start events that have occurred while a snapshot has been being made. | |||||||||||||||||||||
| Snapshot is created every time task is activated (either automatically or manually). This may require certain system resources. When many tasks activate simultaneously and start creating their snapshots, system may be loaded more than usual. Please consider using the 'Activation delay' option (see above) to prevent system overloading.
It is recommended to create a new snapshot every time task is activated. This will ensure that only relevant files are transferred.
Example: task made an initial snapshot of Source, performed properly and then was deactivated. Then (after task was deactivated) new files were added to Source. When this task is activated again later it will not backup these new files unless the 'Make a new snapshot' option is enabled. This is simply because task knows only about files listed in its snapshot. | ||||||||||||||||||||
| Snapshot (created at first task activation) is used every time task is activated (either automatically or manually). | ||||||||||||||||||||
|
| ||||||||||||||||||||
This group of settings defines what happens when task has produced an error.
An 'error' is generally any misbehaviour in task performance. This may be, for example, a failure to copy a file because a Target folder was inaccessible, or lack of disk space in Target, or failure to restart or hibernate a computer after backup completion, or interruption of connection to FTP server. | |||||||||||||||||||||
| This option defines how AnyFileBackup responds to any errors. Three options are available:
| ||||||||||||||||||||
| When selected, this option allows to define custom (aka 'task-specific') error handling settings (see below) overriding common error handling properties. | ||||||||||||||||||||
| Before AnyFileBackup proceeds according to the 'On error' rules (see above), it may attempt to perform an action or a step, which caused the error, again. This option defines a number of attempts to perform this faulty action / step. If the last attempt is unsuccessful, AnyFileBackup will proceed according to the 'On error' rules. | ||||||||||||||||||||
| This option defines an interval (in minutes) between attempts to perform a faulty action / step. While waiting, task will not proceed but wait for the next attempt to perform such faulty action / step. | ||||||||||||||||||||
|
| ||||||||||||||||||||
| Click the 'Edit' button to access task advanced options. These options are intended to be used in those rare situations when task needs special treatment or does not perform properly. We do not recommend to change or use any of these settings unless absolutely necessary. | ||||||||||||||||||||
| Task Maintenance
File Options
Example: consider the following 'Backup' step of the task:
Outcome 1 -- Actions apply to files and folders: when any single folder has been copied to (=created in) Target (yet before files have been copied), a delay of 60 seconds will occur; the same will happen after each file has been copied.
Outcome 2 -- Actions apply to files only: copying of a folder to Target does not trigger the delay; the 60 seconds delay will only occur after a file has been copied to Target.
This is not to suggest that if actions apply to files only, then no folders will be copied to Target -- quite the opposite: folders will be copied as usual. The only difference is that they (folders) will not trigger any actions and will not be caught by any actions (will not be listed separately in the list of copied items, etc).
We generally recommend to apply actions to both files and folders.
Task Information
| ||||||||||||||||||||
| Content Previous Next |