| Content Previous Next |
Topic Content | |||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||
This option defines Target properties for local area network (LAN) and local folders. | |||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||
| A path to a local or LAN folder. | ||||||||||||||||||||||||||||||||||||
| When AnyFileBackup transfers Source files to Target, it does not create a Source folder itself in Target. However, this may be changed. A simple example will illustrate the difference.
Example:
-- Outcome 1 (Target path is not modified): D:Backupreadme.txt -- Outcome 2 (Target path is modified by adding the Source folder name): D:BackupDatareadme.txt
Modifying Target path may be necessary when multiple Source folders are being transferred to a single Target. | ||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||
| If you connect to a Target folder 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. | ||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||
| A list of file masks that describe files to be transferred to this particular Target.
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, no files will be transferred to this Target. | ||||||||||||||||||||||||||||||||||||
| A list of file masks that describe files not to be transferred to this particular Target. | ||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||
This option (previously known as 'Pre-processing') applies to all files before they are transferred to this Target.
The underlying idea is that files may be transferred to some Targets as usual (without any modifications: compression, encryption, etc), and to other Targets (for which this option is enabled) in compressed and (or) encrypted form. Equally, if files are already compressed and (or) encrypted, they may be uncompressed and (or) decrypted before being transferred to Target(s).
File modification may take additional time when large files or significant number of files are processed. | |||||||||||||||||||||||||||||||||||||
| A type of modification that is applied to each file before it is transferred to Target. The following options are available:
| ||||||||||||||||||||||||||||||||||||
| Click the 'Configure' button to access the Modification Options.
Encryption / Decryption Options
Compression Options
'--' (=none): file will be archived 'as is', without any folders; 'Relative': file will be archived with folder where it is located; 'Full': file will be archived with full path (but excluding drive and server names).
| ||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||
| When transferring large files with identical filenames from Source to Target(s), AnyFileBackup can ensure that a file in Target will not be replaced by a file from Source until such Source file is fully transferred to Target. This file transfer method is known as a 'safe transfer'.
This is achieved in the following way. First, the Source file is transferred to Target with a temporary name (different from that of the Target file). Secondly, when the Source file is fully transferred to Target, its filename is changed to its proper [Source] name replacing the Target file.
The main advantage of this method is full protection from accidental interruptions during file transfer process which otherwise may cause only partial transfer of files.
This method of transfer also has certain disadvantages:
| ||||||||||||||||||||||||||||||||||||
| This is the maximum incoming speed of file transfer to Target set in bytes per second. When left blank, the speed is unlimited. You can also configure outgoing speed of file transfer from Source in the Source settings. | ||||||||||||||||||||||||||||||||||||
| If enabled, a Target file that has read-only attribute will be overwritten with a Source file. If disabled, this Target file will be kept intact but this will be considered as error and common and task error handling rules will apply. | ||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||
| If enabled, Source full subfolder structure will be transferred to Target with Source files allocated to their respective subfolders. If disabled, all Source files will transferred to Target as if Source files were in one single folder; no subfolders are transferred to Target. | ||||||||||||||||||||||||||||||||||||
| If enabled, Target file will have exactly the same timestamp as its Source counterpart. If disabled, Target file will have timestamp that reflects time of its transfer to Target. | ||||||||||||||||||||||||||||||||||||
| If enabled, AnyFileBackup will calculate and compare a Source file's CRC (Cyclic Redundancy Check) (that is a file's checksum) with a Target file's CRC after a particular files has been transferred from Source to Target.
Generally, operating systems automatically check file consistency after coping that is enough in most circumstances. This option is an additional guarantee that the file from Source is identical to the file transferred to Target. We recommend to use this option only when a critical data is being backed up.
A CRC calculation of large files may be time-consuming, so we invented a special 'smart verification' that significantly speeds up this operation (though copying becomes slightly longer). AnyFileBackup uses last kilobyte of each files (from Source and from Target) to calculate and compare their CRCs. This is generally sufficient to prevent a very unlikely event when files are not identical after back up.
If CRC verification fails and files are not identical, AnyFileBackup will treat this as an error and will proceed according to the Common Error Handling Rules or Task-Specific Error Handling Rules. | ||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||
| 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 |