For the most part, MozyPro is a solid, reliable remote backup software and service. Once in a while, because of a software conflict, or in our case, a system crash, the MozyPro local database file can become corrupted and prevent MozyPro from completing a backup. Here is how we fixed it. First step is to identify whether or not your problem is actually a corrupted database file. Generally for most Mozy errors, Mozy’s tech support recommends that you restart your machine, and/or install the latest Mozy client. In, our case we had already tried these steps, and had the same error. When initiating a manual backup, the backup will start, then hang on “Connecting to backup service”. The message will eventually go away, and the Mozy status will say that it is ready to backup. There won’t be any obvious error messages.

Check the mozypro.log file to see what error messages you have. Here is what we had:

18Apr2010 12:58:51 mozyprobackup.exe: Error: Failed to add to set contents (11: DB_CORRUPT[11]: database disk image is malformed)
18Apr2010 12:58:52 mozyprobackup.exe: Error: Failed to add to fs contents (11: DB_CORRUPT[11]: database disk image is malformed)
18Apr2010 12:58:52 mozyprobackup.exe: Error: Failed to load set contents (11: DB_CORRUPT[11]: out of memory)

And here is the fix from Mozy Technical Support:

1. Delete C:\Program Files\MozyPro\Data\cache.dat.
2. Restart the MozyProBackup service and start another backup.
3. Enter the MozyPro configuration, make a change and save. Then start a backup