No More Mozy

They have had their chance, and now I’m done with Mozy, and switching the rest of my offsite back to Backblaze, no more reticulating splines for me.

My MacBook’s performance was abysmal, until I looked to see what was going on, and I find that mozy is consuming massive resources and not doing anything. I pull up the status only to see that mozy is doing its ever popular reticulating splines, and not doing much of anything else, so I let it run over night, and I do see some success that is has started doing its thing and I don’t think anything of it until the next day or so when I notice the amount that is being backed up, 12.6 GB. That may or may not seem like a lot to you, but considering how much I use this machine it is a lot somewhere around 25% of the user data, so I send off an email to mozy tech support, asking why this would happen, that one apparently disappeared into a blackhole,

I’m busy for the next couple of weeks, and hardly have a chance to use the MacBook, but when I do it seems to be working ok for the most part when I use the machine, but then I notice the status message that mozy has now chosen to back up about half the data on the machine by size.

I fire off another query to mozy, kind of pissed that I have not heard from them, when I see the following

So I go to the website and open a chat, I get some help in that they respond, and ask for my logs file, which I send, and Im told they’ll get back to me in a few, and when they do get back to me in a few I am told that they are still waiting on my logs, I have since removed mozy from my computer, and told them I am thinking of getting rid of mozy. Now I have been sent several emails from various people at mozy trying to “solve” my problem. I figure I’ll give them one more chance, and do a reinstall of the mozy software, do a reboot and let it rip, and after about 20 minutes of churning I get the following.

Thats the last straw…
Over the summer I had an issue on my iMac with BackBlaze, that was a bit like this one where the machine was churning and churning, 2 days and 3 or 4 emails later problem solved and Backblaze has been working like a charm since.