Time Machine fails when trying to backup

I have a macbook running 10.5.8.  I am trying to use time machine with my iomega external hard drive but I keep getting an error that the backup failed.  I have been successful with backups in the past with this same hard drive.  Any ideas what's going on

unfortunately there is no fix for this and there never will be
unless you sell both boxes and get a Time Capsule
in the meantime you need to mount the drive you are backing up to
select it as your backup drive in time machine then unmount it (drag to trash can)
and let time machine mount it
of course once it's mounted your next scheduled backup will also fail
so unmount it every time or turn off time machine and do backups every once in while

Similar Messages

  • Time Machine Fails When Trying to Backup Certain Files

    Time Machine is having problems with some files I have copied from a Windows computer. I am a web developer and I moved my client files from a Windows PC to my iMac. Most of the files backup properly but some don't. When Time Machine tries to backup those files, it fails.
    I downloaded Time Machine Buddy and it has helped me identify files that can't be backed up. However, the only solution that works is to delete the files. *Since these are client files, that is not an acceptable solution.*
    When I look at "Get Info", there are several listings for admin, system, staff, owner, and everyone. Each list shows the permissions to be "Custom." I have changed some to "Read and Write" and I have changed all of them to "Read and Write." Neither of these have fixed the problem. Time Machine still fails on the same files.
    I really need some smart Mac person to tell me what I can do to fix this problem. Thanks.

    Csound1 wrote:
    Correct, at no time did I say that this was for everyone, it is in fact for anyone who wishes to spend his time working rather than restoring.
    For most folks, a hard drive failure is not exactly common. If they are to you, something is seriously wrong.
    Replacing a drive in a unibody MBP is a 5 minute operation! & they are cheap!
    Yes, for those who are mechanically inclined and not afraid to open up a Mac. What percentage of users do you suppose that is?
    As to your second point, I suggested specifically using a TM type backup in addition to the clone, I stated that my choice is a realtime service that stores my files (a) as files that I can access from anywhere (b) with versions (including deletions) going back as far as my storage limits allow.
    And how would you use that to roll back to a previous version of your entire system?
    I don't want to have to deal with TM permissions/user/network/extreme/forgetting to delete till it gets full blahblahblah
    Huh? Now you're adding all sorts of other things.
    Permissions? A user account is a user account, and Time Machine maintains the permissions.
    Network? Your clone is on a network? How do you boot up from that?
    Extreme? You use an Airport Extreme for your network clone?
    Forgetting to delete until it's full? Yes, that's exactly what you mentioned above: "versions (including deletions) going back as far as my storage limits allow."
    PleasePondini, do it your way and I'll do it mine
    Obviously.

  • Time Machine fails when trying to backup user folder

    When I try to backup my OSX 10.6.7 MB Pro to either an USB-attached external disk or a time capsule the backup fails shortly after the scan run, leaving me with the message "The backup was not performed because an error occured while copying files to the backup disk." The scan run is taking quite some time (more than 300'000 objects),,
    Only if I exclude my own user folder (respectively the ~) from backup the timemachine backup runs smoothly, but of course without my user data.
    The MB has an SSD with 250 GB capacity of which 188 GB are used.
    If you can assist in any way, many thanks to you!
    Kind regards
    Stefan

    Not one of Apple's best messages. 
    See #C3 in Time Machine - Troubleshooting.   It will show you how to locate the message(s) that describe the problem, then help you fix it.    If that doesn't help, post back with details, including all the messages, your setup, what you've done, and the results.

  • Time Machine stalls when trying to back up to Time Capsule or an external hard drive.

    TIme Machine stalls when trying to back up to Time Capsule or an external hard drive.  Time Machine shows a message such as "Backing up 4MB of 9.00GB" but nothing happens for hours.

    Are you really running 10.6.4 OS?
    What model TC and what firmware?
    Wireless or wired?
    How is the TC setup?
    If TM can work to neither a TC or external hard disk it is more likely the computer is faulty hard disk..
    Do a verify of the disk.
    See A5 here.
    http://pondini.org/TM/Troubleshooting.html

  • Time Machine Fails when VPN is Active

    Running Cisco VPN that allows local access to my 192.168 network with no problem for other applications. However, Time Machine fails to find my local NAS drive when the VPN is active. The NAS and MBP are on the same subnet. Any thoughts or reasons why this is occurring and how to resolve the issue?
    Thanks.

    If you're using the Cisco client built-in to OSX, be sure that "Send all traffic over VPN" is disabled. With the client from Cisco, I think the checkbox is called something like "Allow local LAN access." Be sure that that is enabled.
    Note that this setting can be overridden by the VPN administrator, and often is. (Usually for security or company policy reasons.) So do not be surprised if the checkboxes have no effect for you. If that is the case, then you'll have to speak to the VPN administrator to see if they'll make an exception.

  • Time Machine fails intermittently to start backup

    I am running MBPro Retina laptop with Mountain Lion 10.8.4, with all current updates (except for the new v. 6.3 for Airport Utility, which does not work right on my machine and many others). I am using a relatively new 2GB Time Capsule for backup via a wireless connection. The connection appears to be stable (as indicated by the console log) and I do not think that issue is relevant here. I backup has been working very well for many months but started to act up several weeks ago with a intermittent error (see below).
    I get a successful backup about 1 out  3 times, so the situation is annoying  but not fully critical. I include below a listing from the console showing the relevant part of the log for a failed initation of the backup (personal information is redacted with XXXX). I have searched out error messges for the DiskMountedNotifier and have little to help isolate the problem.  Can someone help point me in the right direction??
    6/21/13 10:45:15.686 AM com.apple.backupd[7009]: Starting automatic backup
    6/21/13 10:45:16.000 AM kernel[0]: nspace-handler-set-snapshot-time: 1371825917
    6/21/13 10:45:16.844 AM com.apple.backupd[7009]: Attempting to mount network destination URL: afp://XXXX;[email protected]/Data
    6/21/13 10:45:25.400 AM com.apple.backupd[7009]: Mounted network destination at mount point: /Volumes/Data using URL: afp://XXXX;[email protected]/Data
    6/21/13 10:45:25.000 AM kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 7012
    6/21/13 10:45:25.000 AM kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff81d0440008 /Volumes/Data (error = 0, retval = 0)
    6/21/13 10:45:41.127 AM DiskMountedNotifier[279]: Try #0, for SXvN, result = -600
    6/21/13 10:45:43.129 AM DiskMountedNotifier[279]: Try #1, for SXvN, result = 0
    6/21/13 10:45:43.129 AM DiskMountedNotifier[279]: launch for id = 0 NvXS event = Mscn result = 0
    6/21/13 10:46:28.636 AM com.apple.backupd[7009]: Failed to eject volume /Volumes/Data (FSVolumeRefNum: -122; status: -47; dissenting pid: 0)
    6/21/13 10:46:28.636 AM com.apple.backupd[7009]: Waiting 60 seconds and trying again.
    6/21/13 10:47:28.712 AM com.apple.backupd[7009]: Network destination already mounted at: /Volumes/Data
    6/21/13 10:48:25.199 AM com.apple.backupd[7009]: Failed to eject volume /Volumes/Data (FSVolumeRefNum: -122; status: -47; dissenting pid: 0)
    6/21/13 10:48:25.199 AM com.apple.backupd[7009]: Waiting 60 seconds and trying again.
    6/21/13 10:49:25.967 AM com.apple.backupd[7009]: Network destination already mounted at: /Volumes/Data
    6/21/13 10:50:07.809 AM coreaudiod[160]: Disabled automatic stack shots because audio IO is active
    6/21/13 10:50:10.047 AM coreaudiod[160]: Enabled automatic stack shots because audio IO is inactive
    6/21/13 10:50:22.889 AM com.apple.backupd[7009]: Failed to eject volume /Volumes/Data (FSVolumeRefNum: -122; status: -47; dissenting pid: 0)
    6/21/13 10:50:22.890 AM com.apple.backupd[7009]: Giving up after 3 retries.
    6/21/13 10:50:32.928 AM com.apple.backupd[7009]: Backup failed with error: 21
    6/21/13 10:50:32.988 AM com.apple.backupd[7009]: [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
    6/21/13 10:50:32.988 AM com.apple.backupd[7009]: Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
    6/21/13 10:50:32.988 AM com.apple.backupd[7009]: Failed to eject Time Machine disk image: /Volumes/Data/Queets.sparsebundle
    6/21/13 10:50:33.064 AM UserNotificationCenter[7065]: *** WARNING: Method userSpaceScaleFactor in class NSWindow is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.

    I have used the above to fix a Time Machine issue. I had a problem with my backup and after recovering the
    sparsebundle I still could not get the backup to run.
    The error message I had initially was
    sparse bundle could not be accessed (error -1)
    I took correctve action from these useful sites and recoved the sparsebundle
    http://www.pondini.org/TM/C17.html
    http://blog.jthon.com/?p=31
    But the message "sparse bundle could not be accessed (error -1)" just would not go away and
    In the system log I had this message repeated 3 times for each backup attempt.
    26/08/2013 21:43:27.269 com.apple.backupd[434]: Failed to eject volume /Volumes/Data (FSVolumeRefNum: -105; status: -47; dissenting pid: 0)
    The final thing I needed to do was remove /Volumes/Time Machine Backups.  I think it was dated from when my backup first got corrupted.

  • Time Machine crashes when trying to view Mail

    Using Time Machine to backup. I can see on my backup drive that it is producing the incremental backups.
    In Finder, when I click on TM to view previous times/days, it works fine. I am able to view files and folders that were previously there. I am able to recover old files.
    In Mail, when I click TM, it tells me to "Click Restore to retrieve" whatever mailbox I have selected, and then TM crashes within seconds. Mail stays open, as it is not effected.

    scottnl wrote:
    Using Time Machine to backup. I can see on my backup drive that it is producing the incremental backups.
    In Finder, when I click on TM to view previous times/days, it works fine. I am able to view files and folders that were previously there. I am able to recover old files.
    That's not the best way to recover files, as you may have permissions or other problems with them. Use the TM "Star Wars" display (once you get it fixed).
    In Mail, when I click TM, it tells me to "Click Restore to retrieve" whatever mailbox I have selected, and then TM crashes within seconds. Mail stays open, as it is not effected.
    Does that also happen when you go into TM from a Finder window, or iPhoto?
    Do you see not only the +Today (Now)+ window, but a "cascade" of windows behind it, and a TimeLine on the right? Is there a starry background, and is it moving?
    If all those are "yes," then TM is having trouble reading your backups. Do a +*Repair Disk+* (not permissions) on the drive, via Disk Utility (in your Applications/Utilities folder).
    If any of those are "no," this can be caused by any of a number of things. Try these fixes:
    If you're using a Finder replacement (such as Pathfinder), be sure the Finder is running.
    If you're using Spaces, turn it off temporarily.
    If you have a second monitor, or anything plugged-in to a video-out port, disconnect it temporarily.
    De-select your TM drive via TM Preferences > Change Disk (select "none"), then re-select the correct one.
    Do a "complete reset" of TM, as in item #A4.
    Do a +*Repair Disk+* on your TM drive.
    Try or create another user (System Preferences > Accounts). If it works ok from that user, delete the file:
    +*<home folder of the user where it doesn't work>/Library/Preferences/com.Apple.Finder.plist+*

  • How can I force Time Machine to make a complete backup of my Hard Drive.  I just installed a new external drive for Backup since my previous one failed.  Now when I back up, Time Machine only backs up my data folder and the Users folder.

    How can I force Time Machine to make a complete backup of my Hard Drive.  I just installed a new external drive for Backup since my previous one failed.  Now when I back up, Time Machine only backs up my data folder and the Users folder.
    When I start a backup. Time Machine says "Oldest Backup: None; Latest Backup: None", so it seems like it should do a complete backup, but it only does a partial. 

    Hi I'd like to jump in here. Your app showed me this:
    Time Machine:
              Skip System Files: NO
              Mobile backups: OFF
              Auto backup: YES
              Volumes being backed up:
                        Macintosh HD: Disk size: 749.3 GB Disk used: 453.81 GB
              Destinations:
                        Plastic Wrapper [Local] (Last used)
                        Total size: 999.86 GB
                        Total number of backups: 64
                        Oldest backup: 2013-07-24 23:25:11 +0000
                        Last backup: 2013-11-17 01:40:47 +0000
                        Size of backup disk: Too small
                                  Backup size 999.86 GB < (Disk used 453.81 GB X 3)
              Time Machine details may not be accurate.
              All volumes being backed up may not be listed.
              /sbin excluded from backup!
              /usr excluded from backup!
              /System excluded from backup!
              /bin excluded from backup!
              /private excluded from backup!
              /Library excluded from backup!
              /Applications excluded from backup!
    Aside from the size of my backup drive, which I will increase at some point, I'd really like to have time machine backing up all system folders, especially Applications. How to I reset this hidden exclusions?
    Thanks,
    Darcy

  • Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem."  Tried suggestions I've seen on the forum.

    Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem."  I've tried various suggestions I've seen on the forum but nothing has worked.  TIme Machine worked fine for the last two years and just suddenly started having this problem every time.  The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned.  I have more than enough available backup storage space for it.  Before failing, Time Machine has backed up no more than 12GB or so of the backup.  It fails during different files each time.
    I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem.  It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine. 
    I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
    I have system logs that I can share if helpful.  The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
    I always get this message near the beginning of the backup:
    Event store UUIDs don't match for volume: Macintosh HD
    I've gotten this messsage a number of times:
    Bulk setting Spotlight attributes failed.
    One Day
    Stopping backupd to allow ejection of backup destination disk!
    Another day
    1/7/12 10:44:20 AM
    mDNSResponder[18]
    PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
    1/7/12 10:46:37 AM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
    1/7/12 10:46:37 AM
    kernel
    AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
    Another Day
    1/6/12 8:03:22 AM
    Google Chrome[164]
    Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
    1/6/12 8:04:02 AM
    com.apple.backupd[193]
    Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
    1/6/12 8:06:58 AM
    /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
    No valid tickets, timing out
    1/6/12 8:29:44 AM
    mDNSResponder[19]
    PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
    1/6/12 8:59:22 AM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  doing reconnect on /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    ASP_TCP asp_SetTCPQoS:  sock_settclassopt got error 57
    Another day
    1/5/12 3:48:55 PM
    mdworker[2128]
    CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
    1/5/12 4:24:54 PM
    mDNSResponder[19]
    PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
    1/5/12 4:29:58 PM
    com.apple.backupd[2074]
    Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
    1/5/12 4:39:00 PM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380

    bokon0n wrote:
    1/11/12 8:53:30 AM
    com.apple.backupd[1169]
    Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
    1/11/12 8:53:30 AM
    com.apple.backupd[1169]
    Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
    Those indicate that your NAS is not fully compatible with Snow Leopard. 
    1/11/12 8:53:35 AM
    kernel
    jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
    1/11/12 8:53:39 AM
    kernel
    jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
    1/11/12 8:53:39 AM
    kernel
    jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
    1/11/12 8:53:49 AM
    kernel
    jnl: disk2s2: journal replay done.
    1/11/12 8:53:49 AM
    fseventsd[41]
    event logs in /Volumes/Time Machine/.fseventsd out of sync with volume.  destroying old logs. (253512 14 253512)
    1/11/12 8:53:50 AM
    kernel
    hfs: Removed 1 orphaned / unlinked files and 0 directories
    That looks like a problem was found with the file system (data) on the TM disk.  I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive.    Likely a result of the incompatibility mentioned above.
    1/11/12 9:47:40 AM
    com.apple.backupd[1169]
    Bulk setting Spotlight attributes failed.
    That's a problem writing to the NAS drive.
    But the backup continued after all this.
    1/11/12 1:25:07 PM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
    Something caused a disconnect.  Can't tell from the log what it was.
    I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
    To be incompatible with Snow Leopard, this NAS must be at least a couple of years old.  It may be beginning to fail.
    Contact the maker.  See if there's an update to make it compatible with Snow Leopard.  If so, that might fix it.
    If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light.

  • HT3275 Since updating OS to Mountain Lion from leopard, I get the following error message when trying to backup with time machine on external drive.  Could not complete backup to media share.  The network backup disk does not support the required AFP feat

    Since updating OS to Mountain Lion from leopard, I get the following error message when trying to backup with time machine on external drive.  "Could not complete backup to media share.  The network backup disk does not support the required AFP features."  What are AFP features and how do I get Time Machine to backup to my current external backup?

    This means that your NAS does not support the required encryption. Update your NAS to the latest firmware or ditch it and buy a Time Capsule (they are the most reliable when using TM).

  • I keep getting this error when trying to backup time capsule with time machine. The backup disk image "/Volumes/Data-1/Dan's iMac.sparsebundle" is already in use.

    I keep getting this error when trying to backup time capsule with time machine. The backup disk image “/Volumes/Data-1/Dan’s iMac.sparsebundle” is already in use.

    Make sure that no other Macs are backing up at the time.
    Pull the power cable from the back of the Time Capsule
    Count to ten
    Plug the power cable back into the back of the Tme Capsule
    Wait a few minutes, then try a backup again.

  • Time machine failed me when my 2010 iMac HDD failed

    Hello,
    Just had a bit of a nightmare!
    My mid 2010 27" iMAC has been running slow the last few months and last week it was pretty much unusable. No issues on the CPU/system memory in Activity monitor so i suspected that the drive was failing.
    I have it, and my two macbooks backing up to a 4th gen 3TB time capsule.
    I'd verified and repaired permissions. This caused it to start a fresh time machine backup but it never made any progress and kept saying two days to complete.
    The apple care guy asked me to try and verify and repair the disk but the it came back that the disk could not be repaired and that I should backup, reformat  and restore but gave me no option to backup. The disk couldn't be mounted either.
    No problem I thought, I'd get a free replacement drive under Applecare and restore from my Time machine backups. BUT, when we looked for them in the Time Capsule folders there was nothing there. I could access the backup files for the macbooks but the iMac had a sparsebundle file that didn't open and one data folder that was".inprogress".
    It had never before crossed my mind that Time Machine could start a fresh backup but not complete it, and in doing so make it impossible to access my earlier backups. It seems to me that it's failed to do exactly what it's meant to do.
    I have everything on this iMAC including photos of my two kids, hundreds of ripped CD's in iTunes etc.
    The recommended service guy has confirmed that the drive has failed and that the backup also failed. He does, however, think that he'll be able to recover the data and put it back on a new hard drive. Phew!
    The time capsule cost over £300 and now I'm thinking that I need an alternative backup system; something that doesn't just rely on one backup, possibly with multiple connected drives. Any suggestions for something? It's outside of my knowledge base.
    Just thought it'd be worth flagging this as a potential issue. I guess I should have disabled Time Machine before trying anything?
    Cheers
    Dave

    See Pondini's TM FAQs, for starters.

  • Time machine fails backing up with a "backup disk not found" error after upgrade to Lion 10.7.2

    Time machine fails backing up with a "backup disk not found" error after upgrade to Lion 10.7.2. I've erased and reformatted the drive; reconnected Time Machine(it saw it) and began a new backup. The backup starts again but fails before completing with backup drive not found error. I used the 10.7.2 combo update. Any help on how to fix this problem would be appreciated.

    Arghhhhhhhhhhhhhhhhhhh!!!!!!
    After waiting since October for a fix, I have now upgraded the firmware on the Time Capsule and installed the new Airport Utility, released yesterday, and the situation is even worse.
    Up until now, the Airport Utility had an option to disconnect all drives manually and the Time Capsule would then work until the next reboot – a temporary (?) work-around.
    Now that option does not exist in the new-look Airport Utility. And the Airport Utility installation can’t be rolled back and the old utility won’t restore.
    The sparesbundle is still not accessible. Anyone worked out a work-around in the new environment yet?
    I have another Time Machine backup working fine to a trusty old Lacie Drive so erased the one on my Time Capsule to see if that works. I have renamed the Capsule and the Time Capsule Drive.  But to build another full backup will take at least two days and I shall be away from tomorrow and am reluctant to leave the Capsule and computer up and running for a week. And I’ll bet the sparsbundle will still be nowhere to be found.
    How can Apple screw up so badly when they are to become the richest company in the entire world and – soon – will have more cash in the bank than the entire United States? Can’t they afford someone who really can sort this out? Especially when a Firewire connected hard drive – my trusty and simple LaCie – works fine.
    Words, almost, fail me.

  • Time Machine Failed to Backup

    Time Machine failing to backup last few days. Tried Disk Utility disk repair. Failed, with response, "Could not unmount disk." Installed Time Machine Buddy and copied this message:
    Starting standard backup
    Backing up to: /Volumes/Backup HD-1/Backups.backupdb
    Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Backup HD-1/Backups.backupdb/WuLi’s MacBook Pro size:13
    Error: (-50) Creating directory 2011-12-23-204707.inProgress
    Failed to make snapshot container.
    Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Backup HD-1/Backups.backupdb/WuLi’s MacBook Pro size:13
    Backup failed with error: 2
    Any help appreciated.

    Hi, TM is such a pain & the worst Backup App I've ever ebcountered outside of no backup at all, that being said the great Pondini has covered most all of it's problems here...
    http://pondini.org/TM/Troubleshooting.html
    http://pondini.org/TM/C10.html
    Not that it helps much but...
    unitEmptyErr                  = -22,  /*I/O System Errors*/
    What Brand/Model External drive is this?

  • I tried to instal 10.8.3 to my MBP and it crashed. I then tried to restore from Time machine but when it is about 50% through a message comes up "the files cannot be restored"

    I tried to instal 10.8.3 to my MBP and it crashed. I then tried to restore from Time machine but when it is about 50% through a message comes up "the files cannot be restored" Can anyone help me to get out of this mess?

    Back up all data.
    Boot into Recovery by holding down the key combination command-R at the startup chime. Release the keys when you see a gray screen with a spinning dial.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.
    When the OS X Utilities screen appears, follow the prompts to reinstall the OS. You don't need to erase the boot volume, and you won't need your backup unless something goes wrong. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.

Maybe you are looking for