Topic Content

General

Unconditional Renaming of Files Transferred to Target

Conflict Resolution Rules

This option defines properties for File Transfer -- a key stage of Backup mode. During this stage files are being copied or moved from Source to Target(s) and other defined actions are performed.

File Transfer has certain sub-events (Targets and Actions) which reflect how File Transfer actually works. In brief, every sub-event within File Transfer happens to every file that is within the task scope. This may be illustrated by the following example.

Example: consider the following situation

General

This group of settings defines the basics of file transfers between Source and Target locations. Proper configuration of this settings is essential for successful backup and synchronization.

This is the way files are being transferred from Source to Target location. Three options are possible:

This is the order of priority in which files are transferred to Target. The following options are available:

Example: files created in 2005 first, then files created in 2009, and finally followed by files created in 2014.

Example: files created in 2014 first, then files created in 2009, and finally followed by files created in 2005.

Unconditional Renaming of Files Transferred to Target

This group of settings configures the rules for renaming files that are backed up to all Targets. This renaming happens when the 'Match pattern' fits the Source file's name and, consequently, in Target this file will have a different name, that matches the 'Replace pattern' settings.

This option utilizes powerful 'regular expressions'. Good explanation and examples of usage can be found at this Wikipedia page: https://en.wikipedia.org/wiki/Regular_expression#Examples

If enabled, the Unconditional Renaming will be active and apply to all files that are transferred by AnyFileBackup to all Targets (but if, and only if, the file name matches the 'Match pattern' settings; if there is no match, then no renaming will be made).

An expression (aka 'mask') that is used to define which filenames or part(s) of filenames are to be renamed when they are transferred to Targets, so in Targets these files will have new names as set by the 'Replacement pattern' rules.

An expression (aka 'mask') that is used to define a new filename for a Target file.

Conflict Resolution Rules

This group of settings defines what happens to a file in a Target location if a file with the same name is being transferred to that Target location from a Source location.

This defines what will happen to any file in Target if a file with exactly the same name is being transferred to that Target location from a Source location. The following options are available:

The following is essential when you consider using the 'Update changed parts' mode:

-- a Target file does not exist: a Source file will be transferred to Target in full;

-- a Target file is longer than a Source file: the Target file will be truncated (that means that certain changed parts will be cut out as appropriate);

-- Source files and AnyFileBackup are located on different computers: this may significantly increase file transfer time and it is recommended to use this mode only when Source files and AnyFileBackup are located on the same computer;

-- Source files are large: this may significantly increase file transfer time and it is suggested to consider other mode.

Some of these rules are not compatible with certain Targets, namely:

This option activates when the 'Rename' option is selected in the 'If target file exists' field above. The following files may be renamed:

Specify the template which will be applied to files that are to be renamed. You may use the existing templates or specify a new one. Details of macro strings can be found here.