Skip to Content

Mozy fixes issue that affected Time Machine / Time Capsule users

by Steven Sande Aug 17th 2009 at 11:30AM

Users of the MozyHome and MozyPro online backup services who also use Apple's Time Machine and a Time Capsule for onsite backups were dismayed to find last week that their Time Machine backups were not working. A bug in version 1.4.1 of the Mozy software caused Time Machine backups to Time Capsules and other network drives to pause, and then freeze up.

A user quoted on the Computerworld website last week noted that Time Machine would no longer mount his MacBook Pro's sparse bundle file while running Mozy offsite backups, and that he had to wipe the Time Machine backup in order to get the Time Machine / Time Capsule combination working again. The problem did not affect Mozy users who were backing up to a locally attached hard drive. Part of the issue was that Mozy was attempting to back up the large Time Machine sparse bundle files.

Engineers at Mozy's parent company, Decho, worked with Apple to gain resolution to the issue, and a fix was made available for download last Friday as version 1.4.3 of the Mac software for MozyHome and MozyPro.

[via Macworld and Computerworld]

View Tags

Related Stories

Categories

Odds and ends Bugs/Recalls

Users of the MozyHome and MozyPro online backup services who also use Apple's Time Machine and a Time Capsule for onsite backups were...
 

Add a Comment

Sign in »
*0 / 3000 Character Maximum

10 Comments

Filter by:
Michael

Count me among the people who until recently loved mozy. After having my time machine backups destroyed, and then my mozy backups corrupted by having all my mozy local settings get destroyed, i've had enough of this crap.

Funny enough, I actually find backing up my vista machine way easier.
Vista image to an external drive, then scheduled xcopy's to a NAS. simple and effective.

August 18 2009 at 1:18 PM Report abuse rate up rate down Reply
Jonathan Payne

I, too, lost all my time machine backups when this happened. I then worked with their terrible (but very polite) support and still they never told me that 1.4.3 had been released and fixed this particular problem: that I had to find out for myself.

I downloaded it, installed it, was able to create time machine backups again over the network (so it seems like they really had fixed things), ran them for a couple of days, but woke up this morning to find both of them corrupted and failed in the same way as before. The one difference: I had a long, overnight Mozy backup running this time.

I agree that Mozy is crap. It cannot figure out how to use my full upstream bandwidth. It pauses and restarts constantly and pegs my CPUs when it starts a backup. iDrive uses rsync, so it's the bee's knees. As soon as they fix their memory footprint issues I am switch away from Mozy.

August 18 2009 at 4:03 AM Report abuse rate up rate down Reply
Matt

Thank you again, TUAW! I've been having this issue and I never would have guessed that Mozy was the culprit. For everything I like about having software update itself, it can also cause so many headaches.

August 17 2009 at 1:30 PM Report abuse rate up rate down Reply
Mark Suman

This bug existed in 1.4 as well. All users who use Time Capsule should upgrade to 1.4.3.

August 17 2009 at 12:58 PM Report abuse rate up rate down Reply
Pete

I installed the update and still couldn't get TM to work. I ended up erasing the drive and I'm now at hour 20 of my initial TM backup :(

August 17 2009 at 12:53 PM Report abuse rate up rate down Reply
starq

Mozy is crap.

Total. Complete. Crap.

They totally screwed up my Mac and couldn't care less.

DO NOT TRY OR BUY. YOU'LL BE VERY SORRY.

August 17 2009 at 12:13 PM Report abuse rate up rate down Reply
starq

Mozy is crap.

Total. Complete. Crap.

They totally screwed up my Mac and couldn't care less.

DO NOT TRY OR BUY. YOU'LL BE VERY SORRY.

August 17 2009 at 12:07 PM Report abuse rate up rate down Reply
1 reply to starq's comment
Drew Scott

Works fine for me ... couldn't be happier :)

August 17 2009 at 12:11 PM Report abuse rate up rate down Reply
Ryan Sandberg

Oi! I've been wondering why TM hasn't been able to back up! x_x Now I know why.

August 17 2009 at 11:57 AM Report abuse rate up rate down Reply
1 reply to Ryan Sandberg's comment
Ryan Sandberg

... Strike that. I missed the part about it not affecting local drives! That's what I had, and it still had the issue. Now it's gone. Sure it didn't affect local ones too? x_x

August 17 2009 at 11:58 AM Report abuse rate up rate down Reply
Buy an ad here

Hot Apps on TUAW

Tweets

© 2012 AOL Inc. All Rights Reserved.