Time Machine Bug after Restore

Hi all,
I've been learning Time Machine and will share two possible bugs if it is helpful.  I am working on a 2011 MacBook Pro, upgraded to Mountain Lion some months back, with 50 GB data on SSD being backed up to and restored from a LaCie SSD 80 GB partition so the speed is very nice: 14 minutes for initial backup and 7 minutes for a Reboot + Command + R restore.
Bug #1.  Both (initial) backup and restores begin with large 60 minute estimated times in Time Machine Prefs Progress Bar but, once it gets going, finishes in 14 and 7 minutes respectively.  If symptom is due to some quadratic journal searching algorithm, it may explain why APL-CARE warned me about potential 16 hour restores and could be a bug.  If it is due to Time Machine just counting what has been transferred so far, then maybe not a bug (but maybe a possible enhancement request).
Bug #2.  It appears that the first time Time Machine runs after a Cmd+R restore, it tries to rebuild an entire journal or record of what it has and, if you interrupt this initial backup, you break Time Machine.  The next time you try to backup, Time Machine thinks Everything needs to be backed up (even though your disk is identical to what it just restored), and it Fails in my case with message "Time Machine couldn't complete the back to [my LaCie drive because my 50 GB of data is already there and it thinks it needs a full 50 GB more]" in so many words.  APL-CARE (and its expert advisor) tried to call this a feature and sent me to your article HT3275 but that seems like a different issue.  Since I did not believe Time Machine was so stupid, I ran the sequence again and carefully avoided interrupting Time Machine during its initial backup following my Cmd+R restore and, indeed, it took about 8 minutes to backup 4.5 MB (and rebuild whatever it does that first time).  So this feels like a straight-up bug, Time Machine should scare me with a popup if I interrupt it while it is rebuilding its critical list for the first time after a restore.  If APL-CARE were correct, it would mean everyone loses all history after a restore, everyone needs to Erase their backup disk and start from scratch, and methinks that too would be a bug.
Hopefully this is helpful, Time Machine is otherwise very cool and I love the Star Trek GUI. 
Regards,
Dave.

And this is an ERROR in time machine.  I just did a test restore again, went quickly, then Time Machine is GONE, GONE, gone trying to restore 5MB, waiting over an hour when a fresh backup takes about 15 minutes.
So only solution is DESTROY all my backups, then start over.  Really dumb, and this page has no option to change my post back to a question, also really dumb.
I am going to swear now:  cr*p.  OK.  Fix your **** software please.  I'll deal with workarounds till then.
-dave

Similar Messages

  • Time Machine Problem after restore

    I had a hard drive crash, and after repair, I restored from a time machine back.  Everything seemed fine, although a few sets of photos were missing from iPhoto.  After things seemed to be fine I have started doing time machine backups again. 
    My problem is that they take a very long time to complete.  I expected the first one or two to take a long time, but not since then.  I have given it weeks to make sure that it has had enough time.
    Every single time the verifcation stage shows 10s of thousands of files.  Even if I have not made any changes.  In my console log I see:
    6/7/12 11:17:34 AM
    com.apple.backupd[61578]
    Node requires deep traversal:/Users/dersh/Pictures/iPhoto Library reason:contains changes|must scan subdirs|fsevent|missed reservation|
    For every single backup.  It seems like it is not actually fixing this.  From googling around, I expect that this should take a long time the first time or two, but then should finish.  It then says that it is backing up about 600 meg.  The exect number seems to change with each backup, depending on what I am doing, and what changes I have made.  But even if I do nothing, it still is in that range.  It then appears to complete, although it takes a long time.  I would guess that since it is doing the deep traverse it then has to match up a bunch of files, so doing the actual backup takes much longer then it should.  For example it might sit for a good few minutes at "backing Up:  105.2 MB of 580.2 MB" Then it moves on to 107.6.  Finally, the cleanup takes a very long time.  So overall each backup is taking 10s of minutes.  Even if I am not doing anything with the computer. 
    I am using a firewire drive directly connected to the computer.  I have done a repair of the external time machine drive, and have done a verify of the internal drive, with no issues.
    I see that I have plenty of space on the external drive. 
    So, it seems like what is happening is that it doesn't "know" that it has done a succesful backup of iPhoto, each time so it does a deep traverse  and then backsup something like 600 meg of data from there.  How can I get it to "understand" that it has done this?  Can I force it to do it once correctly, so that it will take?
    Any other suggestions?

    UPDATE
    Happen to have a QNAP NAS from work at the house which has Time Machine support and can select and initiate a backup there, no problem!
    So, it's something about the Mac Mini or drive? I didn't do anything to the Mac Mini in the process other than removing the USB drive and plugging it back in.
    As far as the drive, I dumped it and re-partitioned it with two partitions one for the Mini and one for the iMac. The Mac Mini is backing up to it locally, no problem.

  • Time Machine problem after restoring to a new HD (after my original HD failed)

    I am running Lion 10.7.5 on a MacBook Pro Late '11
    My HD was getting SMART errors, so I did a complete back up using Time Machine using a WD My Passport 1TB external, and then sent my MBP to Apple for HD replacement (under my Applecare plan).
    I collected it yesterday and restored my system using Time Machine (using the data from my external HD) and everything was restored perfectly, which was great,
    However, I'm now encountering a problem after plugging my external HD back into my MBP on the new system. Rather than Time Machine doing a swift 'top up' back up, it appears that TM is attempting to do a full back up. (I have 300GB and it took nearly 24hours to backup on the faulty drive) Is this normal after installing a new HD? Bearing in mind the Time Machine data is still on my external drive?
    It's also appearing to be taking FOREVER to do this entire back up again. It is stuck on 'preparing back up' and when I do get some movement, it's doing a couple of KB's at a time and with no genuine back up progress.
    Fundamentally, I just want to just top up my Time Machine back up without having do a complete back up, again. (which doesn't actually seem possible, viable at the min)
    Any help / support would be much appreciated

    AFAIK, it'll do that since the HD has a different UUID and the old TM backup won't recognize it. See Pondini's TM FAQs, for starters.

  • Does Time Machine reset after restore?

    Hello,
    Suppose I have Time Machine backups for the last 6 months on an external hard drive. Suppose I restore my entire system to 3 months ago using TM. Will Time Machine still keep all the backups that were made AFTER that date,  Or will TM treat that date that I restored to as the most "current" date, and delete all the backups created after it? What happens when TM starts to run again after restoring? I ask because I don't want to do anything that might cause any of my backups to be inadvertently deleted.
    Best,
    James

    It will keep the more recent snapshots.

  • Time machine freezes after restore using migration assistant

    after an erase/install done in an Apple Store, I restored my Mac Book from the Time Machine using the migration agent.
    To do this I created a temporary admin account and performed the Restore of all users and contents in the backup.
    Now logged in as my old user ID the time machine backup starts and identifies that the entire MacBook content needs to be backed up.
    TM Backup runs through the prepairing stage and reaches the "Baccking up 'xxx' MB from 'yyy' GB" message.
    Then it gets stuck after 120 MB has been backed up. I did run the backup for 2 entire nights in the 2nd night it got stuck after 0 kB had been backed up.
    What to I need to do to get TM running again?

    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    If all you see are messages that contain the word "Starting," you didn't clear the search box.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • Spotlight and Time Machine broken after restore/upgrade

    I've found a few similar threads to this but none of those solutions has worked for me.
    Two things happened at nearly the same time, so I don't exactly know the source of my problem:
    I upgraded my old MacBook Pro (approx. Oct 2010, 2.66GHz I think, 300GB-ish HD) from Lion to Mountain Lion
    The hard drive on my old MacBook Pro developed a terminal fault, so I had to buy a new one (8GB, 750GB HD) and restore a month-old Time Machine backup from my external drive.
    I can't remember whether my last Time Machine backup to my external drive was before or after I upgraded to Mountain Lion.
    Now I'm on OS X 10.8.2 on this new machine and I have two problems that seem to co-exist for a lot of other people too:
    Spotlight won't index: this is f***ing infuriating, I love spotlight and I use it all the time. When I first restored from the TM backup I think the old index restored with the backup as I did get a decent number of search results (both in spotlight and in MS Outlook), but new files didn't seem to get recognised. I tried adding my hard drive to the exclusion list and removing it again in an attempt to get it to rebuild the index, but all that did was wipe the old index without building a new one, so now I get no spotlight results whatsoever. I tried this solution and sadly it hasn't worked either. Basically I can't search for anything. Even applications (which I like to launch from spotlight) don't appear. All I get is "estimating indexing time", and it never gets any further.
    Time Machine won't back up: the first time I tried to backup my new machine it got a few hundred megabytes in before stalling; then a few hundred kilobytes in the next time I tried; and now it just doesn't get anywhere at all. The external drive I'm trying to backup to is recognised fine, I can see all the other files on it, and Time Machine seems to know that it's there, but the backup gets nowhere.
    There are reports of this kinds of crap all over the Apple Support forums, but no definitive answer, especially for 10.8.2.
    I could really do with some help on this. I need a backup before I screw another laptop, and I need spotlight to survive day-to-day life.
    Thanks,
    Craig

    Hi Craig - I had the exact same problem - I'm using an old early 2009 MacBook Pro upgraded to 8 Gb Ram, 1 TB internal Hitachi HD, 10.8.2 - tried the fixes suggested - got it to work with these steps- everybodies mileage is different but hopefully it works for you as well.
    a) I repaired disk permissions with Onyx (free utility)  and then  started  up with Command-R using Disk Utility to repaired/check the Volume (harddisk checked out fine but the volume needed some minor repairs )- Onyx repair disk permission seems to go deeper -had to reinstall some apps - don't know if this solved it-seems to bring it back to the default state - you might get away with doing all from Disk Utility (but starting up with  Command-R)
    b) restart from my internal hd
    c) downloaded the 10.8.2 combo update ( not the incremental shell update or whatever you call it which automatically gets installed with software update - combo update installs everything fresh from the .0 version)
    d) with  Onyx  I deactivated spotlight and erased the spotlight index
    d) restart
    e) started TM backup - prep took pretty long 30 minutes but then 450 GB got backed up in 6 hours to my external HD which is fast enough for me
    f) activated spotlight and 450 Gb were indexed in 9 hours or so
    g) for 2 days everything runs fast and very responsive
    best,
    Franz

  • Time machine bug after upgrading system

    Hello,
    I just upgraded my macbook pro from Lion to Mountain Lion.
    After this upgrade, I created a new admin account and tried to install back my previous account with my entire files thanks to migration assistant with a time machine data.
    Unfortunately, it seems that my 150go of personal data are in my hard drive after time machine'work but I can see my last account with my entire file. I have just the choice to loggin to my new ML admin account. Moreover, I can use some application with this new account but the fact is that I can found my important files.
    Do you have any solution in order to find my previous account?
    Thank you,
    Regards,
    Niels.

    See the pink box in Problems after using Migration Assistant for an explanation.  One of the workarounds in the green box (probably #4) should set things right.

  • Time Machine error after restoring all data

    Sorry, I've tried to run through various trouble shooting guides on Time Machine (notably here http://pondini.org/TM/C4.html etc) but haven't been able to work out a solution.
    I just had my iMac harddrive replaced and earlier did a full restore of the harddrive from my Time Machine backup drive.
    Time Machine, rather than deleting the old backups on the disk, is now giving me the error message
    "This backup is too large for the backup disk. The backup requires 564.63 GB but only 521.89 GB are available."
    I backed up to Snow Leopard 10.6.8. I just upgraded to Mountain Lion 10.8.3 because there were a couple of comments online that suggested that might help resolve the problem (unfortunately it didn't)
    It seems from articles I've read that this is a known issue that occassonally happens when a full restore happens and Time Machine can't associate the new harddrive with the old backups.
    One solution seems to be to use disk utility to reformat the external harddrive and start again, but that seems slightly like using a sledgehammer to smash a nut. Is there a less dramatic solution? Is there a easy way to just associate the two drives with one another again?
    Many thanks in advance for any help you can offer, and apologies if I've missed a relevant/ helpful thread somewhere else on the board.

    "Reconnecting" to your backups

  • How can I access old Time Machine backups after restoring from Time Machine?

    Just restored my iMac and I can only see "Now" when I enter Time Machine. How can I see all the backups and dates I had before I restored?

    While in Time Machine, press the key combination shift-command-C. The front window will show all mounted volumes. All snapshots should now be accessible. Select the one you want and navigate to the files you want to restore.

  • No permission to access my time machine backups after restoring.

    I reinstalled osx mountain lion on my macbook pro and restored my computer from a time machine backup. Now when I try to access my old backups time machine tells me that I have no permission to access those files. How can I regain access to my old backups?

    See Pondini's Tips, for starters.

  • Time machine full after restore

    Hi all
    I recently suffered the 'pleasure' of a HD failure in my 2008 24".  An apple engineer replaced the drive and reinstated my data from time machine - all good so far.  However, my mac doesnt want to relink with my existing backups and continue the save/delete old entries like before.  I can still access my old backups, but It seems to want to create a new time machine on the very little space i have left on the drive for new backups.
    Is there a way of relinking to the previous backup or is it a case of wipe/restart, which i'd like to avoid.
    Ta.
    Dezza.

    Hllo:
    Time machine will try to make a complete new backup as a result of the new drive.
    I would (I am not you) erase and format the external drive and let Time Machine make the new backup.
    Barry

  • Time Machine Backup after Restore

    I have been using Time Machine for months without a hitch. I also put some other files on the external that I am using for Time Machine. Recently I decided to sell my brother my old Macbook so I can get a new computer.
    I reinstalled Leopard on the macbook, erasing everything that was there before. I did not use my time machine backups because I only need a few files for my brother. Now when I connected the 500 GB WD USB external harddrive, it sometimes shows up in Disk Utility, but does not mount and I cannot access and of the files. What can I do, ALL of my files are backed up here?

    Try right clicking on it and mounting it.

  • After clean install of Snow Leopard, Time Machine did not restore all files.  When I try to restore these files I get "Not enough disk space" error.  What do I need to do to get these important files back onto my Mac from my external hard drive??

    After clean install of Snow Leopard, Time Machine did not restore all files.  When I try to restore these files I get "Not enough disk space" error.  What do I need to do to get these important files back onto my Mac from my external hard drive?? 

    Janet.b wrote:
    About 3 years old...pretty dated now I guess.  Am thinking I may just need to have it upgraded by a Mac tech.
    For what the Apple Store's charge you can buy almost buy a new computer.
    Just for giggles I brought my old laptop in for a drive upgrade and asked, they wanted $600 for a drive that only cost $120 at the time and it was a slow 5,400 RPM drive. The new Mac's of a similar make were going for $1000.
    I did the drive replacement myself, got a faster drive of better quality for $300 instead.
    Then another time I asked for a RAM upgrade from 4GB to 8GB, they wanted to charge $400 + $35 for the labor.
    The same RAM is on Crucial.com for $90 and all I need is a 00 micro phillips screwdriver.
    So you see what's going on here.
    I think what you should do, if your out of warranty/AppleCare, is to call up the local PC tech guy who also does Mac's and have them fix you right up.
    They can offer more personalized care which you need. Clone your old drive to the new and everything.
    With Apple they are overworked at the Genius Bar and just place roadblocks so you buy a new machine instead.
    For instance, all new iMac's now have proprietary drive software installed on the hard drives for heat monitoring. So now the only choice a user has is to bring their iMac into a Apple Store for a very expensive drive upgrade, which a person then decides the money is better spent buying a new machine.

  • Had to restore my iMac from Time Machine. After the restoration all programs are functioning except my Adobe Creative Suite 4 Design Premium. When I start any program in the suite the error message, "Licensing for this product has stopped working." I rest

    I had to restore my iMac from Time Machine. After the restoration all programs are functioning except my Adobe Creative Suite 4 Design Premium. When I start any program in the suite the error message, "Licensing for this product has stopped working." I restarted the computer and tried again to run Photoshop and the same error message appeared. The message was followed by a message that stated that I needed to contact Adobe technical support and mention Error: 150.30. I need Adobe technical support to provide me a solution for my problem so I can continue using my Adobe products installed on my computer.

    Unfortunately when Adobe products are restored from backup, especial CS4 and especially Mac, it breaks licensing.
    There is a python script included in the license recovery kit that should work if you are familiar with Terminal.
    If not, you must reinstall your CS4 suite.  You don't need to delete your preferences, so it should be the same as before.
    Error "Licensing has stopped working" | Mac OS
    Gene

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

Maybe you are looking for