Does time machine identify any file replications?

Hi all,
I am wondering whether anyone knows more about this, looked into this.
- I know that time machine does use links to ensure that files that belong to multiple snapshots (successive snapshots)
  are not backed more than once.
However, recently I had to reset my Mac (MacBook Pro) from 10.7.5 to 10.7.4, because there were problems in operation.
(actually with time machine and Spotlight, but I do not think, this is the issue here).
I simply reinstalled the version from about two weeks earlier - in the meantime there were not a large number of changes.
However, the next time the backup was about 80 GB.
This made me wonder under which conditions does TM actually identify a file that it has already backuped before
and it does only need to link it and not back up it up again:
only if it is at the very same position and it has no modified change date (of course also no content change)?
     - this would mean the complete system actully would have been backuped again - not nice, but would roughly fit the size.
or are there more conditions?
It also seems that any files that are moved lead to a replicate backup. - the file at the new position is treated as a new backup.
Also if temporarily some location was excluded from the backup and then the exclusion is removed, it seems the next backup contains
an all-fresh replica.
In these and many other cases, a lot of space could be gained, if multiple occurances of files would be treated as a single file with
a hard-link in the backup.
a) It seems this is in no way addressed by TM
b) It seems that this might be compatible with the way TM manages backups. (files can be hardlinks)
Thus, does an utility exist, which is able to identify such copies in a backup and replace the identical copies by a single
copy with hard links? Does someone know more about the inner management of TM-backups? Could this approach work?
I know that this is not directly supported by TM, but I am just curious whether something like this exists, it seems to me
that due to my restoration and the way I handle data (e.g., put everything for working on the desktop - later move it to the
final destination), there would be very many opportunities to thus compress the size of TM-backups.
Cheers
Klaus

It says it will notify you after a backup is deleted. That's the only option available. You will have to open the TM backup and see where the file dates you wish to keep are and manually track them if you need TM to store files you deleted from your current system.
If you delete a file from your current system that you need to keep long term, then I wouldn't rely on a TM backup to store it. You should either keep it on the computer and you will always have a TM backup. If you need to clear space on the computer, you should back up important files to another location such as a flash drive or external drive.

Similar Messages

  • Does Time Machine backup system files (/usr/local/*)?

    Does Time Machine backup system files (/usr/local/*)?
    If so how do you locate them in the Time Machine interface?
    If I go into Time Machine mode and type say "/usr/local" in the Time Machine search bar I get nothing although I can open a terminal application and cd to /usr/local and see bin, lib, include, etc.
    Of course I can never see /usr/local in Finder either ... only at the command line.
    Thanks.

    John, another tech pro ("baltwo") suggests:
    Run this in the Terminal:
    defaults write com.apple.finder AppleShowAllFiles 1
    OPTION-click and hold on Finder's Dock icon->Relaunch which reveals all hidden files. Then, look for that file and delete it. To hide all of those, use the same command, substituiting zero for the one, and relaunch the Finder.

  • Does Time Machine Compare/Verify Files?

    I have typically performed manual backups, and have no experience with Time Machine.
    Does Time Machine COMPARE / VERIFY that the backup files match the originals?
    I used to use Retrospect for Archive/Backup, which logged an alert if there was any mis-match in the backup process. Now I tend to backup files simply using Drag/Drop copying to redundant external storage devices. I have recently encountered errors in this process when backing up larger amounts of data. Hopefully this will not occur using TIme Machine. 
    What does Time Machine do if there is an error in the backup process?
    Is Time Machine the most reliable solution for Archive/Backup?
    thanks

    Time Machine logs to the system.log as process com.apple.backupd, which you can access via Appplications -> Utilities -> Console
    Carbon Copy Cloner logs to a CCC.log which you can access from within CCC, or via Applications -> Utilities -> Console.
    CCC will popup and error if there is backup problem.
    SuperDuper has its own built-in log, that you access via SuperDuper.
    SuperDuper will popup an error if there is a backup problem.
    CrashPlan has a /Library/Logs/CrashPlan/ directory with backup logs.
    CrashPlan can send you an email if there is a backup problem. Even better, it will tell you if a backup has not completed within the last 3 days.  I find that very nice in that automatic backups that stop and you haven't noticed it, is more annoying than not having a backup verification.
    I also remember Retrospect.  And the verify taking longer than the backup is a good excuse to just make another backup using a different utility and media destination.

  • How does Time Machine handle alias files on the backup volume?

    I have been trying to find some info on how Time Machine handles alias files on the backup volume, but can't find anything on that topic. Neither here in this discussion or at the Apple support pages.
    My concern is if an alias file on the backup volume is backed up »as is«, or if it is resolved and the original file is backed up? The last would be most annoying as this will make the size of the backup much larger.
    Even though I do not know of folders having been renamed (which will cause that folder and all its content to be backed up again) Time Machine often backs up a surprisingly large amount of data, so I suspect that alias files could be resolved.
    Any info on this will be appreciated.

    Alias files are NOT followed, AFAIK.
    For more info on how TM works, see this ars technica review.
    Good luck!
    Message was edited by: joshz

  • Does Time Machine replace changed files and delete old files?

    I haven't upgraded to Leopard yet, but my son is a NEW CONVERT to the Mac; has uses Dells for years. He has a new Macbook Pro with Leopard. I use SuperDuper! with my Tiger Mini Mac.
    I don't understand what Time Machine does. Does it continually update files on the target device, and if so how does it handle deleted and renamed files on the source device.
    Thanks.

    Time Machine takes a snapshot of the drive it is backing up every hour. If a file is new, renamed or modified since its last backup, Time Machine will make a physical copy of that file. To conserve drive space Time Machine will only make hard links back to its previously backed up files for files that exist on its source drive which remain unchanged. Hard links work in a somewhat similar fashion as aliases. If a file has been deleted Time Machine won't make a copy or hard link. You can read about how hard links work in Time Machine in this Ars Technica review.
    http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/14
    If a file is not on the hard drive for over an hour and is deleted before Time Machine makes its hourly backup that file will not be in any of Time Machine's backups.
    Time Machine only retains the first hourly backup of the day as its daily backup. The other hourly backups get deleted in the course of the day. That means that to be retained in the daily backups a file must be on the hard drive for over a day or be physically present on the source drive for the first backup of the day.
    After a month, Time Machine retains the daily backup made on the same day of the week as the initial backup as its weekly backup. If a file is on the source drive for less than a week and is not in the daily backup retained as the weekly it will end up being deleted when Time Machine thins its daily backups.
    When the Time Machine volume fills up, Time Machine will start deleting its earliest backups to make room for new ones.

  • Does time machine backup open files that I am currently working on?

    Will time machine backup files that are open? I have a quickbooks file or others that sometimes will be open for as long as a week. I was having problems with a file I was working on that had days worth of data that I had been changed. When I tried to restore a file with time machine, I had to go back a week. All my changes were lost. I assumed that time machine would be backing up a file even as I was working on it. Maybe not? Can find very little info anywhere. Yosemite 10.10.1

    I don't believe it does. I know that there was an issue in the past where it wouldn't back up any of the iPhoto Library if iPhoto was open. I don't know if that was fixed. But, like you, I can't find anything else to verify my suspicion.
    If the program supports Auto-save and Versions, then you would be able to go back through the versions, but I don't think QuickBooks would support that.

  • How does Time Machine handle large files?

    I'm relatively new at the whole Time Capsule / Time Machine process and have learned that large files (eg aperture library) are backed up each time there is a change and this can lead to the TC filling up quicker than normal.
    How does this work with daily and weekly backups?
    For example, if my aperture library is, say 1Gb and I import a load of photos from my camera and this goes up to 2Gb. I've learned that I should disable time machine while I'm in Aperture (or at least before 10.6...not sure now). So given I've done that, imported the files to Aperture but want to edit them later and ultimately move them into iPhoto to keep the Aperture album small.
    When I turn back on Time Machine, the next hourly backup will know the library has changed and will back it up, this will go on until a day backup has been taken - this deletes the 24 hourly backups? or does it merge them?
    If I then do the editing the following week, then export the photos and the library is now back to 1Gb again....backed up hourly/daily/weekly etc what am I left with??
    Do I have an original, the 2GB version and the new 1Gb version...ie 4Gb......is there a cunning way I can work to change the files within a week so only one of the changes is in the backup?

    Orpheus999 wrote:
    When I turn back on Time Machine, the next hourly backup will know the library has changed and will back it up, this will go on until a day backup has been taken - this deletes the 24 hourly backups? or does it merge them?
    The Time Machine panel of System Preferences says this:
    Time Machine keeps
    - Hourly backup for the past 24 hours
    - Daily backups for the past month
    - Weekly backups until your backup disk is full
    Each time Time Machine runs it creates what appears to be an entirely new backup set, although it does this in a way that doesn't require it to copy files that have already been copied. So merging isn't necessary. Another effect of how it operates is that each unique version of a file (as opposed to packages of files) only exists on the backup volume once.
    According to the contents of my Time Machine backup file, hourly backups are literally kept for 24 hours, not until the next "daily" backup. For a "daily" backup, it seems to keep the oldest "hourly" backup for a day.
    If I then do the editing the following week, then export the photos and the library is now back to 1Gb again....backed up hourly/daily/weekly etc what am I left with??
    Do I have an original, the 2GB version and the new 1Gb version...ie 4Gb......is there a cunning way I can work to change the files within a week so only one of the changes is in the backup?
    You might be able to exclude those files from being backed up at certain times, but I can't be sure this would result in older copied of those files being retained.

  • How does time machine handle deleted files

    I've recently grown into a 1.5TB external hard drive where I back up my iMac through Time Machine. I'm a photography hobbyist who does a lot of processing work on my photos in Photoshop, therefore I'm regularly generating sizable data to back up.
    My question is, using some hypothetical numbers:
    Pretend I create 50GB of new data by importing a lot of photos onto my iMac, then Time Machine does it's thing before I can decide what photos I want to keep or trash. I later go back and edit my photo catalog and decide I only want to keep 1/2 of photos from that previous import, reducing that data to only 25GB. Will Time Machine keep those old pictures on my external drive, even though I deleted them from my iMac? Will Time Machine ever recognize I threw away those files, assume I don't want them, and overwrite them? Or is Time Machine going to keep using my my external drive to back up everything until I used up all of the externals space?
    Message was edited by: Michael Streubert

    Understanding how TM deletes things can be difficult, but I'll try to summarize it:
    -TM will back up your system every hour.
    -After 24 hours, TM will delete all but one of the 24 previous hourly backups. The one it decides to keep will become your "daily" backup. You have no control over which of those 24 backups it will select to keep as the daily.
    -After 30 days, TM will start to delete the old daily backups too. It will keep 4 of the last 30 backups, one for each week.
    -After your TM disk fills up, it will start to delete old backups to make room for new ones.
    So, after you delete them from your main HD, the length of time that they kept on the TM drive can vary. If the files existed for only a few hours, then there is a good chance that they will be purged from the backups the following day. Or they might be kept for weeks or months, depending on if TM decided to keep those backups as the daily or weekly. It's kind of a crap shoot.
    If the files existed on your main hard drive for between one and seven days, then they will remain on your TM backup drive for at least a month. After that they are at risk of being purged out.
    If the files existed for more than a week, they will stay on your TM drive until it fills up. After that, they are at risk of being deleted.
    I hope this helps.

  • Does Time Machine Copy UNCHANGED files over and over??

    Okay, it seems to me that whatever files I have selected for backup are copied by Time Machine EVERY SINGLE TIME it backs up my Mac, instead of just when I make changes to them. Is that correct? If so, that just seems to be a massive waste of space on the external hard drive, and is probably the reason my 1TB drive runs out of space so quickly.
    For example, I don't need 50 copies of my iTunes Library. I just need ONE copy. Time Machine should back up the music files ONCE, and if I add more songs to iTunes, it should then detect it and backup JUST the new files. Same thing with a Word document or whatever...make ONE copy of the file and then if I ALTER the file, make a copy of the ALTERED FILE.
    Am I making sense here or is this just wishful thinking? Is there a way to make these types of adjustments in settings that I am missing?
    Thanks!

    Shugama wrote:
    Okay, it seems to me that whatever files I have selected for backup are copied by Time Machine EVERY SINGLE TIME it backs up my Mac, instead of just when I make changes to them. Is that correct?
    no, that's wrong. that would indeed be a huge waste of space. TM only backs up afresh new and changed files since the last backup. everything else is *hard linked* to existing backup copies. read up on what a hard link is.
    http://en.wikipedia.org/wiki/Hard_link
    that's why incremental backups take very little space and yet every single TM backup is a full and completely independent copy of your system at the backup time. and that's why you can have a lot of TM backups fit on your backup drive.
    If so, that just seems to be a massive waste of space on the external hard drive, and is probably the reason my 1TB drive runs out of space so quickly.
    For example, I don't need 50 copies of my iTunes Library. I just need ONE copy. Time Machine should back up the music files ONCE, and if I add more songs to iTunes, it should then detect it and backup JUST the new files. Same thing with a Word document or whatever...make ONE copy of the file and then if I ALTER the file, make a copy of the ALTERED FILE.
    Am I making sense here or is this just wishful thinking? Is there a way to make these types of adjustments in settings that I am missing?
    Thanks!

  • Does Time Machine backup open applications/files?

    I recently lost my calendars (in Entourage, Ical, Mobileme, etc.), and wanted to restore from a time machine backup.
    I tried to restore the Entourage identity from a day or two before only to see that the date in Time Machine for the file was way old.
    I suspected that because I leave the app open all the time, particularly all night when my backups run at 11 pm that the file never got backed up. Does this sound right?
    Ical, on the other hand (which is synched to mobile me and entourage), even though I rarely open it and use it, seemed to have the updated data.
    How does Time Machine deal with files that are in use?

    Entourage needs some special handling. I don't use it, so can't tell you exactly how to do it, but if you search this forum for Entourage you should find a post or two (by Kappy and/or Baltwo, I think) with good advice.

  • HT201250 Every time I add/delete music to itunes, does time machine backup my entire library?  If so can I limit backup just to added music?

    Usimg time machine-every time I add/delete music in itunes library does time machine backup entire file? If so,an I set it up to just backup added music?

    It shouldn't be backing up the whole thing again, just the changes.

  • Time machine and hidden files

    Hi all
    Apples old Backup software didnt backup hidden files (which i think really *****), but the question is does Time Machine backup hidden files as well?

    The best way I have found to restore hidden files using Time Machine is to download the "HiddenFiles" widget from the widgets downloads here:
    http://www.apple.com/downloads/dashboard/developer/hiddenfiles.html
    Once you have hidden files enabled, then they also show up in Time Machine, and appear to restore just as easily as normal files
    Steve
    (a recent switcher feeling somewhat chuffed at his findings)
    Message was edited by: stevesant

  • HT201250 What files and directories, if any, does Time Machine automatically exclude?

    Does Time Machine automatically ignore any files that aren't displayed in the Preferences>Time Machine>Options exclude list?

    That is not entirely correct: TM does exclude some items. To see the complete list: in Finder's menubar select Go -> Go to Folder.... and type in this path (followed by [return]:
    /System/Library/CoreServices/backupd.bundle/Contents/Resources/
    In the window that opens, select "StdExclusions.plist". You can see what's in it with any text editor.

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

  • Does Time Machine Ever Delete All Traces of a File?

    I have a question.  I have read up on Time Machine on various articles, posts, and documents across the web and I am having a hard time understanding exactly how time machine deletes files.
    When a disk is full, does Time Machine ever make the decision to delete the last copy or version of a file, therefore completely erasing it off the disk forever?  I know that Time Machine deletes older versions of files, but will it ever completely delete the last, final backup of a file to make space?  If so, I can't imagine using Time Machine as a true piece of backup software.  It seems like it would be useful in restoring your computer in an emergency, but as far as backing up files, it seems that it would be catastrophic, because it may choose to delete the last remaing version of a file to make space and you end up losing that file for ever.
    Here is an example:
    I create a file X.doc
    Time Machine backs it up.
    I modify X.doc
    Time Machine backs up the copy, keeping both the original and the new copy on the backup drive.
    I modify X.doc yet again.
    Time Machine drive runs out of space. Time Machine deletes the oldest version of X.doc and backs up the new copy.
    I create 10 more files unrelated to X.doc
    Will Time Macine remove all remaining versions of X.doc to make space for the 10 new files???
    I hope I am making sense.

    Derek Doublin1 wrote:
    Will Time Macine remove all remaining versions of X.doc to make space for the 10 new files???
    The worst TM can do is delete all your older copies of files, not the most recent version.
    If the drive is full, then it can't accept any more files period.
    If you had a full 100GB boot drive and a 100GB TM drive, the TM drive would be a copy of the boot drive with no room for saved states.
    If you changed a file on the full boot drive, then TM updates that file on it's full drive, there will be no copy of the previous version of that file.
    TimeMachine makes for a poor pernament backup system, because lets say you do a major files addition to your boot drive, TM backs that up and can go ahead and delete files you realized you accidentially deleted just a few short days ago.
    It's better than nothing and works ok for newbies, but more seasoned types use many backup methods in addition to TM, because corruption creep is possible with TM as well as malware as it's hooked up so often, in a lot of cases all the time.
    Most commonly used backup methods

Maybe you are looking for

  • Associative Array our only option?

    Hello, I'm having a problem accepting associative arrays as the only option I have for getting data from a stored procedure. I have a good reason for not wanting to use ref cursors as I am using the stored procedure to manipulate data which I in turn

  • How do I delete a lot of old photos from my iPad at the same time?

    I have a 64Gb iPad and I have filled it with photos from past holidays.  I want to delete them so that I can store photos from this holiday.  I import photos from my digital camera to inspect, edit & share while I am away, but load them in a separate

  • Apply profile to AnyConnect Secure Mobility Client 3.1

    G'day Gurus, I have created a profile for Network Access Mnaager using Standalone version of Profile editior. May I know the steps to deploy on end node? Cheers, Ahmed.

  • Jmf simple code

    Hi all, this is my simple code that plays a video from a specifed location. * To change this template, choose Tools | Templates * and open the template in the editor. package javaapplication1; * @author rohan import com.sun.media.util.ContentType; im

  • IMap and Google recognition when using a third part domain with forwarding

    Hi, I have iWeb and have brought a domain name from Godaddy. The Godaddy domain is set to forward to the .Mac account so I can easily edit the information with iWeb - however, I have registered the site with Google (a few weeks ago now), but it still