02-04-2009 08:59 AM
02-10-2009 11:54 AM
02-11-2009 08:03 AM
02-11-2009 08:57 AM
That document says error 8211 is from system files/files in use/hidden files, etc. If that were the problem in our case then that error would have shown from day one not consistently on day 11. The same folders and files are being backed up every night at the same time when there is no other activity on the computer. And this is actually the message you get on those type of files:
"Not Supported/File skipped (backup of operating system files and folders ( those that have both system and hidden attributes) is not supported)" or "Open or locked file skipped" not internal error 8211.
02-11-2009 10:16 AM - edited 02-11-2009 10:18 AM
AlanM: When I go into Level1, Level2, Level3, Level4, Level5, Level6, Level7, Level8, Level9, Level10 the QuickBooks file is backed in each folder. Once it reaches the 11th backup the Quickbooks file doesn't backup giving a Internal Error 8211.
If I delete ANY one of the Levels the backup goes through fine. Once there is 10 levels again the 11th backup will fail. If I delete 3 different levels the backup will run until it reaches 10 levels then the next backup will fail.
That documents pretty much says we can't backup certain files but we've been backing them up 10x times already why when it reaches 10 Levels in the backup, the next backup fails and doesn't backup the file saying Internal Error 8211? I believe this to be a bug in the software.
02-12-2009 06:27 AM
Well, I can't say I've never seen bugs in this software...
I'd encourage you to try to restore one of those files from a previous version that seemed to back up correctly, and see if it did indeed go through into the backup correctly.
I seem to recall that for certain programs, you need to perform an explicit and special export action to get the data into a file that the OneTouch software can backup correctly.
02-19-2009 10:44 PM
The knowledge base entry gives the clue, I think, when it says it doesn't support encrypted/compressed folders.
What I have found is that newly created files of all types are fine. But if you change a file of a type that it does not understand, you will get an 8211 error and the file will not be backed up.
In my case, I have an app that creates a data file every day in a format that's indistinguishable from binary data. When new, these are fine - but if I ever go back and change one, boom. The same thing happens with compiled executables. The actual backed-up file seems to be fine, as you'd expect since it's just a collection of bytes.
The solution if this is a rare case, is to change the name or delete the backed up version. If it's more common, it's time to throw out the Maxtor software and take advantage of the configurable one-touch button action to run a real backup application. Like SyncToy .
Why the developers didn't just back up the file anyway, move the old versions down one in the history tree, and move on... I don't know. It doesn't seem to do anything that would justify trying to understand my file contents - back it up already!
03-24-2009 09:47 AM
04-02-2009 02:39 AM
in general, the file history seems to work fine and deletes the oldest file version from the backup.
i can confirm the problem, but it seems to be in combination with the "compress" feature from winxp in my case. some compressed files are saved over and over again, although they were not changed/modified. other compressed files do not seem to be saved every time and therefore do not create the "internal error 8211". really strange...