Skip navigation
This discussion is archived

Time Machine/Capsule not backing up

3434 Views 7 Replies Latest reply: Jun 6, 2012 11:10 AM by jfwells RSS
jfwells Calculating status...
Currently Being Moderated
May 22, 2012 8:41 PM

Time Machine is not backing up to my Time Capsule and I can't figure out what is wrong.  The error message just states that it did not back up and has not since April 26.  I looked through all of Pondini's troubleshooting site and have not found anything applicable.  I installed the Time Machine Buddy Widget and this is the error message that I am getting:

 

Starting standard backup

Attempting to mount network destination URL: afp://Margaret%20Wells@WellsTimeCapsule.local/WellsTimeCapsule

Mounted network destination at mountpoint: /Volumes/WellsTimeCapsule using URL: afp://Margaret%20Wells@WellsTimeCapsule.local/WellsTimeCapsule

Renaming /Volumes/WellsTimeCapsule/Margaret Wells’s iMac.sparsebundle to /Volumes/WellsTimeCapsule/MargaretWellsiMac.sparsebundle

QUICKCHECK ONLY; FILESYSTEM CLEAN

Disk image /Volumes/WellsTimeCapsule/MargaretWellsiMac.sparsebundle mounted at: /Volumes/Backup of Margaret Wells’s iMac

Backing up to: /Volumes/Backup of Margaret Wells’s iMac/Backups.backupdb

Event store UUIDs don't match for volume: Macintosh HD

Error: (-36) Applying backup protections to /Volumes/Backup of Margaret Wells’s iMac/Backups.backupdb/MargaretWellsiMac/2012-04-26-200756.inProgress/C02B2E8C-5 BDB-4D58-886F-5B848020F531

Error: (5) setxattr for key:com.apple.backupd.SnapshotStartDate path:/Volumes/Backup of Margaret Wells’s iMac/Backups.backupdb/MargaretWellsiMac/2012-04-26-200756.inProgress/C02B2E8C-5 BDB-4D58-886F-5B848020F531 size:17

Error: (5) setxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Backup of Margaret Wells’s iMac/Backups.backupdb/MargaretWellsiMac/2012-04-26-200756.inProgress/C02B2E8C-5 BDB-4D58-886F-5B848020F531 size:2

Deep event scan at path:/ reason:must scan subdirs|new event db|

Finished scan

26.77 GB required (including padding), 173.89 GB available

Copied 0 files (0 bytes) from volume Macintosh HD.

Copy stage failed with error:11

Backup failed with error: 11

Ejected Time Machine disk image.

Ejected Time Machine network volume.

 

When I looked at the AirPort Utility I noticed that the latest update occurred right after the most recent successful backup.  The version is 6.0.  My operating system is 10.7.3.  Any advice would be appreciated!

  • Kappy Level 10 Level 10 (221,190 points)
    Currently Being Moderated
    May 26, 2012 12:17 PM (in response to jfwells)

    I think the key line in the log is:

     

    Event store UUIDs don't match for volume: Macintosh HD

    Error: (-36) Applying backup protections to /Volumes/Backup of Margaret

     

    There is some sort of disconnect between the UUID of your computer and what Time Machine finds for the .sparsebundle. The -36 error is an I/O error of a pretty serious nature.

     

    I'm not an expert with Time Capsules, but I can suggest that you might want to consider just erasing the Time Capsule and starting over from scratch with your backups. I understand this is pretty extreme, but I'm not able to suggest anything less drastic.

     

    You can wait for Pondini to show up. He may have an easier solution to recommend such as repairing the sparsebundle or Time Capsule drive. We will see about alerting him to your problem.

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    May 26, 2012 3:44 PM (in response to jfwells)

    As Kappy says, error -36 is an I/O error. 

     

    The setxattr errors are also problems writing to the Time Capsule;s internal HD.

     

    Most likely, that's a problem with the TC.  How old is it, and do you have AppleCare for your Mac?

     

    You can try repairing the backups, per #A5 in Time Machine - Troubleshooting.  That will take quite a while, even when connected via Ethernet.  If that succeeds, you may be able to continue backing-up to them (but stay connected via Ethernet if at all possible for the next backup -- it will be a fairly large and lengthy one).

     

    Or, as Kappy suggests, just erase it and let Time Machine start fresh.  See #Q5 in Using Time Machine with a Time Capsule

     

    Haviing Airport Utility 6.0 isn't a problem (but you'll need to download 5.6 as noted in the #Q5 article to do the erase).

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    May 26, 2012 3:48 PM (in response to Kappy)

    Kappy wrote:

     

    I think the key line in the log is:

     

    Event store UUIDs don't match for volume: Macintosh HD

     

    There is some sort of disconnect between the UUID of your computer and what Time Machine finds for the .sparsebundle.

    Actually, that's the UUID of the File System Event Store on the Mac's HD vs. the one registered by Time Machine at the time of the previous successful backup.  When there's a conflict (because of a failed or cancelled backup, a very long time without a backup, or a large volume of changes such as with an OSX update), that's what tells Time Machine it has to do a "deep scan," comparing every directory on the Mac to the backups, to figure out what's changed and needs to be backed-up.  That takes longer than usual, of course.

     

    That's a long way of saying, it's normal in this circumstance. 

  • dldubois Calculating status...
    Currently Being Moderated
    Jun 5, 2012 8:21 PM (in response to Pondini)

    I, too, am having trouble backing up, with two different computers. I had a successful backup first thing this morning:

     

    Jun  5 07:57:21 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[10698]: Backup completed successfully.

    Jun  5 07:57:24 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[10698]: Ejected Time Machine disk image.

    Jun  5 07:57:24 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[10698]: Ejected Time Machine network volume.

     

    Then a few minutes later...

     

    Jun  5 08:14:46 Dwight-DuBoiss-MacBook-Pro [0x0-0x44a44a].backupd-helper[10777]: Not starting Time Machine backup after wake - less than 60 minutes since last backup completed.

    Jun  5 08:15:44 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[10787]: Starting standard backup

    Jun  5 08:15:44 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[10787]: Attempting to mount network destination URL: afp://Dwight%20DuBois@Time%20Capsule._afpovertcp._tcp.local/Data

    Jun  5 08:16:41 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[10787]: NAConnectToServerSync failed with error: 89 for url: afp://Dwight%20DuBois@Time%20Capsule._afpovertcp._tcp.local/Data

     

    Throughout the day the error has changed to...

     

    Jun  5 14:47:01 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11356]: Starting standard backup

    Jun  5 14:47:05 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11356]: Attempting to mount network destination URL: afp://Dwight%20DuBois@Time%20Capsule._afpovertcp._tcp.local/Data

    Jun  5 14:47:35 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11356]: NAConnectToServerSync failed with error: 64 for url: afp://Dwight%20DuBois@Time%20Capsule._afpovertcp._tcp.local/Data

    Jun  5 14:48:35 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11356]: Failed to resolve network service using name = Time Capsule type = _afpovertcp._tcp domain = local.

    Jun  5 14:48:45 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11356]: Backup failed with error: 18

    Jun  5 19:57:53 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11396]: Starting standard backup

    Jun  5 19:57:57 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11396]: Attempting to mount network destination URL: afp://Dwight%20DuBois@Time%20Capsule._afpovertcp._tcp.local/Data

    Jun  5 19:58:53 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11396]: NAConnectToServerSync failed with error: 89 for url: afp://Dwight%20DuBois@Time%20Capsule._afpovertcp._tcp.local/Data

    Jun  5 19:58:53 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11396]: Attempting to mount network destination using URL: afp://Dwight%20DuBois@Time%20Capsule._afpovertcp._tcp.local/Data

    Jun  5 19:59:49 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11396]: NAConnectToServerSync failed with error: 89 for url: afp://Dwight%20DuBois@Time%20Capsule._afpovertcp._tcp.local/Data

    Jun  5 19:59:59 Dwight-DuBoiss-MacBook-Pro com.apple.backupd[11396]: Backup failed with error: 19

     

    Help?

     

    (My other computer hasn't backed up for two days.)

  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Jun 5, 2012 8:33 PM (in response to dldubois)

    Obviously, Time Machine is having a problem connecting to your backups. 

     

    Start by re-selecting them, via Time Machine Preferences > Select Disk.

     

    If they don't appear as a destination, try repairing them, per #A5 in Time Machine - Troubleshooting.

     

    If they don't appear in the Finder, you may need to reset your Time Capsule.  See Resetting an AirPort Base Station or Time Capsule FAQ.  A "soft reset" should be enough.

     

    If nothing helps, the TC may be failing.    It's covered by a one-year warranty; but if you have Apple Care on a Mac, and purchased the TC within two years of that, the TC is covered, too.

  • dldubois Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 6, 2012 7:19 AM (in response to Pondini)

    OK, after a LOT of fooling around, the simplest thing solved my problem. (BTW, I was also having trouble with web access; about half the pages I went to wouldn't load.)

     

    I tried the fixes above. TC showed up in the finder, but connections always failed, so I couldn't do anything there. Disk Repair didn't show TC at all. I could get nowhere with any of this.

     

    Finally I shut down our modem & TC, then restarted them. All is working perfectly now. Go figure.

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.