Skip navigation

mountain lion breaks time machine

44048 Views 118 Replies Latest reply: Dec 5, 2013 6:51 PM by xser RSS
  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Oct 19, 2012 11:12 AM (in response to rhjph)

    Sorry, I can't help with SuperDuper.  I use CarbonCopyCloner (downloaded SD a couple of times, but never got around to testing it).

     

    Most likely, you need two partitions on the destination.  I don't think you'd have to do that with CCC, but it would be advised. 

     

    CCC gives you this window where you can select what you want to do, as below, but I'd still use separate partitions, especially if one is an OSX partition, so things from the two source drives/partitions don't get mixed:

     

    Screen Shot 2012-10-19 at 2.10.29 PM.png

  • esaitch Calculating status...
    Currently Being Moderated
    Oct 19, 2012 6:08 PM (in response to splurben)

    10.8.2 has broken my Time Machine via WiFi abilities.

     

    I have the following setup for Time Machine:

     

    1) External Hard Drive (2TB Seagate, partitioned into 4 drives - 3 TMs  and 1 'general' to store music /movies /etc) plugged into MacMini (2009, 10.8.2)

    2) MacMini cabled to my Wireless Router

    3) MBP (Sept 2012, 10.8.2) connects to MacMini through wifi to access the drive for Time Machine.

     

    This worked GREAT

     

    Until...

    I ran the upgrade for 10.8.2  Now, Time Machine on MBP won't recognize the drives on the MacMini, even when I mount them manually. 

     

    I get an Error 45 currently (though sometimes I get Error 1).  What's odd is:  when TM is "Looking for backup disk", I can see it create Laptop.tmp.sparsebundle on the external drive that's connected to the mini, so it's TRYING to do this.  But has been failing every time since installing 10.8.2

     

    I have tried doing the "network mapping" option, but that hasn't helped either. I've tried connecting via afp, which fails.  When I mount the MacMini I can see all the drives and can even access files on the drives no problem.  It's only TM that's not working.

     

    I had this working fine under 10.8.1, so it's frustrating that 10.8.2 borked it.

     

    Can anyone help?

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Oct 19, 2012 6:17 PM (in response to esaitch)

    esaitch wrote:

    . . .

    What's odd is:  when TM is "Looking for backup disk", I can see it create Laptop.tmp.sparsebundle on the external drive that's connected to the mini, so it's TRYING to do this.

    It's trying to make a new sparse bundle, which means it doesn't recognize the old one as valid for that Mac.

     

    Turn Time Machine OFF, and make sure no backup is running (or attempting to run).  That can be hard to tell on Mountain Lion, since the menubar icon doesn't spin while it's trying to get started, so check the Preferences panel.  If you have trouble stopping it, see #D6 in Time Machine - Troubleshooting.

     

    Then, via the Finder (on either Mac), delete the new "tmp" sparse bundle. 

     

    Then Repair the backups, per #A5 in the above link.  That may take a while.  Assuming that says it's ok, do a "full reset" per #A4 in the same link, and try backing-up again.

  • rhjph Calculating status...
    Currently Being Moderated
    Oct 20, 2012 11:07 AM (in response to Pondini)

    Hi Pondini. All my data is now backed up on the new drive and tucked away in the fire-safe so, so I have a 2TB eSATA drive to play with to try to get TM up and running again. What course of action would you now recommend?

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Oct 20, 2012 11:22 AM (in response to rhjph)

    Great!

     

    I guess, format the drive (just to be extra sure, you might even want to zero it out) and set up Time Machine to back up the same stuff it was backing-up to your "Horsa" drive that did such odd things. 

     

    The first backup will be a full one, of course, probably with lots of those bogus Error (256) messages.

     

    Assuming it completes normally, run another and see if it does a quick incremental properly with little fuss.

  • rhjph Level 1 Level 1 (15 points)
    Currently Being Moderated
    Oct 20, 2012 2:54 PM (in response to Pondini)

    Well touch wood, it seems to be working OK. It did the full 650 GB back-up and has now done a subsequent incremental of a few hundred KB. Apart from the semi-colon parsing  and the disabled ownership issues (as before) the Buddy didn't report anything unusual and TM seems to be working normally. Now we know it works with an eSATA drive I can look at the USB3 problem (and also why my HP 2015 printer keeps locking up and failing to print since 10.8.2). Very many thanks again.  BTW Carbon Copy Clone seems to allow a second volume to be backed-up as a protected sub-folder of the main volume back-up, according to their FAQ.

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Oct 20, 2012 3:20 PM (in response to rhjph)

    rhjph wrote:

    . . .

    Apart from the semi-colon parsing 

    This one?: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.

     

    If so, it's an internal problem with a .plist file somewhere, probably one that's no longer in use.  Time Machine finds it, but it isn't a problem.

     

    and the disabled ownership issues

    You should have seen that on the first, full backup only.   If you saw it on the incremental, something is wrong.

     

     

    the Buddy didn't report anything unusual and TM seems to be working normally.

    Great!    

     

    I'd be inclined to do a restart, maybe move a folder or two around, etc., and run a couple more incrementals, etc., just to be sure.

     

    Then erase it and change the exclusions to do the "other" backup. 

     

    BTW Carbon Copy Clone seems to allow a second volume to be backed-up as a protected sub-folder of the main volume back-up, according to their FAQ.

    Ah, yes, I see that.  You'd have to be rather careful, though -- if you ever want to erase and start over, you'd erase the backups of both volumes.  Worse, if your OSX volume dies or gets corrupted, you'd have to remember to exclude the other drive's subfolder when you clone back to the new or erased drive.

     

    One partition per volume being backed-up sounds cleaner and safer to me. 

     

    Keep us posted on your progress and findings.

  • esaitch Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 21, 2012 8:30 AM (in response to Pondini)

    I tried all of this, it didn't help.  Mostly because there is no "sparsebundle" when I plug the drive in.  It only appears as Backups.backupdb (oddly the same is true on the Mini and the Mini's TM - which IS directly plugged in).  I even tried reformatting the laptop TM drive and starting over.  But everytime when the backup is done, it doesn't appear as a sparsebundle.

     

    Random: but, when I plug the drive into the mini, I can access the Backups.backupdb file from my MBP, but when I try to do anything in disk utility from my MBP on that drive, there's no drive listed.  Disk Utility can't see any drive I have plugged into the Mini.

     

    I had all this working before the 10.8.2 update, what the heck did Apple do?  And how do I fix it?  It doesn't make sense to not be able to do this from one Apple product to another. I did notice that 10.8.2 did turn off AFP sharing, I turned that back on, but still didn't help.

     

    I'm so frustrated now. I had called Apple Support last week, but now, this seems to be more than just TM, I'm going to call them again.  I'll post any results.

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Oct 21, 2012 8:45 AM (in response to esaitch)

    esaitch wrote:

     

    I tried all of this, it didn't help.  Mostly because there is no "sparsebundle" when I plug the drive in.  It only appears as Backups.backupdb (oddly the same is true on the Mini and the Mini's TM - which IS directly plugged in).

    Yes, when backups are made locally, the Backups.backupdb folder is at the top level of the drive/partition;  but when they're done over a network, that folder is in a sparse bundle disk image.

     

    Disk Utility can't see any drive I have plugged into the Mini.

    Also correct.  Disk Utility only sees local drives.  It can, however, see and repair a sparse bundle on a network, if it's mounted on the Mac, per #A5 in Time Machine - Troubleshooting.

     

    You can delete a sparse bundle over your network via the Finder, but that takes quite a while.  Much faster to erase the drive/partiton via Disk Utility on the Mac it's directly connected to.

  • esaitch Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 21, 2012 10:08 AM (in response to Pondini)

    While I was on hold with Apple Support, I was bored, so I ran disk utilities on every disk plugged into the Mini (even the ones that weren't causing me issues) and now TM is running over the WiFi from MBP to the TM on the Mini.  Oddly, no errors were found on the Laptop TM, but some were found on the Mini TM since the Mini TM never caused me problems, I didn't think to run disk repair on it as well - until I was bored.

     

    A suggestion to add to your 'helps" would be: If Disk Repair on the TM partition doesn't help correct your problems, run disk repair on all the partitions for the drive where TM is located, not just the one giving you problems.

     

    Right now, I'm at estimated 20 hours to go for the backup to finish via wifi - for whatever reason, it started a new backup, annoying and time consuming, but at least it's working so far.

     

    Thanks again for your help!

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Oct 21, 2012 10:46 AM (in response to esaitch)

    esaitch wrote:

    . . .

    Right now, I'm at estimated 20 hours to go for the backup to finish via wifi - for whatever reason, it started a new backup, annoying and time consuming, but at least it's working so far.

    Yes, since it stores them differently, when you connect a drive with a Backups.backupdb folder at the top level to a network, Time Machine will ignore that, create a sparse bundle, and start a new backup to it.

     

    Oddly, if you do it the other way around (connect a drive with a sparse bundle directly and run a backup), it will do an incremental backup to the sparse bundle.  But when you Enter Time Machine, it won't see the backups in the sparse bundle unless you manually mount it first. 

  • rhjph Level 1 Level 1 (15 points)
    Currently Being Moderated
    Oct 21, 2012 2:22 PM (in response to Pondini)

    Well having succeeded with the eSATA disc I then erased the USB3 2 TB disc ("Hengist") and backed up the 1.6TB of video files. This proceeded normally. However  the latest subsequent back-up attempts has failed ("Unable to complete back-up. An error occurred creating the back-up folder"), although there were apparently two back-ups subsequent to the initial one, that succeeded. Here is the Buddy message:

     

    Starting manual backup

    Backup failed with error: 19

    Starting manual backup

    Backing up to: /Volumes/Hengist TM HD and Video/Backups.backupdb

    Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Hengist TM HD and Video/Backups.backupdb/Richard’s Mac Pro size:37

    Backup failed with error: 2

     

    Any ideas? I notice that the error message on the screen refers to the name of the drive before I corrected a spelling mistake in it. The name of the disk in TM Preferences, Finder and in the Buddy all match however.

     

    Thanks

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Oct 21, 2012 2:52 PM (in response to rhjph)

    rhjph wrote:

    . . .

    An error occurred creating the back-up folder"

     

    Ordinarily, that message indicates a directory problem on the TM drive.  Try Repairing it.

     

     

    Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Hengist TM HDand Video/Backups.backupdb/Richard’s Mac Pro size:37

    . . .

    I notice that the error message on the screen refers to the name of the drive before I corrected a spelling mistake in it. The name of the disk in TM Preferences, Finder and in the Buddy all match however.

     

     

    What was the original name?  Any odd characters?  In some circumstances, on prior versions of OSX, TM used to choke on volume names containing slashes (an illegal character in a volume name, but the Finder would let you use it).  That's supposed to be fixed in 10.8, but a similar problem might exist.

     

    In addition, it shows some odd characters for the Computer name of your Mac:  Richard‚Äôs Mac Pro

    Make sure the name in System Preferences > Sharing is correct, without special characters, etc. See #C9 in Time Machine - Troubleshooting.


  • rhjph Level 1 Level 1 (15 points)
    Currently Being Moderated
    Oct 23, 2012 10:32 AM (in response to Pondini)

    The only change of the name (in Get Info) was to change a mistyped Y to a T.  The name of my machine has not changed in two years and was working fine before. I find that if I restart then I can back up OK. But subsequent attempts to back up after the first, on the same boot session, will fail.  I think the problem may be related to the fact that I selected the 'alternate back-ups' option, and it is now, for the second back-up,  trying to back up to the drive with the old name. How can I revert to a single back-up mode, or otherwise correct the system to back-up to the other (real) drive?

     

    Thanks again Pondini.

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Oct 23, 2012 10:40 AM (in response to rhjph)

    rhjph wrote:

    . . .

    I think the problem may be related to the fact that I selected the 'alternate back-ups' option, and it is now, for the second back-up,  trying to back up to the drive with the old name. How can I revert to a single back-up mode, or otherwise correct the system to back-up to the other (real) drive?

     

    Right-click the icon for the drive in question on the Preferences window;  that will allow you to remove it from the list of destinations: 

     

    7 Remove backup disk.jpg

     

    Then click the Select Disk button and reselect it.

1 ... 4 5 6 7 8 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (4)

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.