Why Does Time Machine Corrupt Files It Restores?

Time Machine does not restore MS Word files and documents correctly. In the case of a play I am writing, the formatting is completely off and there are unusual symbols appearing which are not in the original document. In trying to restore FileMaker files and documents, I found that I cannot even open the document. A window displaying the title appears and that is all. This renders Time Machine useless.

The reason is that it has corrupted itself.
See http://pondini.org/TM/C13.html
TM over wireless and with Yosemite.. is corruption in a box.
I did not need to do this with the previous Time Capsule.
I think it is more the OS at issue than the TC.. but certainly poor setup of the TC matters.. you have to have very good wireless connection single hop.. no double repeater stuff. Anytime TM stops or fails half way through a backup it is likely to corrupt itself.

Similar Messages

  • HT201250 Does Time Machine delete files in back-ups that are deleted on my Mac?

    Does Time Machine delete files in back-ups that are deleted on my Mac?  IOW....if I need to restore a whole back-up, I don't want to restore previously deleted files.

    Does Time Machine delete files in back-ups that are deleted on my Mac?
    Not immediately. When space starts to get tight, Time Machine will start to delete the oldest file(s) to make more room, but this won't occur for some time.
    if I need to restore a whole back-up, I don't want to restore previously deleted files.
    You won't if you choose to restore from a backup that occurred after the date that you deleted the file.
    If you absolutely do not want to keep the file in your Time Machine backups at all, you do have the option to go into Time Machine, find the file, and manually delete all versions of the file from past dates.

  • Why does Time Machine disappear?

    Why does Time Machine disappear each restart?

    Suggest that you power cycle the entire network, as things are likely out of sequence
    Power every device off on the network, order is not important
    Wait a few moments, then start the modem first and let it run by itself for 2-3 minutes
    Start the Time Capsule the same way
    Start each network device one at a time about a minute apart
    Check for proper operation

  • Why is Time Machine displaying files only in the present not the past?

    Hi,
    My PowerBook G4 recently had its Logic Board replaced. Since Time Machine identifies the machine to backup thanks to its MAC Ethernet address and, since after a Logic Board switch my MAC Ethernet address had changed, I had to reconfigure TM so that the external hard drive reassociates with the new MAC Ethernet address and continues to backup in the same backup folder. For that I used this hint posted on MacOSXhints.com :
    http://www.macosxhints.com/article.php?story=20080128003716101&query=time%2Bmach ine%2Blogic
    While performing this hint enabled me to have my new backups in the original backup folder, and access all my backups through finder, I cannot view any backups in Time Machine star-field mode. Whenever I click on "Enter Time Machine" I correctly warp into the star-field, but I only see the present. I cannot go back in time and the time line on the side doesn't show any dates in the past. The finder window at the front displays only what is currently on my PowerBook HDD, and the finder windows that precede it are all dark grey, empty and un-clickable. What is peculiar is that when I click on Time Machine Preferences, the Panel can show the date of the oldest backup.
    To sum up: Time machine has no problem backing up my files in the original backup folder of my external HDD (I can see all my new backups in the same backup database folder as the ones before the Logic board switch), I can access all my backed up files via Finder, but when I enter Time Machine star-field mode, it doesn't show me any of my backups. I really like the ease of use of the star-field mode, and I find it frustrating to have to look at my backups in plain old Finder.
    What I don't know is whether hint I described above might have introduced errors that provoked the error or whether this might be due to the fact that while my computer was going for repair, I connected the external HDD containing my backup with two computers running Mac OS X 10.4 to retrieve some backed up files.
    My case must probably be quite rare, but since I haven't found any solutions to this date, I'm posting it now.
    I would be extremely grateful if anyone had a solution for this, or an intuition on the different parameters to modify to correct this Time Machine problem. Any contribution will be helpful. Thank you very much.

    gbullman,
    You say that the logic board was replaced? Then you will not be able to continue backups to the SAME backup set.
    *_Time Machine Always Performs a Full Backup After a Full Restore_*
    Actually, this is normal. Anytime your hardware has changed, or you have reinstalled the operating system again, Time Machine will perform a new full backup.
    *Full Backup After Restore*
    Bear in mind that in all cases Time Machine will perform a full backup after a full restore. This is normal. Time Machine will resume incremental backups after the full backup has completed. To view previous backups, Control-click or right-click the Time Machine icon in your Dock or Option-click the Time Machine menu extra and Choose "Browse Other Time Machine Disks," then select your previous backup volume. You will enter Time Machine and be able to browse your previous back ups and restore files. [http://support.apple.com/kb/TS1338]
    So even on unchanged hardware, if you reinstall your system software and restore your user data, Time Machine starts anew, and you will not be able to resume backing up with the same history as the previous backups.
    While there may be ways to fool/hack Time Machine into recognizing previous backups without performing another full backup, they are likely rather elaborate. Ultimately, though, in a couple of months, all the effort to preserve old backups may seem pointless. After all, Time Machine will eventually purge away that data anyways as it replaces it with new files.
    It may simply be easier to begin a fresh series of backups while saving the previous backups until your satisfied that you have enough history built up. Then delete the old backups.
    *Why Can’t I Resume Backups?*
    You see, Time Machine was designed to restore your Macs’ immediate environment in case of system crashes or accidental deletion of user files. As a result, reinstalling your Mac OS system software or changing your hardware requires a fresh set of backups since older backups would not accurately represent the current state of your Mac.
    Additionally, if a user has had to reinstall the system software, then resuming backups to the same set could later reintroduce the very issues that forced the reinstall in the first place. Furthermore, maintaining backups that were started with an older Mac, introduces the possibility of restoring system files that were never intended for the new Mac.
    If you require long-term archival storage of files, then you need another backup strategy.
    Hope this clarifies some things.
    Cheers!

  • Does Time Machine track file movements?

    If I have a file on my desktop, have Time Machine back up the desktop, and then move the file to my "Documents" folder and back up again, does Time Machine back up two copies of the file in each respective location or does it know that the file was moved (without being changed) and only keep one copy on the backup drive and just make a new hard link to the file in the new location (in this case the "Documents" folder)?

    if you move a file to another location, TM will think that it's a new file provided that it sees the moved file during a regular backup.
    If you move a file around BETWEEN backups, it will NOT find the intermediate locations.
    - gws

  • Why does Time Machine folder sizes exceed physical capacity?

    I have a MAC G3 Server Serving multiple MACs as a Storage, Media Server, and Time Machine storage. These other external MACs are all running Version 10.8.3. Only the Storage server is running 10.5.8.
    All of the extenal Macs use Time Machine to backup to the served Storage media volume called "Time Machine".
    The physical size of the "Time Machine" volume is 2.0 TB.
    Yet when I am on the G3 Server, and perform a "Get Info" on the "Time Machine" volume, and also the folder that contains the Server's backups, the stored capacities exceed the physical capacity of the drive to which the volume resides.
    The single physical drive is 2.0 GB and only has one partition called "Time Machine". In the root directory of this volume there is the one folder called Backups.backupdb, and a .sparsebundle DMG file for each of the remote systems that are bing backed up by Time Machine.
    Each of the sparsebundles are well below the dirve's physical capacity, but both the local server's backup folder (Backups.backupdb) and the G3 server's local volume "Time Machine" show a used capcity that well exceeds the physical capacity of the drive on which it resides.
    For example, here is the information from "Get Info" on the Backups.backupdb folder on the "Time Machine" volume when viewed from all systems:
    Kind: Folder
    Size: 3,456,930,478,415 bytes (3.46 TB on disk) for 122,254 items
    But the Physical Volume "Get Info" shows this:
    Kind: Volume
    Capacity: 2.0 TB
    Available: 169.92 GB
    Used: 3,456,930,478,415 bytes (3.46 TB on disk) for 122,254 items
    (NOTE: this is identical to the size
    My guess is that there is some sort of deduplication involved.
    If so, I would like to know the type of deduplication is performed?
    Is it File Level deduplication, Block Level, or Content Level?
    Also, is the deduplication inhererant on the volume (File System) level, or only specifically for Time Machine, via symbolic links?
    Thank you in advance.
    Jeff Cameron

    This is due to the way Time Machine stores files. While there is only one copy of each version of each file stored, there are multple links to that file, and each link is reported in Get Info at its restored size.
    How Time Machine Works its Magic

  • 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 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 does time machine back up when no new files have been added?

    I run time machine manually and even after having just back up, it says it is backing up 50mb of something.  Nothing has been added or taken away.  It just keeps adding and using up disk space.

    System files are constantly changing, TM backs the whole machine up not just the files you are working on,
    And 55mb is small change

  • Why does time machine go back less than a month?

    clearly, i'm doing something wrong...
    i'm in the process of cleaning up stuff from my external drives.  sometime in the fall, i switched my time machine backup to a larger drive.  i did my best to follow the instructions for transferring over a time machine backup, and it didn't work.  i still have the old TM database, but time machine wouldn't recognize it.  so i lived with it and got on with my life, starting a new TM backup.
    today, i just realized that it goes back less than a month.  what is THAT about?  before you ask, it's NOT a disk space issue.  on a 2 TB drive, i currently have 1.23 TB of available space.  there's plenty of ROOM for further backups, but it's just not keeping them.  please help... i love time machine, and it's saved my bacon on a number of different occasions.  but on many of those occasions, i had to go back quite a bit further than 3 weeks to restore what i needed.  if that's all i'm going to get from time machine, it's usefulness to me is slashed by about 80%.

    Time Machine automatically deletes older snapshots to make room for new ones. If your backup history is shorter than you expect, it may be because you're backing up one or more large files frequently.
    Virtualization software such as VMware, Parallels, or VirtualBox creates a large virtual-disk container that is constantly changing, so it has to be backed up every time Time Machine runs. That will quickly fill up any backup destination.
    You should exclude the virtual-disk file(s) from your Time Machine backups. To do that, click the Options button in the  Time Machine preference pane. You may also be able to do it in the virtualization app's settings. Back up the files on the virtual disk from within the guest system, using a native backup application.
    A compromise solution is to create a "snapshot" of the virtual machine in the virtualization software (not a Time Machine snapshot.) That will give you a single large file that never changes and only has to be backed up once. All the subsequent changes will be stored in a new file that's initially much smaller, but will grow over time. You should still exclude that file from TM backup. If you ever need to restore the VM from Time Machine, you'll have a working setup, which will make it easy for you to restore the rest of the data from within the guest system.
    Another common cause of large TM snapshots is native OS X disk images. If you store a lot of data on one or more writable disk images, they should be in "sparsebundle" format, which will be backed up much more efficiently than any other format. A sparsebundle will not be backed up at all while the image is mounted. Make sure you unmount the image often so it can be backed up. Consider eliminating large read/write disk images from your workflow, if possible.

  • Why does Time Machine not work over wifi but only via ethernet cable ?

    Hi everyone,
    It's been some time I have this problem now.
    The first time I backed up my mac within Time Capsule with time machine, I chose to use the ethernet cable because the gigabit connection is much faster than the wifi for the first back up, but now, any time I want to update this back up, I need to connect the cable, cause "Time Machine can not connect to the Drive I picked" over wifi.
    This is so annoying. Does anyone have a similar issue ?
    Any solution ?
    When I got this "error" I can use Utility Airport and get full access to the drive, even in finder. The only thing that doesn't work is TimeMachine connecting to the drive, even if it is detected by TimeMachine itself.
    Thanks.
    Riccardo

    Typical Yosemite.
    I suggest a full reconfigure of the TC.
    Follow this list..
    No files are deleted on the TC doing this although you might have to repoint your laptop to the backup.
    Note.. even if TM does connect it will say it is going to do a new backup.. it is only when it starts that it discovers the backup exists and increments it.
    Start from a factory reset. No files are lost on the hard disk doing this.
    Factory reset universal
    Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
    N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
    Setup the TC again.
    Then redo the setup from the computer with Yosemite.
    1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
    eg TCgen5 for basestation and and TCwifi wireless name.
    If the issue is wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round. ie plan on a first and second round of changes to fix this.. hopefully.. I will point out other steps that can be round2.
    2. Use all passwords that also comply with 1. but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
    3. If the TC is main router you can skip this point. This is only an issue when the TC is bridged.
    Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking.
    4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
    5. Mount the TC disk in the computer manually.
    In Finder, Go, Connect to server from the top menu,
    Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
    You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
    However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
    6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only. Do the same for ethernet if you use it.
    There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
    You might need to do some more work on the computer itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
    Tell us how you go.
    Someone posted a solution.. See this thread.
    Macbook can't find Time Capsule anymore
    Start from the bottom and work up.. I have a list of good network practice changes but I have avoided Yosemites bug heaven.
    Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
    http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

  • HT204057 Why does Time Machine no longer support external hard drives connected to an Airport Extreme base station?

    I'm pretty sure that upto a few months ago I had a hard disk connected via USB to my Airport Extreme and I was able to backup all the computers on my home network. However, somehow over the last few months this had stopped happening. I am not able to select my network disks for time machine backup.
    There is a very unhelpful sentence on Apple's website which simply says it does not allow backup to hard disks connected to Airport Extreme via USB. Does anyone know why this is? Is there a way around this? Can I connect a drive to my desktop computer and have other computers backup through the network to that?

    This was never an approved configuration: OS X Mountain Lion: Disks you can use with Time Machine
    Can I connect a drive to my desktop computer and have other computers backup through the network to that?
    The above KB article indicates you can, though I have not personally tried it.

  • Why does time machine make a second/different backup after new installing a hard drive?

    Hi all,
    Long time reader, first time poster...
    after having to install a new hard drive on my MacBook Pro, the new Time Machine backups are not recognising the original/older backups on the external hard drive connected via network router and has created a new/second backup caller 'xxx Mac Book Pro 1' instead of updating/reading the orginal 'xxx Mac Book Pro backup'?
    Does anyone know why it did this? and more importantly how do i make it recgonise the original and stop making the secondary copy?
    Thanks!

    Hi gb69,
    If you are having issues with Time Machine backups after a recent hardware change, you may find the following article helpful:
    Time Machine: Troubleshooting backup issues
    http://support.apple.com/kb/ht3275
    Regards,
    - Brenden

  • Does time machine delete files that you delete on hard drive

    On my mac HD I have files "A", "B" and "C". Time machine has backed them all up. Later, I decide I don't want "B" on my mac HD anymore. Does this data get deleted on time machine as well? If not, is there an easy automated option to do this?

    Jason,
    While it is not automatic, you can still remove said file from the backup quite easily (there is consideration for doing so). Open Time Machine, navigate back to a point where the unwanted file exists, select it, then choose "Delete from all backups" in the "Action" menu (looks like a gear).
    Scott

  • Why does time machine back up change root directory of software?

    about a year ago i did a time machine back up of my old macbook pro, then when i came to use a piece of software (native instruments-traktor) it said the root directory had been changed and it couldnt find the file. i had to remove the whole program from my mac and redownload it. then since then had no problems.
    now ive just purchased a new macbook today and wanted all my old files and software on it so i did a migration expert with time machine. it seems to have bought most things over.....a few files are missing from logic but again when i went open traktor, again it said root directory changed,,,im not to good with these root directorys so havent got a clue what to do so again ive had to remove the program and redownload it which is a bit of a pain.
    any ideas why time machine changes it??

    I'm also puzzled because it continually wants to back up some 15MB or more when I've changed nothing
    Suggest that you download and install BackupLoupe to find out exactly what is being backed up on each pass.
    soma-zone: BackupLoupe
    If you want to change the backup frequency of Time Machine, an application like Time Machine Editor will allow you schedule backups whenever you like. But, you may not need to do this if you can figure out what might be causing the first issue.
    TimeMachineEditor
    If you ever decide to delete Time Machine Editor, be sure to change the backup frequency back to hourly before you delete the application.

Maybe you are looking for

  • How to restrict Internal Order master data changes

    Hi Experts, We have internal orders that have no Functional Area assigned to it at the beginning of the month, but part way through the month a change is made to the master data and a Functional Area gets assigned to the internal order.  When settlem

  • Issue with Mail and limited account rights

    Has anyone else noticed similar problem as I did: When you don't have permission to create new mailboxes to root of an mail account and then turn on automatic moving to Junk folder, and saving of sent messages on server, it just discards all Spam-mar

  • Ipod Service Failed To Start!!!!!!! Grrr!

    Hi Everyone.. Well, I have been at trying to sort this out ALL day and I still haven't managed to figure it out or find a solution! I have tried every troubleshooting method I could find to get my ITunes to recognise my Ipod and I am now stuck on thi

  • I am having

    trouble finding a LabView driver for the waveform generator AFG 5101. I am trying to revive some old code written 5 years ago with LabView version 3.01 and the driver listed on National's website does not seem to work with this program. Thanks in adv

  • Why doesn't the stroke width tool create smooth curves?

    Am I the only one who has edited a stroke with the stroke width tool, then outlined the stroke only to find a countless number of points and noticeably unsmooth edges? Is there a setting or certain way to ensure that the stroke width tool won't corru