Summary
We have found that Kaspersky Internet Security v8.0.0.506 may interfere while Backazon attempts to access files in a Backazon backup. This may result in Backazon returning an error and could result in backup jobs not being completed successfully. It may also prevent a backup from being restored.
At this time, we do not believe that this problem will result in loss of data nor do we believe that a backup will become corrupted.
Error Message
We have found the error may occur in these locations:
- In a backup log. Go to the Logs option, Open the Log Viewer, go to the List View tab, look in the Result column.
- When viewing a Crate's contents. Go to the Crates option, select a Crate, choose View Contents. As you open a folder, Backazon may respond with "Unexpected error while loading folder:
Data at the root level is invalid. Line 1, position 1."
The error may occur in other locations, but the root cause appears to be the same. When Kaspersky accesses certain types of files, such as graphics files (BMP, JPG, GIF, et al), it attempts to "clean" the file so that a virus cannot enter your computer. Backazon stores information about your files in specially formatted XML files. These XML files are named similarly to your original files, so Kaspersky intercepts these XML files and "cleans" them. Unfortunately, the cleaning process renders the file unusable and Backazon reports an error.
Work Around
To work around this problem, Kaspersky advises you to exclude your Backazon files from being scanned.
- Stop the Backazon Engine and then close Backazon.
- Open Kaspersky.
- Click on Settings.
- Click on Anti-Malware on the left.
- Click on Settings... next to
Enable Web Traffic protection.
- Click + Add new item.
- Type in the site address as
http://YOUR-CRATE-NAME.s3.amazonaws.com/* in the line and press OK.
- Press OK twice to close the
other Settings windows.
- Close the main Kaspersky window.
- Retry the operation in Backazon.
It is quite unfortunate that Kaspersky behaves in this way. We have reported the situation to their technical staff and asked that they fix their program.