Mozy Woes on Mac

Mozy has been working fine on my Mac for about 6 months (aside from the massive memory usage it requires during backup), but starting about a week ago, I can’t make Mozy finish (or even start) a backup. I’ve tried uninstalling it, removing all configs, reinstalling it, using the shipped config defaults, and I still get this error in /Library/Logs/Mozy.log:

INF (backup) Starting backup
INF (backup) Using 108.7 MB of memory
INF (backup) User ID is [snipped for paranoia's sake]
INF (backup) Checking for update
INF (backup) Connecting to [snipped for paranoia's sake]
INF (backup) Version is up-to-date (1.4.3.3)
INF (backup) Adding new history entry
INF (backup) Cleaning up temporary files
INF (backup) Loading encryption key
INF (backup) Loading machine information ...
INF (backup) Connecting to [snipped for paranoia's sake]
INF (backup) Loading configuration from the server
INF (backup) Connecting to [snipped for paranoia's sake]
INF (backup) Fetching the manifest hash from the server
INF (backup) Connecting to [snipped for paranoia's sake]
INF (backup) Server version is 1.3.0.19
INF (backup) Building backup set
ERR (backup) Churn is not running, exiting backup
INF (backup) Cleaning up, finishing
INF (backup) Updating existing history entry
INF (backup) Finished backup (Client error)
INF (backup) Backing up history
INF (backup) Using 108.9 MB of memory
INF (backup) Ending backup

Sometimes I see this as well:

ERR (churn) Failed to scan files, stopping: database is locked

What is “Churn”? What database is locked? I am running Time Machine as well. Does that matter? Any ideas out there? I know some of you used to work at Mozy. Does any of this ring familiar?

On another note, does anyone else notice that Mozy Backups take a lot of memory on Mac OS X?


(click for bigger picture)

Mozy sits this way for hours on my Mac in the rare cases that it does actually get a backup started.

Write a Reply or Comment

Your email address will not be published.