Comments on: Mac 1.4.3 Update

By: Doug

Doug — Sun, 13 Sep 2009 18:04:37 +0000

Well, the 1.4.3 update completely hosed Mozy on my machine – I’ve reinstalled, removed and readded my machine from the server, etc and no solution. I have sent several support requests including crash dumps and client logs with no response, and no status updates on if/when the problem will be fixed. I’ve been using Mozy for several years with no issues, but if this is the way you handle support, I’ll go somewhere else.

By: Mikey

Mikey — Tue, 08 Sep 2009 01:41:17 +0000

Please release 64bit mac version for us snow leopard users.

By: Arthur

Arthur — Thu, 03 Sep 2009 16:31:08 +0000

I agree on the linux question. Your competitors have had a client and/or at least an rsync address which works perfect, so to swich to something with less functionality just does not make sense.

Their suggestion, get a server license, setup samba, share your linux folder, backup from a windows box. Not a good practice I would say!

By: dusponda

dusponda — Wed, 02 Sep 2009 18:13:00 +0000

Where is the linux version!? It’s a great service, but I will need to stop using it, because I’m moving to Linux.

By: ed

ed — Wed, 19 Aug 2009 02:09:30 +0000

it would have been nice if you’d informed your “customer service” reps about the issue so that at least people (like me) who contacted you about the issue would have had the necessary info to let me know what was going on.

also, was the fix for network drives in 1.4.3 to just disallow backing up from them? i’m no longer able to select any of my network drives for backup with the latest version?

By: David

David — Tue, 18 Aug 2009 17:10:22 +0000

I never would have found this update if I hadn’t stumbled across the phrase “Mozy fix” in the Macintouch headlines.
I never would have thought to follow you on Twitter, read your blog, or look in the Apple forums – how did you think it possible that people having this problem – like me – would ever think to connect Time Machine and Mozy as a broken interaction when it had never been the case before?

Send out the mass email next time.

By: Lake Perriguey

Lake Perriguey — Tue, 18 Aug 2009 01:04:15 +0000

What is the current status? While my Time Capsule is backing up again, I have lost all my logs on Mozy and Mozy is not backing up.

By: devin

devin — Mon, 17 Aug 2009 20:09:17 +0000

You bring up a valid point. I understand how annoying and confusing this must have been for our customers who were affected.

Of our Mac customers, only a portion of them were using Time Machine with Time Capsule. The rest use Time Machine with another locally connected external drive. We were concerned that we would be pulling a unnecessary fire alarm for the majority of our customers if we sent an e-mail since most of them were not affected by the issue and our database doesn’t tell us who is using Time Capsule and who isn’t.

That said, we wanted to be responsive and helpful. So we opted to respond in the Apple Forum, on Twitter and on our own blog rather than blasting all our customers with an e-mail. The feedback here from each of you, though, is helpful. If something likes this happens again, we may opt to send the e-mail rather than responding only in the forums and on twitter.

Devin Knighton
devin@mozy.com
http://www.mozy.com

By: mike

mike — Sat, 15 Aug 2009 04:33:28 +0000

As Mozy users, we tore our hair and wasted countless hours out trying to fix Time Machine before finally stumbling over this Mozy fix. Why wouldn’t Mozy blast an email to its users for something this important? Incredible.

By: Jackie

Jackie — Sat, 15 Aug 2009 04:15:59 +0000

Like countless other Mozy customers using Time Machine/Time Capsule, I have spent the past several days trying to trouble-shoot this problem. I cannot fathom why Mozy made NO effort to advise customers of the problem as soon as it was uncovered. Like many others, I’ve lost all the data on my Time Capsule after being forced to reformat the drive — when all the other trouble-shooting was unsuccessful.

How do you justify the fact that you can email us regularly about subscription fees and the like, but you can’t notify your customers when your programming mistakes put their data and backup systems in jeopardy?