Directory Tree Options specifies what directory structure information will be saved at the destination location for the backup. These options are only available when the backup type is of copy.
Replicate empty directories | If unchecked, then empty directories on the source are not created on the destination. If you have a source directory structure that is important, with some directories not containing any files - this item should be checked. If you are unsure, then check this item. |
Delete files no longer on source | The processing associated with this option happens at the end of the backup. If checked, any files that exist at the destination but do not exist at the source will be removed from the destination. This is usefull if the contents or structure of the location you are backing up from changes frequently. If this is the case, then this option will ensure that the destination is structured as close as possible to the source. |
Prompt if volume not loaded | If this is enabled, a check will be performed before the backup starts to ensure that the right disk/catridge is loaded on the destination device. This option make no sense whatsoever for non removable destinations (like local fixed disk drives). It should be used if you are backing up to a ZIP (tm) or LS-120 drive, and you want to make sure that the right disk is in the unit before the backup starts. |
Keep the last 'n' backup(s) | If enabled, before the backup starts, existing backups will be
reshuffled. For example, if you have entered 4 in the edit box, and the backup starts -
the following will happen:
There is no real limit to this process other than disk space. DataArmour sets the limit to 400, although if you use this at all, you will most likely set it to some value between 2 and 10. |
List of files scanned | If enabled, the complete list of files that were scanned from the source directories will be included in the log. Note: The scanning process is intelligent - and automatically excludes those files that appear to be the same on the source and destination); so do not expect a complete file list to be dumped to the log every time a backup is run. |
List of files actually backed up | This option is only of real use when performing a ZIP backup. While DataArmour tries to be intelligent regarding the files that is scans from the source directories, it is possible that the ZIP processor will differ. If checked, a listing of the files that were actually added or updated to the ZIP file will be listed here (note: Files that are removed from the zip file are recorded in a seperate list). |
Files that have been deleted from the source | If checked, a list of the files that would be removed from the destination (because the files no longer exist on the source) is added to the log. The files are only removed from the source if the delete files no longer on source option is also enabled. |
All FTP activity | This option is only available if the backup item's destination is an FTP server. If enabled, all FTP commands and their responses (appart from the password command) are logged. This log can be quite lengthy. |
This option is only available if at least one of the rules specified by the item has it's on file change option set. If enabled, and something in the specified directorie(s) changes ((file name, file size, addition or removal of directory or file, etc) then the backup is started. Often, it is not desirable for the backup to start straight away. This option adds a fixed amount (specified in the edit box) to the next execution time, so that the backup starts sometime in the future.
e.g: If this option enabled and set to 5, and you add a file to source directory that is being monitored, the backup for that source directory will run in five minutes time.
If you continually make changes ot the source directory (less than every 5 minutes) the backup will never run. In these cases, do not set the on file change option on those directories. Instead, use standard scheduling.
Directory Tree Options
These options are available when the Backup method is Copy files to
destination. These options effect how DataArmour stores the directory
structure of the source files on the destination drive.
Entire Structure will force DataArmour to backup the source file, with its directory structure, while Some structure, grouped by UNC will only back up what is necessary to keep the source file name unique on the destination.
Use this option to configure how DataArmour handles files which other applications could be writing to (This is known as "shared write access"). Note: It is acceptable for other applications to be reading files, just not writing to the files. If you do not wish DataArmour to check for open files, then you run the risk of backing up a corrupt or zero length file, or worse backing up a file that is currently being written to.
If you wish DataArmour to check for open files, you have two options:
Skip files - This is the default option and forces DataArmour to skip any open
files. Skipped files are noted in the log, if any are skipped then the backup item
completes with the status of warning. This is represented by a yellow exclamation
mark (!) in the list and a yellow stem of the DataArmour system tray icon.
Wait for file - If DataArmour detects that the file is open for shared write, rather than
simply skipping the file, it will wait for the specified period for the file to become
available. It performs a periodic check for this availability. If the time is
exceeded the file is skipped and this is noted in the log as above. The maximum wait is
120 seconds. This option is not available when the backup type is zip.