Skip navigation
This discussion is archived

Time Capsule/ Endless Preparing - no backup

29523 Views 210 Replies Latest reply: Sep 25, 2009 7:38 PM by Craig1259 RSS
  • Kinjapan Calculating status...
    Currently Being Moderated
    Aug 9, 2009 2:57 PM (in response to mpdharley)
    There is a big risk to make you laugh on me: a) I don't know what you mean with "MOZY" - and b) I am quite sure that I do not run any "MOZY"-Software - however: still having same problem since 10.5.8 on my Macbook Pro. Therefore I still think we should blame Apple for this....
    ??
    Anyone out there who can explain the meaning of "MOZY" to me??
    Best regards, K
    Macbook Pro, Mac OS X (10.5.5)
  • William Luckie1 Level 1 Level 1 (55 points)
    Currently Being Moderated
    Aug 9, 2009 3:01 PM (in response to JohanDA)
    Mozy is an on-line backup service.
    iMac Core 2 Duo, iPhone, Mac OS X (10.5.8)
  • leahk Calculating status...
    Currently Being Moderated
    Aug 9, 2009 3:04 PM (in response to JohanDA)
    Grrr! Mozy 1.4 - There must be a lesson here - don't upgrade to the bleeding edge just cause it's there.

    Time Capsule and Mozy have been working flawlessly for months - Mozy wasn't even telling me to upgrade - I just spotted there was a new version and installed it. I have wasted the whole weekend on this problem and lost 6 months worth of Time Machine backups as a result.

    Still, I'm happy to report that my Time Capsule isn't faulty as I had feared and for the first time in 3 days, I have a working Time Machine backup. Just a pity that I can't use Time Machine to roll back to the old version of Mozy!

    Thanks to whoever spotted the connection.
    Macbook Pro/Mac Mini G4, Mac OS X (10.5.2), AEBS X 2
  • Snipes01 Calculating status...
    Currently Being Moderated
    Aug 9, 2009 4:49 PM (in response to JohanDA)
    Mozy 1.4 did me in as well. Thanks for finding this. Wasted enough time debugging it without finding a solution on my own. It does stink that the old sparse bundle is corrupt, so I had to start with a new full backup.
    Mac OS X (10.4.8)
  • lagreca Level 1 Level 1 (0 points)
    Currently Being Moderated
    Aug 9, 2009 6:02 PM (in response to JohanDA)
    Same thing here. Mozy stopped time machine with the same errors. I stumbled upon this thread, and once I uninstalled Mozy, backups started working.

    I'm kind of disgusted by both Apple and Mozy for this one. Time Machine should not be so vulnerable to 3rd party software. Mozy should do a little QA before releasing their products.
    Macbook 13", Mac OS X (10.5.8)
  • BlaineHargrove Calculating status...
    Currently Being Moderated
    Aug 9, 2009 7:13 PM (in response to lagreca)
    Anyone heard anything back from Mozy support?
    Macbook Pro, Mac OS X (10.5.8)
  • Eric Tiffany Calculating status...
    Currently Being Moderated
    Aug 9, 2009 8:12 PM (in response to BlaineHargrove)
    BlaineHargrove wrote:
    Anyone heard anything back from Mozy support?


    No, and I wouldn't hold my breath. I see that there is a new version of Mozy 1.4.1 available, but I'm not going to install it to do more unpaid beta-testing for Mozy.
    MBP 15" 2.33GHz 3G RAM, Mac OS X (10.4.8)
  • janberlin_ Calculating status...
    Currently Being Moderated
    Aug 10, 2009 1:03 AM (in response to Eric Tiffany)
    I had a reply from technical support this morning. He requested for the mozy.log. The log says, that the time machine was skipped the time the problems started.

    the update 10.5.8. and the 1.4.0.6 from mozy came morning august, 6. So hard to say, which update can be blamed for the mess....

    I sent the log, the "Operation not permitted" alert from the console to mozy support..and this thread.... lets see....

    PS: Have tested idrive and there are no probs at all so far....

    Cheers
    Macbook 13" DualCore, Mac OS X (10.5.8)
  • Robert Slifka Calculating status...
    Currently Being Moderated
    Aug 10, 2009 1:04 AM (in response to JohanDA)
    Yes! *It was Mozy Home!* THANK YOU!

    I spent ALL WEEKEND debugging this, pulling my hair out thinking Spotlight + Time Machine = broken in 10.5.8.

    Well I'm not thrilled it took so long for me to stumble across this thread, although I'm glad I did

    Thanks everyone!
    Mac OS X (10.5.8)
  • leahk Level 1 Level 1 (0 points)
    Currently Being Moderated
    Aug 10, 2009 1:26 AM (in response to janberlin_)
    I installed 10.5.8 on 5th August and Mozy 1.4 on 6th August
    I first noticed the problem on the morning of 7th August

    Whilst something in 10.5.8 might have broken 1.4 - there is no doubt that removing Mozy fixed the problem for me.

    Is there anyone here that saw the problem with a combination of 10.5.7 and 1.4?
    Macbook Pro/Mac Mini, Mac OS X (10.5.8), AEBS, Time capsule
  • Neepawa Calculating status...
    Currently Being Moderated
    Aug 10, 2009 3:41 AM (in response to BlaineHargrove)
    I got an email back from them this morning asking for the Mozy log. I sent it to them, along with the System log showing the Spotlight errors. Hopefully that can help them to address the problem.
    MacBook Pro, Mac OS X (10.5.8)
  • leahk Level 1 Level 1 (0 points)
    Currently Being Moderated
    Aug 10, 2009 4:34 AM (in response to leahk)
    I've checked my logs - There was over 24 hours between the two upgrades
    Aug 5 21:58:05 Leopard 10.5.8 Upgrade
    Aug 6 23:19:23 Mozy 1.4.0.6 Upgrade


    So from 21:58 on the 5th August to 23:19 on the 6th August I was running Mozy 1.3.2.4 with OS X 10.5.8 - during that time and previously I would see these three lines in the system log at hourly intervals:

    Aug 6 22:06:39 wsprosys02 /System/Library/CoreServices/backupd[9795]: Mounted network destination using URL: afp://Kevin%20Leah@bsprosys01.local/TimeCapsule
    Aug 6 22:06:39 wsprosys02 /System/Library/CoreServices/backupd[9795]: Backup destination mounted at path: /Volumes/TimeCapsule
    Aug 6 22:06:45 wsprosys02 /System/Library/CoreServices/backupd[9795]: Disk image /Volumes/TimeCapsule/wsprosys02_001ec21e0e43.sparsebundle mounted at: /Volumes/Backup of wsprosys02


    They would seem to demonstrate normal operation of Time Machine.

    After the Mozy upgrade I would see these lines in the system log:
    Aug 6 23:20:35 wsprosys02 Mozy[10344]: INF (main) Examining TimeCapsule
    Aug 6 23:20:35 wsprosys02 Mozy[10344]: INF (main) /Volumes/TimeCapsule is not in mounted volumes: (\n "/",\n "/private/tmp/584/C",\n "/Volumes/Data",\n "/Volumes/Store",\n "/Volumes/kevinleah",\n "/Volumes/Mozy 1.4.0"\n)

    and
    Aug 7 02:06:37 wsprosys02 kernel[0]: AFP_VFS afpfs_mount: /Volumes/TimeCapsule-1, pid 11352
    Aug 7 02:06:37 wsprosys02 /System/Library/CoreServices/backupd[10989]: Mounted network destination using URL: afp://Kevin%20Leah@bsprosys01.local/TimeCapsule
    Aug 7 02:06:37 wsprosys02 /System/Library/CoreServices/backupd[10989]: Backup destination mounted at path: /Volumes/TimeCapsule-1
    Aug 7 02:08:40 wsprosys02 /System/Library/CoreServices/backupd[10989]: Failed to mount disk image /Volumes/TimeCapsule-1/wsprosys02_001ec21e0e43.sparsebundle (DIHLDiskImageAttach returned: 60)
    Aug 7 02:08:50 wsprosys02 /System/Library/CoreServices/backupd[10989]: Failed to eject volume /Volumes/TimeCapsule-1 (FSVolumeRefNum: -171; status: -47; dissenting pid: 0)
    Aug 7 02:09:50 wsprosys02 /System/Library/CoreServices/backupd[10989]: Backup destination alias resolved to path: /Volumes/TimeCapsule-1


    After that the log is jam packed with TM errors.

    One of the many tests I tried during the weekend to solve the problem, included mounting the new sparse image that Time Machine was creating before it got stuck in the Preparing state. I would first set the TimeMachine disk to "none" in the preference pane. Interestingly, although I could mount and browse these images I could not unmount them as finder insisted they were in use by another process. (and that process was not Spotlight).

    Also since fixing the problem I have tried to re-install an earlier version of Mozy - but this was not to be - I guess I have to wait for a new version that fixes the issue.
    Macbook Pro/Mac Mini, Mac OS X (10.5.8), AEBS, Time capsule
  • mpdharley Level 1 Level 1 (25 points)
    Currently Being Moderated
    Aug 10, 2009 4:43 AM (in response to leahk)
    Also since fixing the problem I have tried to re-install an earlier version of Mozy - but this was not to be - I guess I have to wait for a new version that fixes the issue.


    If the problem you had with the earlier version of Mozy was that it would stop, then crash immediately, only to re-start, check my earlier message on this thread (page 3). The fix is to delete the state.db file.

    Mike
    MacBook Pro, Mac OS X (10.5.8), Saw the light (thanks Vista!) and converted to MAC in 12/07!
  • Moche Calculating status...
    Currently Being Moderated
    Aug 10, 2009 7:42 AM (in response to Eric Tiffany)
    I tried Mozy 1.4.1. It does not fix the problem. TimeMachine still fails. At this point I have one computer remaining to convert to Jungle Disk. It costs more than Mozy but I have no problems with it.
    PowerBook G4, Mac Mini G4, Mac Mini Intel, MacBook Pro, Mac OS X (10.5.8)
  • John Vestal1 Level 1 Level 1 (30 points)
    Currently Being Moderated
    Aug 10, 2009 8:49 AM (in response to Moche)
    Everyone, I am one of the people who noticed the Mozy connection. Just chatted with Mozy and they recommend a clean install of Mozy. I am skeptical but I am trying it. I will let you all know what happens.

    John

    Message was edited by: John Vestal1
    Mac OS X (10.5.8)
1 2 3 4 5 6 ... 15 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.