Why has Time Machine failed?

Since I upgraded to Mavericks (24" Mac, early 2009) time machine has shown all the widely discussed problems.
I thought the various suggestions had fixed it - thanks to all - but after a week or so of working properly it has decided to quit. 
It now keeps telling me that the backup has Failed - no explanation offered.
There is still 350GB free on the backup disk and disk full problems have always been reported as such (before mavericks). 
Has anyone any suggestions - other than reformatting and starting again, again.

first before anyone here can help you, tell us how you do your backups. Are they being done wirelessly or thru an ethernet cable? If your doing them wirelessly, change over to ethernet. My Time Machine backup took over 7 Hours and that was via ethernet, I tried wirelessly the first time and it failed too.
Second, next time do a google search before complaining about incompatibility issues with either device.
Better yet, try this, open up airport utility and select the time capsule. from there, go to manual setup. Select "Wireless" tab. See the radio mode selector, hold down the "option" button on your keyboard and select the prefences that don't include the "N" as an option. you lose "N" speeds. but you gain stabile xBox gaming.
Here are complete instructions incase you need more help.
http://www.xbox360fanboy.com/2007/02/26/xbox-360-and-airport-extreme-compatibili ty-fix/
Message was edited by: JSR

Similar Messages

  • Why does Time Machine fail to restore and keep the original file after I have provided my Admin password?

    I'm attempting to recover a group of lost files from Time Machine. The files are backups from a mobile app within User/LibraryMobile Documents/.
    I'm able to find the lost files, but Time Machine failed to restore them after I select 'Keep Both' and then enter my Admin Password. The screen returns to the desktop and the finder window for the file I'm trying to recover, but nothing else happens.
    I hope someone can help.
    Bil

         "Time Machine in Safe Mode couldn't access any history
         Why not? What happened?
    I have no Idea what happened. Here is the screenshot showing no history at all, and the Console:"
    2/10/2014 6:08:25.166 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[401]) Exited with code: 1
    2/10/2014 6:08:25.166 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:08:28.209 am WindowServer[95]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
    2/10/2014 6:08:28.337 am WindowServer[95]: Display 0x4280480 captured by conn 0xcc03
    2/10/2014 6:08:29.211 am WindowServer[95]: CGXOrderWindowList: Invalid window 85 (index 0/1)
    2/10/2014 6:08:35.206 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[403]) Exited with code: 1
    2/10/2014 6:08:35.206 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:08:40.577 am com.apple.IconServicesAgent[308]: main Failed to composit image for binding VariantBinding [0x6a9] flags: 0x8 binding: FileInfoBinding [0x1d1] - extension: png, UTI: public.png, fileType: ????.
    2/10/2014 6:08:40.578 am quicklookd[408]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x203] flags: 0x8 binding: FileInfoBinding [0x103] - extension: png, UTI: public.png, fileType: ???? request size:64 scale: 1
    2/10/2014 6:08:42.209 am WindowServer[95]: disable_update_likely_unbalanced: UI updates still disabled by application "Finder" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
    2/10/2014 6:08:42.209 am Finder[279]: void CGSUpdateManager::log() const: conn 0xcc03 legacy 1
    2/10/2014 6:08:42.211 am Finder[279]: Backtrace (at 1618.93):
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  0   CoreGraphics                        0x000000010d02b379 CGSBacktraceCreate + 59
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  1   CoreGraphics                        0x000000010d0da62c _ZN16CGSUpdateManager21disable_update_legacyEv + 78
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  2   CoreGraphics                        0x000000010d0da5d7 CGSDisableUpdate + 35
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  3   Finder                              0x0000000107b66aae Finder + 1608366
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  4   Finder                              0x0000000107b66224 Finder + 1606180
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  5   CoreFoundation                      0x000000010cbb7e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  6   CoreFoundation                      0x000000010cb79f79 ____CFXNotificationPostToken_block_invoke + 137
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  7   CoreFoundation                      0x000000010cb1a48c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  8   CoreFoundation                      0x000000010cb0bae5 __CFRunLoopDoBlocks + 341
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  9   CoreFoundation                      0x000000010cb0b86e __CFRunLoopRun + 1982
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  10  CoreFoundation                      0x000000010cb0ae75 CFRunLoopRunSpecific + 309
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  11  HIToolbox                           0x000000010a829a0d RunCurrentEventLoopInMode + 226
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  12  HIToolbox                           0x000000010a8297b7 ReceiveNextEventCommon + 479
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  13  HIToolbox                           0x000000010a8295bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  14  AppKit                              0x000000010b7c224e _DPSNextEvent + 1434
    2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const:  15  AppKit                              0x000000010b7c189b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
    2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const:  16  AppKit                              0x000000010b7b599c -[NSApplication run] + 553
    2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const:  17  AppKit                              0x000000010b7a0783 NSApplicationMain + 940
    2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const:  18  Finder                              0x00000001079e4730 Finder + 26416
    2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const:  19  libdyld.dylib                       0x000000010df545fd start + 1
    2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const:  20  ???                                 0x0000000000000001 0x0 + 1
    2/10/2014 6:08:45.256 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[410]) Exited with code: 1
    2/10/2014 6:08:45.256 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:08:55.346 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[411]) Exited with code: 1
    2/10/2014 6:08:55.346 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:09:05.431 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[412]) Exited with code: 1
    2/10/2014 6:09:05.431 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:09:15.480 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[413]) Exited with code: 1
    2/10/2014 6:09:15.480 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:09:24.342 am WindowServer[95]: CGXOrderWindowList: Invalid window 85 (index 0/1)
    2/10/2014 6:09:25.497 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[414]) Exited with code: 1
    2/10/2014 6:09:25.497 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:09:26.008 am WindowServer[95]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 58.80 seconds (server forcibly re-enabled them after 1.00 seconds)
    2/10/2014 6:09:26.338 am WindowServer[95]: Display 0x4280480 released by conn 0xcc03
    2/10/2014 6:09:35.517 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[415]) Exited with code: 1
    2/10/2014 6:09:35.517 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:09:45.541 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[416]) Exited with code: 1
    2/10/2014 6:09:45.541 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
         "Have you tried restoring at the folder level? so that all files in the folder are restored.   As it is an incremental backup - also wait until you hear the backup drive stop spinning - as it has to find the physical files - pointing to them."
    Yes, I've tried both, and waiting until the drive stops spinning:
    Here is the Console list:
    2/10/2014 6:28:38.742 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[995]) Exited with code: 1
    2/10/2014 6:28:38.742 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:28:46.603 am WindowServer[122]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
    2/10/2014 6:28:46.778 am WindowServer[122]: Display 0x4280482 captured by conn 0xe80b
    2/10/2014 6:28:48.761 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1000]) Exited with code: 1
    2/10/2014 6:28:48.761 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:28:49.891 am WindowServer[122]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04280482 device: 0x7f9dc1422710  isBackBuffered: 1 numComp: 3 numDisp: 3
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
    2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
    2/10/2014 6:28:58.780 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1003]) Exited with code: 1
    2/10/2014 6:28:58.780 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:29:00.603 am WindowServer[122]: disable_update_likely_unbalanced: UI updates still disabled by application "Finder" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
    2/10/2014 6:29:00.604 am Finder[206]: void CGSUpdateManager::log() const: conn 0xe80b legacy 1
    2/10/2014 6:29:00.605 am Finder[206]: Backtrace (at 1000.37):
    2/10/2014 6:29:00.605 am Finder[206]: void CGSUpdateManager::log() const:  0   CoreGraphics                        0x0000000108c65379 CGSBacktraceCreate + 59
    2/10/2014 6:29:00.606 am Finder[206]: void CGSUpdateManager::log() const:  1   CoreGraphics                        0x0000000108d1462c _ZN16CGSUpdateManager21disable_update_legacyEv + 78
    2/10/2014 6:29:00.606 am Finder[206]: void CGSUpdateManager::log() const:  2   CoreGraphics                        0x0000000108d145d7 CGSDisableUpdate + 35
    2/10/2014 6:29:00.606 am Finder[206]: void CGSUpdateManager::log() const:  3   Finder                              0x000000010377faae Finder + 1608366
    2/10/2014 6:29:00.606 am Finder[206]: void CGSUpdateManager::log() const:  4   Finder                              0x000000010377f224 Finder + 1606180
    2/10/2014 6:29:00.607 am Finder[206]: void CGSUpdateManager::log() const:  5   CoreFoundation                      0x00000001087f7e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
    2/10/2014 6:29:00.607 am Finder[206]: void CGSUpdateManager::log() const:  6   CoreFoundation                      0x00000001087b9f79 ____CFXNotificationPostToken_block_invoke + 137
    2/10/2014 6:29:00.607 am Finder[206]: void CGSUpdateManager::log() const:  7   CoreFoundation                      0x000000010875a48c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
    2/10/2014 6:29:00.608 am Finder[206]: void CGSUpdateManager::log() const:  8   CoreFoundation                      0x000000010874bae5 __CFRunLoopDoBlocks + 341
    2/10/2014 6:29:00.608 am Finder[206]: void CGSUpdateManager::log() const:  9   CoreFoundation                      0x000000010874b86e __CFRunLoopRun + 1982
    2/10/2014 6:29:00.608 am Finder[206]: void CGSUpdateManager::log() const:  10  CoreFoundation                      0x000000010874ae75 CFRunLoopRunSpecific + 309
    2/10/2014 6:29:00.608 am Finder[206]: void CGSUpdateManager::log() const:  11  HIToolbox                           0x000000010645ea0d RunCurrentEventLoopInMode + 226
    2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const:  12  HIToolbox                           0x000000010645e7b7 ReceiveNextEventCommon + 479
    2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const:  13  HIToolbox                           0x000000010645e5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
    2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const:  14  AppKit                              0x00000001073fd24e _DPSNextEvent + 1434
    2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const:  15  AppKit                              0x00000001073fc89b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
    2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const:  16  AppKit                              0x00000001073f099c -[NSApplication run] + 553
    2/10/2014 6:29:00.610 am Finder[206]: void CGSUpdateManager::log() const:  17  AppKit                              0x00000001073db783 NSApplicationMain + 940
    2/10/2014 6:29:00.610 am Finder[206]: void CGSUpdateManager::log() const:  18  Finder                              0x00000001035fd730 Finder + 26416
    2/10/2014 6:29:00.610 am Finder[206]: void CGSUpdateManager::log() const:  19  libdyld.dylib                       0x0000000109b875fd start + 1
    2/10/2014 6:29:00.610 am Finder[206]: void CGSUpdateManager::log() const:  20  ???                                 0x0000000000000001 0x0 + 1
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
    2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
    2/10/2014 6:29:08.798 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1008]) Exited with code: 1
    2/10/2014 6:29:08.798 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:29:18.817 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1012]) Exited with code: 1
    2/10/2014 6:29:18.817 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:29:24.300 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
    2/10/2014 6:29:24.300 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
    2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
    2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
    2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
    2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
    2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
    2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
    2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
    2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
    2/10/2014 6:29:28.843 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1019]) Exited with code: 1
    2/10/2014 6:29:28.843 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:29:29.894 am WindowServer[122]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 44.29 seconds (server forcibly re-enabled them after 1.00 seconds)
    2/10/2014 6:29:30.261 am WindowServer[122]: Display 0x4280482 released by conn 0xe80b
    2/10/2014 6:29:30.382 am WindowServer[122]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04280482 device: 0x7f9dc1422710  isBackBuffered: 1 numComp: 3 numDisp: 3
    2/10/2014 6:29:38.861 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1024]) Exited with code: 1
    2/10/2014 6:29:38.861 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:29:48.879 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1027]) Exited with code: 1
    2/10/2014 6:29:48.879 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:29:52.483 am com.apple.backupd[907]: Copied 1776 items (176.1 MB) from volume Macintosh HD iMac 21.5-inch, Late 2013. Linked 13206.
    2/10/2014 6:29:58.897 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1037]) Exited with code: 1
    2/10/2014 6:29:58.897 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:30:06.184 am launchservicesd[98]: Application App:"Console" asn:0x0-6b06b pid:951 refs=6 @ 0x7ff443443bd0 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x6c06c pid=1034 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100004/0x186a4 queue
    2/10/2014 6:30:06.185 am WindowServer[122]: [cps/setfront] Failed setting the front application to Console, psn 0x0-0x6b06b, securitySessionID=0x186a4, err=-13066
    2/10/2014 6:30:06.646 am com.apple.backupd[907]: Will copy (4.3 MB) from Macintosh HD iMac 21.5-inch, Late 2013
    2/10/2014 6:30:06.647 am com.apple.backupd[907]: Found 68 files (4.3 MB) needing backup
    2/10/2014 6:30:06.647 am com.apple.backupd[907]: 7.89 GB required (including padding), 133.44 GB available
    2/10/2014 6:30:08.233 am iSnap[331]: Can't Retrieve Window Zoom
    2/10/2014 6:30:08.579 am iSnap[331]: time out
    2/10/2014 6:30:08.917 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1041]) Exited with code: 1
    2/10/2014 6:30:08.917 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:30:18.448 am com.apple.appkit.xpc.openAndSavePanelService[1047]: assertion failed: 13F34: liblaunch.dylib + 25164 [A40A0C7B-3216-39B4-8AE0-B5D3BAF1DA8A]: 0x25
    2/10/2014 6:30:18.934 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1049]) Exited with code: 1
    2/10/2014 6:30:18.934 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    2/10/2014 6:30:18.980 am com.apple.appkit.xpc.openAndSavePanelService[1047]: Bogus event received by listener connection:
    <error: 0x111766b50> { count = 1, contents =
    "XPCErrorDescription" => <string: 0x111766e60> { length = 18, contents = "Connection invalid" }
    2/10/2014 6:30:18.981 am librariand[219]: client process 349 does not have a valid com.apple.developer.ubiquity-container-identifiers entitlement
    2/10/2014 6:30:18.982 am librariand[219]: error in handle_container_path_request: LibrarianErrorDomain/9/The client process does not have a valid com.apple.developer.ubiquity-container-identifiers entitlement
    2/10/2014 6:30:20.551 am com.apple.backupd[907]: Copied 204 items (4.3 MB) from volume Macintosh HD iMac 21.5-inch, Late 2013. Linked 1778.
    2/10/2014 6:30:21.935 am com.apple.backupd[907]: Created new backup: 2014-10-02-063021
    2/10/2014 6:30:22.625 am launchservicesd[98]: Application App:"Monosnap" asn:0x0-28028 pid:349 refs=5 @ 0x7ff443632f50 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x6c06c pid=1034 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100004/0x186a4 queue
    2/10/2014 6:30:22.625 am WindowServer[122]: [cps/setfront] Failed setting the front application to Monosnap, psn 0x0-0x28028, securitySessionID=0x186a4, err=-13066
    2/10/2014 6:30:22.874 am WindowServer[122]: CGXSetWindowLevel: Operation on a window 0x236 requiring rights kCGSWindowRightPresenter by caller com.apple.appkit.xpc.openAndSav
    2/10/2014 6:30:22.874 am com.apple.appkit.xpc.openAndSavePanelService[1047]: CGSSetWindowLevel
    2/10/2014 6:30:22.874 am com.apple.appkit.xpc.openAndSavePanelService[1047]: PSsetwindowlevel, error setting window level (1001)
    2/10/2014 6:30:24.868 am com.apple.backupd[907]: Starting post-backup thinning
    2/10/2014 6:30:24.868 am com.apple.backupd[907]: No post-backup thinning needed: no expired backups exist
    2/10/2014 6:30:24.898 am com.apple.backupd[907]: Backup completed successfully.
    2/10/2014 6:30:25.501 am launchservicesd[98]: Application App:"Finder" asn:0x0-b00b pid:206 refs=7 @ 0x7ff443429180 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x6c06c pid=1034 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100004/0x186a4 queue
    2/10/2014 6:30:25.502 am WindowServer[122]: [cps/setfront] Failed setting the front application to Finder, psn 0x0-0xb00b, securitySessionID=0x186a4, err=-13066
    2/10/2014 6:30:28.952 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1056]) Exited with code: 1
    2/10/2014 6:30:28.952 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
    Still restores only the first 7 files of 955.
    I appreciate your efforts to help. That's a lot of files that are lost!

  • Why has Time machine been backing up for more than a week on Ethernet?

    I recently had to format my MacBook Pro (Snow Leopard). Fortunately I was using Time Machine on Time Capsule. I was able to restore from my last backup everything as it was before.
    However, after all that, backing up for the first time was taking too long (105 GB) on Wifi so I connected my laptop to the time capsule using an ethernet cable. The first 35GB backed up in a few hours... but it has taken a WEEK to go from 35GB to 70GB!!
    Why is this taking so long? What can I do to speed up the process? I am worried that if I cancel the backup I'll have to start all over again...

    Hi V,
    Cancel it. There may be an issue, so it might never finish. Or, it could just be a hiccup, and by starting it over it will complete in a few hours at most.
    When you quit it, run Repair Disk on the TM HD, and Verify disk on your internal HD (from Disk Utility).

  • Why did Time Machine fail?

    I received the following message when Time Machine stopped working:
    An error occurred while linking files on the backup volume.
    I had to reinstall my OS X (10.5.6) today from the disk because of crashing problems, etc.

    Hi, and welcome to the forums.
    "Crashing problems, etc." could have caused damage to the data on your TM disk. I'd start by doing a +Repair Disk+ (not permissions) on it via Disk Utility (in your Applications/Utilities folder.)
    Also, download the +Time Machine Buddy+ widget from: http://www.apple.com/downloads/dashboard/status/timemachinebuddy.html. It shows the messages from your logs for one TM backup run at a time, in a small window. If it fails again, copy and post the messages here (be sure to get them all, as sometimes they overflow the small window).

  • TS1550 Back up to time machine failed.  Error, "Files can't be copied onto the backup disk because it appears to be read-only". Back up has been working.  drive is not read only.  How do I fix this?

    Back up to time machine failed.  Error, "Files can’t be copied onto the backup disk because it appears to be read-only". Back up has been working.  drive is not read only.  How do I fix this?

    Hello,
    http://pondini.org/TM/C6.html

  • I have time machine saving onto two usb drives.  The backup is 4.6TB.  Each drive is 6TB.  Why is time machine only updating one drive?  (The other has been the same for two weeks.)

    I have time machine saving onto two usb drives. 
    The total size of the files being backed up is 4.6TB. 
    Each external USB drive is 6TB.   So I have 12 TB of space for Time Machine.
    Why is time machine only updating one USB drive?  (One drive has been the same for two weeks.)
    I have selected both drives in the Time Machine settings panel.
    My understanding was that it would do a full backup, and then incremental backups of changed files, getting rid of old copies as needed, and alternate between the two drives.
    But it looks like drive A has one complete backup, dated two weeks ago, and drive B is the only one getting action.
    There is a red icon on drive one that says the drive needs 120GB more space to do a backup -- which is strange since the whole backup set is only 4.6TB in size, and the drive is 6TB in size...

    You could try a clone instead.
    Clone  - Carbon Copy Cloner          (Often recommended as it has more features than some others)
    Clone – Data Backup
    Clone – Deja Vu
    Clone  - SuperDuper
    Clone - Synk
    Clone Software – 6 Applications Tested
    Time Machine Versus Clones and Archives
    Commonly Used Backup Methods

  • Why does Time Machine Hang OSX when a USB drive does not respond?

    I use USB drives to store photo data. When I back up the drives using Time Machine to a Time Capsule, If I have added a large amount of data to the USB drive, the backup will consistently fail with the drive hung. I can see the drive in finder, but I cannot see the directory structure. Often OSX hangs too and I cannot even get to finder, just the whirling colored wheel. Sometimes the system has entered sleep mode and it will not wake up. I if I am using the monitor, I can open the MAC Book Pro cover and the screen there shows alternately, a blue screen and the screen wallpaper, flipping back and forth but otherwise unresponsive. If I turn the USB drive off the OS recovers and Time Machine completes, usually indicating a backup failure (but not always). The drive is always very hot under these circumstances, indicating that the system is issuing repetitive operations to the drive. I should emphasize that I am not writing to the USB drives during backup, Time Machine is just reading the drive. So several questions:
    1) How in the world can a non system drive hang the Operating System? This is a big no-no for a supposedly multi-tasking Operating System.
    2) I use Aperture 2.1 to store data on the USB drives with no problems (at least so far). Why would Time Machine drive the USB drive so hard that it fails? I had the same problem using a USB drive with iTunes. It completely fried the drive by writing to it too intensively during one of the frequent software updates. Is there no throttle mechanism in OSX that limits the disc activity so that the throttle mechanism is not the failure of the drive itself?
    3) Does Apple have a list of USB drives that it has validated to be able to work with it's system reliably?

    Are the USB drives powered from the computer or do they have their own power supplies.
    There is a limit to how much power can be drawn from each USB port and also a total limit. If you exceed this, unexpected things can happen.

  • Why is Time machine saying backup disk disconnected? Using MBP 17" Lion 10.7

    Why is Time machine saying backup disk disconnected? Using MBP 17" Lion 10.7

    Do you have an external drive connected?
    If you do has it gone into sleep mode? There is a setting in the OS to put drives to sleep if they aren't being used. Energy Saver "Put the hard disk to sleep when possible".
    Also most external drives have a built in sleep function that if they aren't being accessed for a period of time they go to sleep by themselves.

  • I'm running OS X 10.6.8-Why is Time Machine all of a sudden backing up 225GB of data after 2 years of perfect service? I have not added, deleted, or upgraded anything, Help!

    I'm running OS X 10.6.8-Why is Time Machine all of a sudden backing up 250GB of data after 2 years of perfect service? I have not added, deleted, or upgraded anything.

    USB 3.0 drives work on USB 2.0 but you do get 2.0 speed. They are cheaper because they are popular PC drives.  If you get a new computer you'll get the bump to 3.0 speed.
    I like the Seagate USB 3.0 Backup plus drives. They come formatted for PC but easy to format in Disk Utility.  Seagate Backup Plus Right now the 1T is more than the 2 & 3T drives
    This Western Digital drive has good reviews: WD My Book Hard Drive for Mac 2 TB $99.
    Locally, Best Buy seems to have the best prices.
    USB 3.0 is 10x faster than USB 2.0
    Thunderbolt is 12 times faster than FireWire 800 and up to 20 times faster than USB 2.0.
    Format new drives with Apple's Disk Utility rather than the software that come with the drive.
    My plan was to rid a lot of the stuff I have on my computer (to a hard drive) anyhow once it had backed up.
    I wound't necessarily backup those files to Time Machine. I would copy to the external drive then delete from computer. Only backup to Time Machine the data you would want to restore to your Mac if there was a problem. The backup will go much faster this way. Time Machine backup is slower than just copying data in my experience.

  • 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 post 10.10.3 update

    I updated to 10.10.3, and have had repeated Time Machine fails since this occurred.  Time Machine suggests I run Disk Utility and repair the disk.  I did this, and found no problems (with both Verify Disk and Repair Disk options).
    From the Console app, I can filter for "backupd" messages, and get the following related to one of the failed backup sessions:
    4/12/15 11:30:00.006 AM com.apple.backupd-helper[69]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
    4/12/15 11:30:30.246 AM com.apple.backupd[10741]: Starting automatic backup
    4/12/15 11:30:30.270 AM com.apple.backupd[10741]: Backing up to /dev/disk1s2: /Volumes/MacBookPro TimeMachine/Backups.backupdb
    4/12/15 11:35:46.000 AM kernel[0]: process backupd[10741] thread 631168 caught burning CPU! It used more than 50% CPU (Actual recent usage: 66%) over 180 seconds. thread lifetime cpu usage 176.484545 seconds, (70.631140 user, 105.853405 system) ledger info: balance: 90003233817 credit: 176356562163 debit: 86353328346 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 136165186157
    4/12/15 11:35:46.891 AM spindump[644]: Saved cpu_resource.diag report for backupd version ??? (???) to /Library/Logs/DiagnosticReports/backupd_2015-04-12-113546_Erics-MacBook-Pro.cpu _resource.diag
    4/12/15 11:41:09.660 AM com.apple.backupd[10741]: Will copy (13.69 GB) from Macintosh HD
    4/12/15 11:41:09.737 AM com.apple.backupd[10741]: Found 130612 files (17.91 GB) needing backup
    4/12/15 11:41:10.096 AM com.apple.backupd[10741]: 24.46 GB required (including padding), 57.12 GB available
    4/12/15 12:04:57.848 PM com.apple.backupd[10741]: Error: (-36) SrcErr:YES Copying /Users/kolding/Pictures/iPhoto Library.migratedphotolibrary/Masters/2014/03/21/20140321-120920/GOPR0169.MP4 to (null)
    4/12/15 12:06:16.684 PM com.apple.backupd[10741]: Stopping backup.
    4/12/15 12:06:16.684 PM com.apple.backupd[10741]: Error: (-43) SrcErr:NO Copying /Users/kolding/Pictures/Photos Library.photoslibrary/Masters/2014/03/21/20140321-120920/GOPR0169.MP4 to /Volumes/MacBookPro TimeMachine/Backups.backupdb/Eric’s MacBook Pro/2015-04-12-113038.inProgress/ED575193-4599-4049-A0AF-E3421044ECC1/Macintosh HD/Users/kolding/Pictures/Photos Library.photoslibrary/Masters/2014/03/21/20140321-120920
    4/12/15 12:06:16.778 PM com.apple.backupd[10741]: Copied 97535 items (605.8 MB) from volume Macintosh HD. Linked 439374.
    4/12/15 12:06:16.913 PM com.apple.backupd[10741]: Copy stage failed with error:11
    4/12/15 12:06:17.938 PM com.apple.backupd[10741]: Backup failed with error 11: 11
    4/12/15 12:08:19.141 PM com.apple.prefs.backup.remoteservice[3706]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
    This seems to imply it something related to the GOPRO0169.MP4 file.
    Any idea how to get around this problem?  The GOPRO0169.MP4 file seems to be fine, and readable.

    Start with A4 in the 1st linked article.
    Time Machine Troubleshooting
    Time Machine Troubleshooting Problems

  • Time Machine fails repeatedly with no problem detected on the external disk

    Since a couple of days, Time Machine fails repeatedly, several times a day. I repair the disk with the Disk utility, that finds no error, then I reset Time Machine as indicated, and after one or two successful backups, it fails again, with the following report given by the Time Machine Buddy widget:
    Starting standard backup
    Backing up to: /Volumes/Copies de sauvegarde Time machine/Backups.backupdb
    Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Copies de sauvegarde Time machine/Backups.backupdb/iMac de MM size:8
    Error: (-50) Creating directory 2010-09-22-231449.inProgress
    Failed to make snapshot container.
    Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Copies de sauvegarde Time machine/Backups.backupdb/iMac de MM size:8
    Backup failed with error: 2
    I insist, the disk utility doesn't find any problem in the external USB disk. Should I reinstall the OS?
    Thanks a lot for any help!
    Best regards
    Mauricio

    This is the message after the ejection failure:
    Starting standard backup
    Backing up to: /Volumes/Copies de sauvegarde Time machine/Backups.backupdb
    No pre-backup thinning needed: 5.63 GB requested (including padding), 541.66 GB available
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Device not configured
    Error: (-36) SrcErr:NO Copying /Users/mauriciomilchberg/Movies/Evenements iMovie/Nouvel événement/Edgar 4.mov to /Volumes/Copies de sauvegarde Time machine/Backups.backupdb/iMac de Mauricio Milchberg/2010-09-24-025248.inProgress/5034B0A3-F84E-4992-A7B8-8B9166E9AD42/Mac intosh HD/Users/mauriciomilchberg/Movies/Evenements iMovie/Nouvel événement
    Stopping backupd because the backup volume was ejected!
    Stopping backup.
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Error: (-8062) SrcErr:NO Copying /Users/mauriciomilchberg/Movies/Evenements iMovie/Nouvel événement/Edgar 4.mov to /Volumes/Copies de sauvegarde Time machine/Backups.backupdb/iMac de Mauricio Milchberg/2010-09-24-025248.inProgress/5034B0A3-F84E-4992-A7B8-8B9166E9AD42/Mac intosh HD/Users/mauriciomilchberg/Movies/Evenements iMovie/Nouvel événement
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Copied 4768 files (2.8 GB) from volume Macintosh HD.
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Copy stage failed with error:11
    The word "événement" has been written not by me, but by the translation.
    Anyway, I'll follow your advice and start with the combo.
    Thans a lot again.
    Best regards
    Mauricio

  • 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?

  • 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.

  • Why is Time machine backup not working after Mavericks upgrade?

    Why is Time machine backup not working after Mavericks upgrade?

    I had the same problem due to the Fire Wire port.  Apple tested it told me it is OK!, I tried a new cable, and have tested both ports on my back up device.  I find it strange that as soon as I installed Mavericks.  The drive does work using USB.  It could be a coincidence, I don't absolutely know at this point, my back up drive ports could stop working, but I doubt it!

Maybe you are looking for