5. Viewing and interpreting log files

This is the summary of the job execution. Here you'll find the execution date and time, the backup duration and the overall result code. This should be the first section to look at. If the result code is 0, the backup was executed without any error. Possible result codes are:

This is the summary of all backup activities. This section holds the following entries:

This is the summary of all cleanup activities. This section will only be created if there actually was a cleanup run. This section holds the following entries:

Any directory selected for backup that cannot be accessed by Back4Sure will be denoted here. This section is only created if you have activated error logging in the logging options (chapter 3.8). Each entry consists of the full path of the inaccessible source folder and the result of the access operation as system code and plain text message.

The result code is always non-zero, as only access errors are recorded here. There are usually only two possible error codes, either code 3 (The system cannot find the path specified) or code 5 (Access is denied). Code 3 results from source folders, that were selected for backup but deleted during the backup process. You may fix this error by choosing "Check Job Consistency" from the "Extras" menu. The job file will be checked for invalid source directories, then. The system code 5 will appear, if you don't have sufficient rights to access one of the selected folders or subfolders of the current backup set. Under Windows Vista or Windows 7 e.g. not even the administrator has the right to view or read the profile folders of other users. In this case, you should restrict the job to your own profile folder and create backup jobs for all other users separately.

This section holds one entry for each failed copy attempt. It is only created if you have activated error logging in the logging options (chapter 3.8). Each entry consists of the full path of the source file, the full path of the target file, the state of the target file and herewith the reason for copying this file and finally the copy result as system code and plain text message.

In this section the result code is always non-zero as only failed copy actions are recorded here. To list all possible system codes would go beyond the scope of this manual, but the most common reason for a failed copy attempt is probably the system code 32 (The process cannot access the file because it is being used by another process). This means, another program claims exclusive access rights to the file in question and prevents other programs from reading it. In this case, close all open programs and retry the backup operation. A different solution is to exclude certain file types (e.g. *.lock) from the backup job by defining an exclude filter (chapter 3.3). This way, the possibly locked files will not be included in the backup set.

If during a cleanup run certain files cannot be deleted from the target directory, they'll be noted here. This section will only exist if error logging is activated. Each entry consists of the automatically generated path of a source file that corresponds with an existing target file, the full path of the target file, the state of the source file (e.g. source file does not exist) and herewith the reason for deleting the target file and finally the deletion result as system code and plain text message.

In this section the result code is always non-zero again as only failed actions are recorded here. A common reason for a deletion failure is represented by the system code 5 (Access denied). This error often results from a write protected target file which cannot be deleted. You can alter the cleanup options (chapter 3.5) to enforce the deletion of write protected files.

Contain the summary of the backup job execution. Following keys are available:

This is the summary of all backup activities. Following keys are available:

This is the summary of all cleanup activities. This section will only be created if there actually was a cleanup run. Following keys are available:

Any directory selected for backup that cannot be accessed by Back4Sure will be denoted here. This section is only created if you have activated error logging in the logging options. All keys belonging to one entry will receive a consecutive number, starting from zero. In the following key description, the position of this number is marked with a "X". Each entry has the following keys:

In these two sections each copy operation will represented by one entry consisting of four keys. Failed operations will appear in section [BackupErrors], successful operations in section [BackupActions]. For these sections to be included in the log file, error and / or action logging must be activated in the logging options. All keys belonging to one entry will receive a consecutive number, starting from zero. In the following key description, the position of this number is marked with a "X". Each entry has the following keys:

During a cleanup run, each file deletion will create one entry consisting of four keys. Failed operations will appear in section [CleanupErrors], successful operations in section [CleanupActions]. For these sections to be included in the log file, error and / or action logging must be activated in the logging options. All keys belonging to one entry will receive a consecutive number, starting from zero. In the following key description, the position of this number is marked with a "X". Each entry has the following keys: