Revert to Database Backup..
 

Yesterday my macbook pro crashed. Today I am trying to restore my OF backup (via mozy) on my other laptop by using the revert to database backup option. But I consistently get the following 'Unable to read document.' error message with all my backups:[INDENT]Unrecognizable transaction file name '166009EC-E05A-4407-A744-B02C5B356FCF05F16B4C-1F0C-4D3A-90B4-F859E647C908.xml'.[/INDENT]
Does anybody have any idea how to fix this, or what the cause might be? Could it have anything to do with storing the files on a system that sees the files as folders and maybe fiddles with the internals of it?

What are you backing up with Mozy? The package in Application Support or the database backups generated by OF. The Revert to Database Backup menu item expects a package created using the Backup Database option, or automatically generated by the Backup preference in OmniFocus.

OF generates its backups in ~/Documents/OmniFocus Backups. Do you have copies of those files? Have you tried opening one of them? (All my backup packages for OF contain a single file named "root=....xml".)

It are the ones that are automatically generated by the Backup preference in OmniFocus. And they also contain 1 xml file in the format you explained.

The only difference I see is that the format of the xml file in my local backups has a forward slash in the name, e.g.[INDENT]root=79FC2B55-EF4D-4FE4-B679-D5A9B470BB9F/8C7F963A-56FE-4AA1-999A-3DE656027843.xml[/INDENT]whereas the name of the xml file in the remote backups don't have the slash, e.g. [INDENT]root=166009EC-E05A-4407-A744-B02C5B356FCF5B376110-2E51-4B99-9521-CECC67987E46.xml[/INDENT]
Maybe it was converted during the backup? Anyway, the local backups restore without problems, the remote ones don't work.
Manually adding the forward slash doesn't seem to help either.. However, when looking at the same files in terminal, it was a colon ':' instead of a slash '/'. Adding a colon at the correct position seemed to do the trick.

So apparently the ':' in the name of the internal xml file is lost during backup via Mozy. Putting it back (after the twelfth character of the longest string) fixes it.