Clearing hidden backup files from start up disk, time machine

Started gettin the slow down, so I had a tidy up. Moved all my movies audio etc and stored on external HDD, but as I have lion and time machine it saved a local back up so that when time machine was synced it didn't miss anything.
Seems sensible, so next step was to sync time machine, expecting that the local back up would disappear when it shifted to TM. It didn't...
PROBLEM: why in gods green earth is the local back up there even though TM connected the whole time and up to date?
I've restarted, loaded all updates and verified disk...
How do I get to the "it just works" part without having to Delete this double up (32GB "backups") via terminal etc....

Hope information from the below linked  article helps.
http://pondini.org/OSX/DiskSpace.html
Credit to Pondini.

Similar Messages

  • How do I import my video files from old iPhoto - in time machine - to new iPhoto?  Photoes came across, video said incompatible.

    how do I import my video files from old iPhoto - in time machine - to new iPhoto?  Photoes came across, video said incompatible.
    i have moved from a mac pro to a mac mini,
    Mini now has mavericks and latest iLife stuff, I clicked import, was all good, then at end, no videos came across.
    Is Mavericks,/iPhoto having a compatibiltiy issue with some video formats....???
    Your help is appreciated gang.: )

    Please describe exactly what you did. In moving to a new machine no importing is involved. The best way is to simply connect the two computers together and drag the iPhoto library from the old one to the pictures folder go the new one and launch iPhoto
    LN

  • Can i backup files from my ipad2 to time capsule

    I am trying to backup files from my ipad2 to a new 2t time capsule I just purchased. Is this possible? Also, is it ok to delete files from my macbook or ipad once they are backed up in order to free up space?

    The solution is filebrowser app for ipad. Filebrowser is like finder in osx.

  • How to delete files from start up disk

    Please help. After my macbook air is on for 2-5 mins, it comes up with I need to delete files from my start up disk. I went into start up disk and the only thing in there is the OS X system. So, then a small box appears. and tells me my memory is full and that I need to force quit applications. Sometimes the only application that is on it is finder. At this point the macbook air then freezes and I have to turn it off holding the button down. When I go to turn it back on it will often not turn back on. This laptop is only 11months old and running the new OS X system (mountain Lion) that just came out.

    Use Grandperspective to visually map all files:
    http://www.macupdate.com/app/mac/19515/grandperspective
    Also check this page about clearing drop box cache on your Mac:
    https://www.dropbox.com/help/328/en

  • Can't copy some files from FileVault Sparsebundle in Time Machine backup

    I've got filevault turned on for my mac Mac Mini (10.6.2). I'm using Time Machine to back up to a firewire drive. There's plenty of space - my Mini hd has 250 Gb of 500 used, and I'm backing up to a 750Gb partition on the external drive. The initial backup went OK, and when I logged out it backed up my filevault-protected home directory. When I logged back in, I was able to browse the Backups.backupdb on the external drive, go to the users directory, and open the sparsebundle that was my filevault-protected home directory (after entering the password). I can browse through this backup of my home directory. However, when I try copying files from the backup of the home directory, I get an error:
    The Finder can't complete the operation because some data in "(filename)" can't be read or written. (Error code -36).
    I get this error for some files, but not all of them. I've tried running BatChmod to reset permissions on all files in my home directory, and then erasing the backup drive and having Time Machine recreate the backup. However I'm still having this problem.
    I have also tried restoring the entire hard drive (to a 3rd external HD) by booting from the 10.6 DVD and going through the full-restore process. All of my files are fine when I restore using this method.
    Is there something I should do so that I can restore individual files from the backup of my filevault sparsebundle? It is extremly inconvenient to have to do a full hard drive restore if all I want is a file or two, and of course if the motherboard on my mini dies and I can't get a close enough replacement computer, then I could really be up a creek.
    Thanks,
    John F
    New York

    feinberj wrote:
    I've got filevault turned on for my mac Mac Mini (10.6.2). I'm using Time Machine to back up to a firewire drive. There's plenty of space - my Mini hd has 250 Gb of 500 used, and I'm backing up to a 750Gb partition on the external drive. The initial backup went OK, and when I logged out it backed up my filevault-protected home directory. When I logged back in, I was able to browse the Backups.backupdb on the external drive, go to the users directory, and open the sparsebundle that was my filevault-protected home directory (after entering the password). I can browse through this backup of my home directory. However, when I try copying files from the backup of the home directory, I get an error:
    The Finder can't complete the operation because some data in "(filename)" can't be read or written. (Error code -36).
    I get this error for some files, but not all of them. I've tried running BatChmod to reset permissions on all files in my home directory, and then erasing the backup drive and having Time Machine recreate the backup. However I'm still having this problem.
    I have also tried restoring the entire hard drive (to a 3rd external HD) by booting from the 10.6 DVD and going through the full-restore process. All of my files are fine when I restore using this method.
    Is there something I should do so that I can restore individual files from the backup of my filevault sparsebundle?
    Don't try to restore files individually by hand using finder. TM backups are protected by very restrictive ACLs and are not designed to be accessed that way.
    you can restore the whole sparse bundle with the home directory from TM interface. you should be logged in as a different user when you do this. the easiest is to be logged in as root so as not to deal with any permissions issues.
    another thing you might try is doing it from command line instead of finder. this is also not the designed way but might work where finder copy doesn't.
    to do this run the following terminal command after you mount the sparse bundle with backups of the home directory
    ditto --noacl path/to/source/file /path/to/target/directory
    here path/to/source file is the path to the file in the sparse bundle you want to restore and path/to target directory is the path to the folder where you want to copy it to. an easy way to get the path to an item is to drag that item to the terminal window. make sure that you have all the spaces correctly in the command.
    It is extremly inconvenient to have to do a full hard drive restore if all I want is a file or two, and of course if the motherboard on my mini dies and I can't get a close enough replacement computer, then I could really be up a creek.
    Thanks,
    John F
    New York

  • When you upgrade from Lion to ML, do you need to erase your external backup drive and start over in Time Machine, or does it just automatically pick up from where it stopped with Lion?

    This is a 500 GB G-Drive mobile external hard drive that I've been using since I got my MacBook Pro in '09. So I've had it from Leopard through Lion. Should I have been erasing it each time a new operating system comes out and starting over?

    No - just continue to use Time Machine as you have always been.
    Not only is erasing it unnecessary, doing that would eliminate the only practicable way of undoing an OS X upgrade.

  • How do I save files from my HD onto Time Machine?

    If I delete files on my hard drive to free up space (i.e., movie files that I want to save in an external harddrive), time machine will not keep these files for me on my external harddrive, since time machine just backs up what is in Macintosh HD. Right? How do I make it so Time Machine does NOT delete these files from it's archive?

    beccasanchezmartin
    How do I make it so Time Machine does NOT delete these files from it's archive?
    You need to seriously consider options OTHER than time machine for important data.  TM premise is storing a copy of your machine, its design and purpose is not for archiving important data youve spent years working on, despite countless people who in fact, and in error, use it that way.
    since time machine just backs up what is in Macintosh HD. Right?
    Correct, time machine is an entry level backup methodology, you need to consider something other than time machine for that.   You NEVER want to work off the premise of needing to delete things.
    Buy an external HD and store vital files on there, .....Time Machine is a sytem backup, NOT a data archive, nor a primary redundancy.
    Methodology to protect your data. Backups vs. Archives. Long-term data protection
    #1. Time Machine / Time Capsule
    Drawbacks:
    1. Time Machine is not bootable, if your internal drive fails, you cannot access files or boot from TM directly from the dead computer.
    2. Time machine is controlled by complex software, and while you can delve into the TM backup database for specific file(s) extraction, this is not ideal or desirable.
    3. Time machine can and does have the potential for many error codes in which data corruption can occur and your important backup files may not be saved correctly, at all, or even damaged. This extra link of failure in placing software between your data and its recovery is a point of risk and failure. A HD clone is not subject to these errors.
    4. Time machine mirrors your internal HD, in which cases of data corruption, this corruption can immediately spread to the backup as the two are linked. TM is perpetually connected (or often) to your computer, and corruption spread to corruption, without isolation, which TM lacks (usually), migrating errors or corruption is either automatic or extremely easy to unwittingly do.
    5. Time Machine does not keep endless copies of changed or deleted data, and you are often not notified when it deletes them; likewise you may accidently delete files off your computer and this accident is mirrored on TM.
    6. Restoring from TM is quite time intensive.
    7. TM is a backup and not a data archive, and therefore by definition a low-level security of vital/important data.
    8. TM working premise is a “black box” backup of OS, APPS, settings, and vital data that nearly 100% of users never verify until an emergency hits or their computers internal SSD or HD that is corrupt or dead and this is an extremely bad working premise on vital data.
    9. Given that data created and stored is growing exponentially, the fact that TM operates as a “store-it-all” backup nexus makes TM inherently incapable to easily backup massive amounts of data, nor is doing so a good idea.
    10. TM working premise is a backup of a users system and active working data, and NOT massive amounts of static data, yet most users never take this into consideration, making TM a high-risk locus of data “bloat”.
    11. In the case of Time Capsule, wifi data storage is a less than ideal premise given possible wireless data corruption.
    12. TM like all HD-based data is subject to ferromagnetic and mechanical failure.
    13. *Level-1 security of your vital data.
    Advantages:
    1. TM is very easy to use either in automatic mode or in 1-click backups.
    2. TM is a perfect novice level simplex backup single-layer security save against internal HD failure or corruption.
    3. TM can easily provide a seamless no-gap policy of active data that is often not easily capable in HD clones or HD archives (only if the user is lazy is making data saves).
    #2. HD archives
    Drawbacks:
    1. Like all HD-based data is subject to ferromagnetic and mechanical failure.
    2. Unless the user ritually copies working active data to HD external archives, then there is a time-gap of potential missing data; as such users must be proactive in archiving data that is being worked on or recently saved or created.
    Advantages:
    1. Fills the gap left in a week or 2-week-old HD clone, as an example.
    2. Simplex no-software data storage that is isolated and autonomous from the computer (in most cases).
    3. HD archives are the best idealized storage source for storing huge and multi-terabytes of data.
    4. Best-idealized 1st platform redundancy for data protection.
    5. *Perfect primary tier and level-2 security of your vital data.
    #3. HD clones (see below for full advantages / drawbacks)
    Drawbacks:
    1. HD clones can be incrementally updated to hourly or daily, however this is time consuming and HD clones are, often, a week or more old, in which case data between today and the most fresh HD clone can and would be lost (however this gap is filled by use of HD archives listed above or by a TM backup).
    2. Like all HD-based data is subject to ferromagnetic and mechanical failure.
    Advantages:
    1. HD clones are the best, quickest way to get back to 100% full operation in mere seconds.
    2. Once a HD clone is created, the creation software (Carbon Copy Cloner or SuperDuper) is no longer needed whatsoever, and unlike TM, which requires complex software for its operational transference of data, a HD clone is its own bootable entity.
    3. HD clones are unconnected and isolated from recent corruption.
    4. HD clones allow a “portable copy” of your computer that you can likewise connect to another same Mac and have all your APPS and data at hand, which is extremely useful.
    5. Rather than, as many users do, thinking of a HD clone as a “complimentary backup” to the use of TM, a HD clone is superior to TM both in ease of returning to 100% quickly, and its autonomous nature; while each has its place, TM can and does fill the gap in, say, a 2 week old clone. As an analogy, the HD clone itself is the brick wall of protection, whereas TM can be thought of as the mortar, which will fill any cracks in data on a week, 2-week, or 1-month old HD clone.
    6. Best-idealized 2nd platform redundancy for data protection, and 1st level for system restore of your computers internal HD. (Time machine being 2nd level for system restore of the computer’s internal HD).
    7. *Level-2 security of your vital data.
    HD cloning software options:
    1. SuperDuper HD cloning software APP (free)
    2. Carbon Copy Cloner APP (will copy the recovery partition as well)
    3. Disk utility HD bootable clone.
    #4. Online archives
    Drawbacks:
    1. Subject to server failure or due to non-payment of your hosting account, it can be suspended.
    2. Subject, due to lack of security on your part, to being attacked and hacked/erased.
    Advantages:
    1. In case of house fire, etc. your data is safe.
    2. In travels, and propagating files to friends and likewise, a mere link by email is all that is needed and no large media needs to be sent across the net.
    3. Online archives are the perfect and best-idealized 3rd platform redundancy for data protection.
    4. Supremely useful in data isolation from backups and local archives in being online and offsite for long-distance security in isolation.
    5. *Level-1.5 security of your vital data.
    #5. DVD professional archival media
    Drawbacks:
    1. DVD single-layer disks are limited to 4.7Gigabytes of data.
    2. DVD media are, given rough handling, prone to scratches and light-degradation if not stored correctly.
    Advantages:
    1. Archival DVD professional blank media is rated for in excess of 100+ years.
    2. DVD is not subject to mechanical breakdown.
    3. DVD archival media is not subject to ferromagnetic degradation.
    4. DVD archival media correctly sleeved and stored is currently a supreme storage method of archiving vital data.
    5. DVD media is once written and therefore free of data corruption if the write is correct.
    6. DVD media is the perfect ideal for “freezing” and isolating old copies of data for reference in case newer generations of data become corrupted and an older copy is needed to revert to.
    7. Best-idealized 4th platform redundancy for data protection.
    8. *Level-3 (highest) security of your vital data. 
    [*Level-4 data security under development as once-written metallic plates and synthetic sapphire and likewise ultra-long-term data storage]
    #6. Cloud based storage
    Drawbacks:
    1. Cloud storage can only be quasi-possessed.
    2. No genuine true security and privacy of data.
    3. Should never be considered for vital data storage or especially long-term.
    4. *Level-0 security of your vital data. 
    Advantages:
    1. Quick, easy and cheap storage location for simplex files for transfer to keep on hand and yet off the computer.
    2. Easy source for small-file data sharing.
    Make a (some) Redundancy of data
    Secondary data on a single external HD or RAID array is not a redundancy, but a PRIMARY data copy.          First Redundancy takes place on a Secondary storage medium/locus. (both of these external of course)
    2nd level protection in any redundancy necessitates it "be unconnected".           Data ON the actual computer is not considered, ergo a single copy OFF a computer is just that, a backup / copy.  Redunancy begins as secondary to a FIRST COPY

  • Macbook Air Restoring files from Trash Can in Time Machine

    I have memory issues with my Macbook Air.  I think casued by the fact iphoto uses so much memory.  Last week I was trying to download some photos but got a message saying my start up drive was nearly full.  Next think i know, the Macbook has somehow dumped about 500 of my old photos in the trash can (I didn't do this).  A few minutes later I look in the trash can and find it's emptied itself. 
    The next morning when I turned on my laptop, about 1 GB of memory had reappeared, and the photos were back in the trash can.  My plan was to restore the photos however I stupidly didn't do it immediately as I was busy.
    Now a weel later, I again got the message that my start up drive was full.  The photos have disappeared from the trash can.  I have reboted the Mac, but they have not reappeared.
    I backup using an external hard drive and Time Machine.  All I want to do is go into the trash can on the back up and restore the photos from there.  I don't want to restore the whole Mac, as I will lose all the work I've done since that last back up, won't I?  I can't search for the specific files on the Time Machine as I don't know what they're called - they were 100s of photos, the names were numbers only and I don't know which photos they were - as it wasn't me who deleted them!
    Please can anyone help me?
    I find these issues so frustrating, and I can't believe my 60 GB laptop is full.  I only use it for photos, browsing the web and a few documents.  My previous Windows netbook was about a quarter the size and never got close to full. 

    Do you know if the hard drive is full, does iPhoto move files to the trash can?
    No, it doesn't.
    Or does it have a setting to clean up duplicate files
    No. There are third-party applications that purport to do it, and if you used one of those, that would explain what happened.
    Is my only option therefore to restore the entire system to an earlier date?
    I don't see why you would need to restore anything other than the iPhoto library, or whatever folder contained the missing files.
    You can't do a partial restoration of the iPhoto library; it's all or nothing. However, if you restore an older library to a new location, you can extract images from it and import them into a newer library.

  • Retrieve iPhoto files from external drive with Time Machine

    I can retrieve all other files with Time Machine (including photos in Pictures) but not my iPhoto pics. Have read a few suggestions but having trouble following.
    Thanks in anticipation, Ernest.

    If you are trying to restore individual photos saved in iPhoto, you cannot do that. Instead, you need to restore the whole iPhoto library.
    To prevent the lose of the most recent photos, go to the folder where you have got your iPhoto library (by default, Pictures) and copy it to another folder. Then, in that folder, open the Time Machine app (in /Applications/Utilities), navigate through your backups and restore the iPhoto library you need

  • How to transfer backup file from old to new time capsule?

    I'm having trouble copying the backup from my old to new time capsule.  I tried using this http://support.apple.com/kb/HT5097?viewlocale=en_US

    You need to point out at which point you are failing.
    You do need the two TC plugged into each other by ethernet.. do not even dream of doing this over wireless. So a computer is plugged into the primary TC as well.. the secondary TC is in bridge mode.. you then simply copy and paste the sparsebundle from one TC to the next.
    IMHO this is not a good idea.. you are much better starting a new set of TM backups on the new TC.. keep the old TC for a few weeks to make sure there is nothing you need to recover then wipe it.
    There are also instructions in pondini if you insist on doing it.
    Transfer TM backups..
    Apple doco. http://support.apple.com/kb/ht5097
    Pondini doco http://pondini.org/TM/18.html
    The apple doco you have already tried.

  • How can I make I-cloud back up only the files created since the last Time-Machine backup?

    Hi everyone,
    So, I wish to use time-machine to back up every six weeks or so. This means a whole range of files could be lost if my wonderfully fast but terrifyingly unrecoverable solid state hard drive packs up.
    Has anyone any idea how I can make Icloud only backup files created since the last time machine backup?
    Best
    Danny

    Automator is not the right solution.
    Use a folder action script. Apple has an example here: (Auto-backup Script):
    http://www.apple.com/applescript/folderactions/05.html
    the steps might have been written for 10.3, so the steps may not be 100% right, but this will do what you want.

  • Deleting time machine backup files from old time machine disk

    I have an external USB HD that USED to be my Time Machine backup disk. I have replaced it with a newer FW HD and use the old one for archiving files, disk images, etc. The old disk still had 100gigs of backup files on it from time machine. To free up space, I thought I'd drag a few months of backups off the old dick into the trash. This worked. But I can't empty the trash. When I go to put the backup folders BACk on the USB disk, I get an error. So they are stuck in the trash.
    Any help? Thanks.

    I have always understood that there is no need to delete backup files from Time Machine.   Once it reaches 'full' it begins to delete them sequentially of its own accord.
    Good policy to check out Pondini's comments.
    http://pondini.org/TM/Troubleshooting.htm
    Or type Pondini into Google for a broader selection of his offerings.

  • Time machine on external drive will not back up itunes media file on a separate external drive. Have already reformated itunes media drive,dragged itunes media backup file from time machine (old copy) and removed time machine plist and restarted.

    Two external drives, one for time machine backups and a second (daisy chained firewire) for itunes media folder . Time machine fails to backup the media file saying could not be completed, with no error specified. Steps taken already include reformating drive with media, dragging older media backup file from time machine disc to media disc, and deleting time machine plist and starting time macine preferences upon startup. Media folder is approx 200 gb, mostly ripped dvd movies.
    Any help for this??
    Thanks

    Tks for the help. Tried to eliminate duplicates. Copy below.
    6/11/14 3:07:33.458 PM com.apple.backupd[532]: Found 2332 files (193.66 GB) needing backup
    6/11/14 3:07:33.488 PM com.apple.backupd[532]: 219.71 GB required (including padding), 539.32 GB available
    6/11/14 3:09:42.200 PM com.apple.backupd[532]: Copied 1201 items (51.5 MB) from volume Macintosh HD. Linked 2894.
    6/11/14 3:10:14.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:10:17.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:10:30.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:10:30.072 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Home Videos/2013 Trip To Kate and Jason - Large 1.m4v to (null)
    6/11/14 3:10:44.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:10:57.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:10:57.327 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Home Videos/2013 Trip To Kate and Jason - Large.m4v to (null)
    6/11/14 3:11:09.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:11:22.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:11:22.394 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Home Videos/IMG_0378.m4v to (null)
    6/11/14 3:11:57.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:12:09.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:12:09.872 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Home Videos/IMG_0398.m4v to (null)
    6/11/14 3:12:44.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:12:46.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:13:05.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:13:05.959 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/AAA 2.4.1.ipa to (null)
    6/11/14 3:13:23.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:13:46.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:13:51.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:13:51.325 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Air Sharing 3.4.3.ipa to (null)
    6/11/14 3:14:18.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:14:21.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:14:48.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:14:51.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:14:51.289 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Angie's List 3.0.2.ipa to (null)
    6/11/14 3:15:16.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:15:29.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:15:34.517 PM secd[422]:  SecErrorGetOSStatus unknown error domain: com.apple.security.sos.error for error: The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)
    6/11/14 3:15:34.517 PM secd[267]:  SecErrorGetOSStatus unknown error domain: com.apple.security.sos.error for error: The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)
    6/11/14 3:15:34.517 PM secd[267]:  securityd_xpc_dictionary_handler EscrowSecurityAl[581] DeviceInCircle The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)
    6/11/14 3:15:34.517 PM secd[422]:  securityd_xpc_dictionary_handler EscrowSecurityAl[580] DeviceInCircle The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)
    6/11/14 3:15:51.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:15:51.643 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/AP Mobile 6.2.1.ipa to (null)
    6/11/14 3:15:54.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:16:07.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:16:19.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:16:19.908 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Apple Store 120269.ipa to (null)
    6/11/14 3:16:35.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:16:50.710 PM com.apple.backupd-helper[533]: Not starting scheduled Time Machine backup: Backup already running
    6/11/14 3:16:53.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:17:00.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:17:00.552 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Archetype 1.6.2.ipa to (null)
    6/11/14 3:17:10.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:17:23.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:17:35.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:17:49.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:18:01.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:18:14.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:18:28.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:18:40.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:19:03.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:19:06.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:19:18.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:19:41.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:19:43.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:19:56.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:20:11.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:20:23.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:20:36.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:20:48.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:21:01.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:21:13.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:21:26.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:21:38.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:21:51.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:22:03.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:22:16.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:22:28.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:22:41.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:22:53.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:23:06.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:23:19.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:23:31.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:23:57.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:24:09.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:24:22.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:24:38.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:24:50.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:25:03.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:25:15.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:25:35.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:25:47.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:25:47.887 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Bloomberg 3.0.ipa to (null)
    6/11/14 3:26:01.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:26:13.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:26:13.942 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Calculator 3.4.ipa to (null)
    6/11/14 3:26:26.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:26:26.509 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Camera Zoom 3.1.ipa to (null)
    6/11/14 3:26:39.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:26:52.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:26:52.108 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Cards 2.0.1.ipa to (null)
    6/11/14 3:27:14.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:27:17.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:27:29.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:27:29.606 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Casino 2.5.ipa to (null)
    6/11/14 3:27:47.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:28:00.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:28:00.327 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Clear Day 2.6.ipa to (null)
    6/11/14 3:28:14.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:28:26.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:28:39.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:28:56.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:29:09.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:29:21.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:29:34.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:29:47.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:29:59.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:30:12.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:30:24.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:30:37.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:30:49.085 PM xpcproxy[629]: assertion failed: 13D65: xpcproxy + 3438 [D559FC96-E6B1-363A-B850-C7AC9734F210]: 0x2
    6/11/14 3:30:49.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:30:50.194 PM syncdefaultsd[628]: Fixing push token
    6/11/14 3:30:52.507 PM xpcproxy[632]: assertion failed: 13D65: xpcproxy + 3438 [D559FC96-E6B1-363A-B850-C7AC9734F210]: 0x2
    6/11/14 3:31:02.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:31:14.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:31:27.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:31:39.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:31:52.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:32:05.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:32:17.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:32:30.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:32:42.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:32:55.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:33:07.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:33:30.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:33:32.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:33:55.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:33:58.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:34:21.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:34:23.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:34:46.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:34:49.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:35:02.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:35:18.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:35:30.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:35:30.676 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Collection HD 1.7.ipa to (null)
    6/11/14 3:36:14.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:36:17.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:36:29.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:36:29.651 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/eCardExpress 2.1.ipa to (null)
    6/11/14 3:36:52.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:37:14.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:37:17.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:37:30.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:37:52.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:37:55.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:38:07.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:38:30.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:38:32.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:38:45.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:39:08.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:39:10.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:39:23.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:39:46.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:39:48.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:40:01.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:40:23.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:40:26.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:40:38.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:41:01.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:41:04.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:41:16.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:41:39.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:41:41.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:41:54.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:42:17.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:42:19.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:42:32.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:42:54.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:42:57.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:43:09.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:43:32.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:43:34.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:43:47.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:44:10.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:44:12.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:44:25.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:44:48.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:44:50.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:45:03.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:45:25.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:45:28.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:45:40.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:45:55.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:46:07.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:46:20.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:46:32.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:46:45.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:46:58.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:47:10.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:47:23.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:47:35.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:47:48.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:48:00.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:48:13.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:48:26.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:48:38.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:48:51.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:49:03.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:49:16.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:49:21.393 PM WindowServer[128]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04280300 device: 0x7f8ef9d04e00  isBackBuffered: 1 numComp: 3 numDisp: 3
    6/11/14 3:49:21.731 PM launchservicesd[52]: Application App:"System Preferences" asn:0x0-44044 pid:509 refs=7 @ 0x7fb5b9443730 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x45045 pid=513 "com.apple.prefs.backup.remoteservice"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100019/0x186b3 queue
    6/11/14 3:49:21.731 PM WindowServer[128]: [cps/setfront] Failed setting the front application to System Preferences, psn 0x0-0x44044, securitySessionID=0x186b3, err=-13066
    6/11/14 3:49:21.733 PM WindowServer[128]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7f8ef9e94e00(2001)
    6/11/14 3:49:21.795 PM WindowServer[128]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x7f8ef9e94e00(2001)
    6/11/14 3:49:29.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:50:48.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:50:48.546 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/GarageBand 1.1.ipa to (null)
    6/11/14 3:51:01.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:51:13.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:51:26.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:51:38.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:51:51.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:52:03.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:52:16.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:52:29.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:52:41.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:52:55.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:53:07.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:53:07.747 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Glympse 2.22.444.ipa to (null)
    6/11/14 3:53:20.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:53:32.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:53:32.869 PM com.apple.backupd[532]: Stopping backup.
    6/11/14 3:53:32.869 PM com.apple.backupd[532]: Error: (-36) SrcErr:YES Copying /Volumes/Media/itunes Media/Mobile Applications/Golf Channel 3.7.2.ipa to (null)
    6/11/14 3:53:33.357 PM com.apple.backupd[532]: Copied 127 items (2.24 GB) from volume Media. Linked 0.
    6/11/14 3:53:33.376 PM com.apple.backupd[532]: Copy stage failed with error:11
    6/11/14 3:53:34.607 PM com.apple.backupd[532]: Backup failed with error 11: 11
    6/11/14 3:55:53.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:56:05.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:56:18.000 PM kernel[0]: disk1s2: I/O error.
    6/11/14 3:56:33.000 PM kernel[0]: disk1s2: I/O error.

  • Won't start from Start up Disk- Dead iMac - help!!

    Hi,
    My iMac at work died today, first it crashed and then the hard disk began to spin and then the fan cut in and it sounded like a jumbo taking off. I used the power switch to turn off, waited a minute turned it back on and it then hung at the blue screen. Did this again two or three times but it still hung, sometimes in different places but always after the apple screen and the spinning thing. I then loaded the system disk and started it up, it loaded the install software screen and then crashes. I started the machine in "Safe Mode", it started properly but then crashed as soon as I tried to anything. I even loaded the startup cd in safe mode but it did the same.
    The machine is very basic first generation iMac, no bluetooth, 160gb hd, 17inch 1.6gig 256 meg ram. Using Panther fully updated using Software Update. Nothing special.
    Apple Care just wanted £35.00 from me before they would even tell me if I could take it direct to my local Apple Store - I say local but it would be a 100 mile round trip so I thought it best to check first.
    Help, I can't even start from start up disk!!!!

    Hugo, I had the same thing happen twice. The first thing I did is run the hardware diagnostics to determine if the disk had totally crapped out. This test passed on both occurrences. I then tried to repair the disk by booting from the install disk (hold down the 'c' key while booting) and using the disk utility. The first time I had the problem this fixed it. Last night it happened for the second time, this time repairing the disk failed. I had to erase the disk, reinstall the OS and upgrades and load user files from backup. One tip, don't call AppleCare unless you really want to be annoyed. I had some useless tech explain to me how the hard drive was analogous to a library, the librarian goes home at night with all the books properly in place and some kids come in and move all the books around. When the librarian comes in the next day she cannot do anything because the location of the books do not match the locations identified in her book catalog. So I asked, who these 'kids' are that messed up my disk. He said this just happens. Well this has just happened to this computer twice in a month and its old 9 months old. I have 3 PCs running that have never had this problem, one is 8 years old. One more thing AppleCare categorizes this problem as a software issue, not hardware, so it is not covered, even though it's Apple's software that failed ! You either have to fix it yourself or pay someone to do it for you. Sorry for the digression (as you can tell I'm a little frustrated with Apple), when I was just about done loading user files from backup, the iMac died, will not power backup, nothing, just dead. This is after I just spent 4 hours erasing the disk and reinstalling software and files. Guess I do have a hardware problem now.
    Good luck

  • Ola Hallengren maintenance solution TSQL script not deleting old backup files from my local SQL server

    I have looked on Ola's site (https://ola.hallengren.com/frequently-asked-questions.html) and I did see this:
    DatabaseBackup is not deleting old backup files. What could the problem be?
    Verify that the SQL Server and SQL Server Agent service accounts have full control of the backup directory.
    If that directory is a network share, verify that the SQL Server and SQL Server Agent service accounts have full control of the network share.
    If you are using a proxy account, verify that the account is a member of the sysadmin server role and that it has full control of the backup directory and network share.
    Verify that the file is not locked in the file system; for example, a backup or antivirus software could be locking the file.
    DatabaseBackup has been designed not to delete transaction log backups that are newer than the most recent full or differential backup. This could explain why transaction log backups are not being deleted.
    I followed these instructions and then I right clicked the "sp_delete_backuphistory" job under "SQL Server Agent > Jobs" folder and clicked the "Start job at step ..." option. The job successfully ran, but my .bak backup
    files were still on located on my separate drive partition I use specifically for these backups. 
    The SQL Server and the SQL Server Agent are both using the same AD account. 
    Would any of you SQL gurus out there know how to resolve this?
    Thank you 

    The sp_delete_backuphistory job only deletes the historical info from the backup & restore tables in the msdb database. It does not do anything to the files on disk.
    https://msdn.microsoft.com/en-us/library/ms188328.aspx
    The code to actually purge the backup files from disk is inside the DatabaseBackup stored procedure. It is controlled by using the @CleanupTime parameter for that stored proc. Verify the value for that parameter is low enough to delete your files on disk. The
    value is in hours, and I believe the default is 48 hours. The SQL agent job name usually starts with "DatabaseBackup...".

Maybe you are looking for