Time Machine stalls during backup to external HD

About a month ago, Time Machine began to stall when attempting to backup to my external HDD. Now when I attempt to backup, the progress will reach ~3 KB/4GB and will stop. I have no idea what the problem is or how to fix it.
I have tried running repair disk on my external hard drive, i was able to backup to the point of 1.58GB/4.09 GB before the progress stalled. I performed a search in console for "backup" and found an error that occurred 3 hours after the backup was started. This was the error "7/28/12 3:15:00.439 AM com.apple.var-db-shadow-backup: Error adding file shadow". I dont know exactly what it means or what to do about it.

Jul 30 19:06:13 Users-MacBook-Pro com.apple.backupd[3973]: Starting standard backup
Jul 30 19:06:13 Users-MacBook-Pro mtmd[2561]: Set snapshot time:1343689575 (current time:1343689573)
Jul 30 19:06:13 Users-MacBook-Pro com.apple.backupd[3973]: Backing up to: /Volumes/Iomega HDD/Backups.backupdb
Jul 30 19:06:20 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendDetachNotification (thread 0x7fff72651960): sending detach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Jul 30 19:06:20 Users-MacBook-Pro iTunes[2382]: _AMDDeviceDetached (thread 0x10fd75000): Device 'AMDevice 0x7f921e9f66b0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 214, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' detached.
Jul 30 19:06:20 Users-MacBook-Pro iTunes[2382]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
Jul 30 19:06:20 Users-MacBook-Pro ath[2407]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
Jul 30 19:07:06 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendAttachNotification (thread 0x7fff72651960): sending attach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Jul 30 19:07:06 Users-MacBook-Pro usbmuxd[21]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Jul 30 19:07:06 Users-MacBook-Pro iTunes[2382]: _AMDDeviceAttachedCallbackv3 (thread 0x10fd75000): Device 'AMDevice 0x7f921c9fa7f0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 215, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
Jul 30 19:07:06 Users-MacBook-Pro ath[2407]: _AMDDeviceAttachedCallbackv3 (thread 0x7fff72651960): Device 'AMDevice 0x10433b820 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 215, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
Jul 30 19:07:06 Users-MacBook-Pro ath[2407]: _AMDDeviceAttachedCallbackv3 (thread 0x7fff72651960): Device 'AMDevice 0x104243d30 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 215, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
Jul 30 19:07:41 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendDetachNotification (thread 0x7fff72651960): sending detach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Jul 30 19:07:41 Users-MacBook-Pro iTunes[2382]: _AMDDeviceDetached (thread 0x10fd75000): Device 'AMDevice 0x7f921c9fa7f0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 215, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' detached.
Jul 30 19:07:41 Users-MacBook-Pro iTunes[2382]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
Jul 30 19:07:41 Users-MacBook-Pro ath[2407]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
Jul 30 19:08:23 Users-MacBook-Pro com.apple.backupd[3973]: 4.57 GB required (including padding), 213.21 GB available
Jul 30 19:10:28 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendAttachNotification (thread 0x7fff72651960): sending attach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Jul 30 19:10:28 Users-MacBook-Pro usbmuxd[21]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Jul 30 19:10:28 Users-MacBook-Pro ath[2407]: _AMDDeviceAttachedCallbackv3 (thread 0x7fff72651960): Device 'AMDevice 0x104338da0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 216, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
Jul 30 19:10:28 Users-MacBook-Pro iTunes[2382]: _AMDDeviceAttachedCallbackv3 (thread 0x10fd75000): Device 'AMDevice 0x7f921ed04060 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 216, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
Jul 30 19:10:29 Users-MacBook-Pro ath[2407]: _AMDDeviceAttachedCallbackv3 (thread 0x7fff72651960): Device 'AMDevice 0x1040be1e0 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 216, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' attached.
Jul 30 19:11:03 Users-MacBook-Pro com.apple.usbmuxd[21]: _SendDetachNotification (thread 0x7fff72651960): sending detach for device 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Jul 30 19:11:03 Users-MacBook-Pro iTunes[2382]: _AMDDeviceDetached (thread 0x10fd75000): Device 'AMDevice 0x7f921ed04060 {UDID = 2d1d4facae3fbd7ea8002b8d571a3009c9bae7bb, device ID = 216, FullServiceName = 00:c6:10:ac:88:0f@fe80::2c6:10ff:feac:880f._apple-mobdev._tcp.local.}' detached.
Jul 30 19:11:03 Users-MacBook-Pro iTunes[2382]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...
Jul 30 19:11:03 Users-MacBook-Pro ath[2407]: _NotificationSocketReadCallbackGCD (thread 0x7fff72651960): Unexpected connection closure...

Similar Messages

  • My Time Machine stalls during initial backup on external hard drive even after several hours.

    We have been using Time Machine and an external hard drive to back up our MacBook for almost a year now.  Recently, the hard drive (using a USB) was removed without ejecting it properly.  After that, the auto backups began stalling.  We tried setting up Time Machine all over again but the initial back up stalls at different places (like 6MB of 87GB) even if it's left for several hours overnight.  Does anyone have any suggestions on how to fix this?  If not, can anyone suggest another inexpensive way of backing up our files from our MacBook? 
    Thanks!
    Shane

    It might have created a new user and loaded under that.. new user being the old user. But if you have issues do it again, only this time pick where the backup will go.
    http://pondini.org/TM/16.html
    The other questions might also be relevant as a new hard disk will make the Mac appear to the TM backup as a new computer.
    See 14-18 for restore info.

  • Time Machine Freezes During Backup!

    Hi there,
    When I back up my computer for the first time using Time Machine, it gets to around 53.2 GB. After that, it sits there with the blue progress bar at the same level. Then, i get a message that says I did not eject the disk properly, and then Time Machine alerts me that it could not finish the backup. NOTE: When it says the disk has not been ejected properly, I still see the disk in both Finder and disk utility. Also, I currently have the disk in 2 partitions, but I'm only using the Mac OS X (Journaled) partition for my Time Machine backups. Please help! Like I said, it seems to eject my external hard drive (Hitachi 250 GB Simple Drive) after freezing up for a while. I am able to use other things on my computer the whole time. The only application that was open during the backup was iTunes. Here is the log from Time Machine buddy:
    Starting standard backup
    Backing up to: /Volumes/External HD/Backups.backupdb
    Backup content size: 142.3 GB excluded items size: 30.7 GB for volume Macintosh HD
    No pre-backup thinning needed: 133.85 GB requested (including padding), 213.91 GB available
    Waiting for index to be ready (101)
    Copied 48.9 GB of 111.5 GB, 250192 of 667394 items
    Stopping backupd because the backup volume was ejected!
    Stopping backup.
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Error: (-36) SrcErr:NO Copying /Users/********/Library/Mail/IMAP-********@******[email protected]/INBOX.imapmbox/Attachments/3234/2 to /Volumes/External HD/Backups.backupdb/*******’s MacBook/2011-03-12-104926.inProgress/A8B8FCD0-3EA2-4A4D-B313-4A9EE0C56252/Macin tosh HD/Users/********/Library/Mail/IMAP-*********@********[email protected]/INBOX.imapmbox/Attachments/3234
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Copied 259985 files (49.5 GB) from volume Macintosh HD.
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Copy stage failed with error:11
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Backup failed with error: 27
    Thank you so much!
    Message was edited by: Host

    As a first step, launch Disk Utility, select the backup volume, and run "Verify Disk" (NOT "Repair Disk"). It will take a long time to run, maybe hours. If any errors are found, copy all data on the device to another drive, then run "Repair Disk." Be prepared for the possibility that "Repair Disk" may destroy the volume beyond recovery. It may also fail to repair the damage, in which case you should replace the device -- DO NOT erase it and continue to use it.

  • Time Machine stuck during backup

    From December 28 to January 13 my Time Machine functioned without issue, using an external Seagate Free Agent Drive (300 GB) with a 150 GB partition devoted to TM. For whatever reason I didn't happen to connect the drive from the 13th to the 16th, and now it appears to be freezing during the preparation process or very early in the backup.
    I've looked at some of the non-complete packages to try and ascertain the problem - so far it appears to always hang while backing up the Applications folder. Why it is re-backing up this whole folder at once is beyond me, as I'm only aware of one program I've recently updated - Flip4Mac. Incidentally, this was the program is was halting on initially - so I added that to the exclude list. Next go at it, and its stuck on a different program. Then another. Then another.
    Do I really need to exclude my whole Applications folder? That seems a bit counterintuitive to me.

    I've discovered the culprit after some additional searching here. Apparently Time Machine does not function correctly while the iSight is enabled. In the past I've had no trouble with Time Machine running in the background with a variety of other processes ongoing, but apparently this one is problematic. After quitting Skype I've found that backups completed quickly and painlessly. Hopefully this post is helpful to others as well, and hopefully Apple addresses this - at least through improving Time Machine's dreadfully horrible Help files.

  • Time Machine won't backup second external hard drive

    I am trying to store my iTunes music library on an external hard drive because I have run out of space on my hard drive. I have moved my folder to the external drive, but before I delete the folder from my computer I want to make sure my Time Machine is backing up the drive containing my music as well. However when I go into Time Machine preferences and tell it to include the other hard drive in its backups it says "The backup was not preformed because an error occured while copying files to the backup disk. The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair your backup disk."
    So I have tried again later, and still the same message. I went into Disk Utility and verified my backup disk and it said it was healthy. Ideas as to what I am doing wrong?

    Howdy Kgkgkg12,
    It sounds like this drive you are wanting to use with Time Machine is not in the same format that Time Machine needs to operate. According to this article:
    Mac Basics: Time Machine backs up your Mac
    Your Time Machine drive needs to be formatted as Mac OS X Extended (Journaled). If you select an NTFS or FAT-formatted drive, Time Machine prompts you to reformat the drive. Important: Reformatting erases any files on the destination drive. If you're not sure if you want to erase the drive you connected, choose a different drive.
    You can check the format of the drive with these steps:
    OS X Yosemite: View file, folder, and disk information
    Get individual item info: Select the item(s), then choose File > Get Info, or press Command (⌘)-I.
    Thank you for using Apple Support Communities.
    Cheers,
    Sterling

  • New Macbook hard drive can't locate Time Machine files of backup on external drive

    I just got my hard drive replaced as it was failing.  Just before I took it to the apple store I backed up my hard drive using time machine, on a separate hard drive: phew!  I checked that time machine was operating fine before I took it in to get the new hard drive - it was fine, I was able to "go back in time" and access my files.
    I tried to reload from time machine as soon as it started up, but it wasn't working, so I figured I'd just work on transferring the files after I booted up. Now I have a new hard drive and then plugged my external hard drive with the back up stored on it into my computer, but it cannot get the backup on my fixed macbook! It says it can't find it, and when I've looked at the disk in Finder (in backups.backupdb) it shows as a folder of my computer's name, and the only file inside is It is called: 2013-11-22-133614.inProgress (not even the correct date of the back up!).
    Now time machine won't go back in time any further than the age of the new hard drive.
    I can't understand that it seemed to be there, but now it is incomplete - this is ridiculous!
    What has happened?
    Has Time Machine failed me?
    Are the files there somewhere hidden away?

    Check here, Pondini has extensive info on TM:
    http://pondini.org/OSX/Home.html

  • Reset Time Machine Password to Backup Using External Drive

    I have been using Time Machine to backup my files regularly on an External drive. I usually backup my files (using Backup Now option) and then turn off Time Machine. I have been doing this successfully for a month on my new MacBookPro (late 2013 version, purchased 5 March 2014). I used this same procedure successfully since 2010 on a previous Macbook Pro I owned.
    I just tried to backup my files, all of a sudden Time Machine now asks me for a password which I don't remember setting. Time Machine Preferences looks like this.
    When I try to set Time Machine On I cannot do it (I used to be able to do it). When I click unlock and try to input my MacbookPro login username and password, but this login/password is not accepted.
    Frankly, I have no idea what happened. I must have pushed the wrong button at some point. I don't mind losing my old backus and resetting the password on Time Machine software, provided I can and backup my files right away.
    How can I reset the Time Machine password? Any help will be much appreciated.
    Francisco

    Dear Eric,
    I am using a Western Digital Ultra external drive that I myself formatted Journaled. It is not encrypted.
    I went to the keychain and I could not find the password for Time Machine. (Frankly, I am not sure where to look).
    I also ran Keychain first aid and no problem was found. I also ran Keychain first aid repair and everything seems fine.
    Tomorrow Monday I will call the repair shop, as I suspect they introduced a different password.
    Many thanks for now. I will keep you posted.
    Francisco

  • Time Machine won't backup my external drive

    I have my iTunes library stored on an external drive and I want Time Machine to back it up.
    I have a brand new TM drive. I've been using it without problems to backup my 250Gb iMac. As soon as I add the external drive to the TM backup, it fails. I have other data on this drive that I don't need backed up, so I've only included the sub directory iTunes (by excluding all the others).
    I followed a couple of similar threads, but the situations don't seem to apply. I did install Time Machine buddy so I could see the error messages.
    Starting standard backup
    Backing up to: /Volumes/Time Machine/Backups.backupdb
    Node requires deep traversal:/Volumes/Music:DVDs reason:must scan subdirs|
    No pre-backup thinning needed: 151.31 GB requested (including padding), 1.56 TB available
    Error: (2) setxattr for key:com.apple.backupd.SnapshotVolumeUUID path:/Volumes/Time Machine/Backups.backupdb/Tori's iMac/2009-11-25-182722.inProgress/3B5DD274-5AB6-44D1-9F1B-561934FB44AD/Music/DV Ds size:37
    Stopping backup.
    Copied 0 files (0 bytes) from volume Music/DVDs.
    Copy stage failed with error:11
    Backup failed with error: 11
    Drives are all formatted OS Extended Journaled
    I've run Disk Util on all the drives - no errors.
    Any ideas or other things I should try?
    If I remove the external drive from the backup, it starts to work again.

    The mystery deepens . . .
    I tried to replicate the problem. Renamed an empty partition from Misc2 to Misc2/test and copied some docs into it and ran a backup.
    Sure enough, the message refers to it as Misc2:test and the deep traversal took almost a minute and a half (one folder, 3 sub-folders, total of about 30 items!), but it ran successfully.
    So renamed it again, to Music/DVDs exactly like yours. No deep traversal, and it does call it Music:DVDs in the messages, but it backed-up properly.
    Perhaps it was fixed in Snow Leopard? Or just another of TM's many little quirks? Perhaps the phase of the moon?
    Edit: Some of your posts say you're on 10.5.3, others 10.6.2. Which is correct?
    Message was edited by: Pondini

  • Time Machine doing full backup of external drive again

    I have a Time Capsule, as well as an external data drive connected to my Mac. The external drive (named Yoda) is NOT excluded from backups. Yoda has about 703 GB of data on it.
    I recently replaced the hard drive inside my time capsule. Consequently, a full backup was made, which was to be expected.
    When the new full first backup was done, I disconnected the Yoda drive. A day later, I reconnected it, and now Time Machine is saying it's doing a 703 GB backup. Since the size TM indicates its backing up is ever so slightly larger than the total amount of data on Yoda, I'm assuming it's doing a full backup of the Yoda drive for some reason (the only other drive, the system drive, only has about 200 GB on it).
    The files on Yoda weren't changed, certainly not all 703 GB of them. No hardware changes were made, no updates, tinkering, modifications, or anything. The Mac itself has not even been shut down or logged out. The ONLY thing that's happened was the Yoda drive was unmounted and disconnected, then several hours later it was reconnected.
    Why is Time Machine repeating a full backup of this external drive? Is this going to happen every time I disconnect and reconnect the drive? Is there any way to make this not happen, short of excluding the drive (which I don't want to do)?

    After posting this thread, I did find a similar thread (in the "More Like This" section) and saw your responses in it. You had suggested the same thing, as well as doing #A5 if that didn't work.
    I tried #A4 and although that seemed to work in the other thread, unfortunately it didn't work for me. So I moved on to #A5, but I could not get my Time Capsule drive to show up in the Disk Utility. I didn't see a "data folder", but I did try directly dragging the sparsebundle to the left pane of the Disk Utility, but that seemed to hang Disk Utility.
    At this point I'm probably going to try deleting the plist file as per #A4, erasing (reformatting) the drive, rebooting, and starting a whole new backup from scratch. It's not going to take much longer than backing up the entire external drive by itself would have, and I still have older backups (up to a few days ago) on the original Time Capsule drive in case of massive disaster.
    So we'll see how that goes...

  • Time Machine won't backup my external hard drive.

    I am trying to get Time Machine to backup my external hard drive.  I have the external drive formated as Mac OS Extended (journaled) and I have also removed the drive from the Excluded list.  I put some 'test' files on the external drive and told TM to do a backup and when it is finished the only way I can see my external hard drive in TM is if it is connected to the computer.  It doesn't seem to be backed up anywhere in TM that I can see.  Please Help
    Thanks.

    Chihuahua Rancher wrote:
    My thinking is that if my external hard drive craps out it would be ok because it would be backed up on the TM (what I'm trying to get it to do)  How would I open the external drive if it was damaged and then invoke time machine?
    #E3 in Time Machine - Troubleshooting shows how to do that.

  • Time Machine: Multiple volumes backup to external drive

    It is slightly more complicated:
    I have a Mac Pro with two internal hard drives. Drive A has 5 partitions  and Drive B has a single large partition.
    I have one external drive that I divided into two partitions, with the plan of backing up Drive A to one and Drive B to the other.
    The backup of Drive A to the first partition went well. The problem is that I cannot figure out how to get Drive B to the 2nd partition on external drive.
    Suggestions?

    By default, Time Machine backs up everything on all attached drives.
    You can reduce the size of the backup set (by about 10 to 20GB depending on Applications installed) by choosing to exclude System files and Applications. Then you can back those up separately if you prefer.
    Time Machine's claim to fame is that it is the backup that actually happens, as opposed to the more specific hand crafted backup that, oops, did not get done since last month.

  • Time Machine crashing during backup

    I have been having issues with TM for the past 2-3 days. It worked fine for the past year and has suddenly stopped working and generating errors after every attempt. I have verified, repaired permissions on both my internal HD and the Lacie 1 TB external drive (partitioned into 2x500G, one for TM and one for media). I have also erased the partition and resetup TM but still no luck. The backup seems to fail after copying 1.8GB of data of 178 GB. I have attached a copy of the log from Time Machine Buddy.
    Thanks for any help.
    Starting standard backup
    Backing up to: /Volumes/Time Machine Backup /Backups.backupdb
    Error parsing SystemMigration.log to determine source volume of system migration.
    No pre-backup thinning needed: 198.26 GB requested (including padding), 431.11 GB available
    Waiting for index to be ready (101)
    backupd(317,0xb0185000) malloc: * mmap(size=2720010240) failed (error code=12)\n* error: can't allocate region\n* set a breakpoint in mallocerrorbreak to debug
    backupd(317,0xb0185000) malloc: * mmap(size=2720010240) failed (error code=12)
    * error: can't allocate region
    * set a breakpoint in mallocerrorbreak to debug
    terminate called after throwing an instance of 'std::bad_alloc'
    what(): std::bad_alloc
    2010-04-21 22:44:23.453 ReportCrash[320:1207] Saved crash report for backupd[317] version ??? (???) to /Library/Logs/DiagnosticReports/backupd2010-04-21-224423localhost.crash

    Going to give the hardware test a run to see what it comes back with. I am quite confused as I am not seeing any other issues with the computer.
    I have been working on computers for years and still do it for a living and can't figure this out for the life of me (The reason I use a mac is because I deal with PC issues all day long). I honestly am considering doing the actual complete wipe and reinstall even though its probably not going to help. I'm at a loss here and its frustrating because I deleted all my old backups as I originally thought it was the HD causing the problem and tried formatting the drive.
    Thanks for all your help...Your assistance here is invaluable and you are great at articulating troubleshooting steps.
    Crash Log:
    Process: backupd [225]
    Path: /System/Library/CoreServices/backupd
    Identifier: backupd
    Version: ??? (???)
    Code Type: X86 (Native)
    Parent Process: launchd [1]
    Date/Time: 2010-04-22 19:16:59.553 -0600
    OS Version: Mac OS X 10.6.3 (10D578)
    Report Version: 6
    Exception Type: EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Crashed Thread: 2
    Application Specific Information:
    abort() called
    Thread 0: Dispatch queue: com.apple.main-thread
    0 libSystem.B.dylib 0x94b632fa machmsgtrap + 10
    1 libSystem.B.dylib 0x94b63a67 mach_msg + 68
    2 com.apple.CoreFoundation 0x968f800f __CFRunLoopRun + 2079
    3 com.apple.CoreFoundation 0x968f70f4 CFRunLoopRunSpecific + 452
    4 com.apple.CoreFoundation 0x968fd034 CFRunLoopRun + 84
    5 backupd 0x0001067d 0x1000 + 63101
    6 backupd 0x00005f59 0x1000 + 20313
    Thread 1: Dispatch queue: com.apple.libdispatch-manager
    0 libSystem.B.dylib 0x94b89b42 kevent + 10
    1 libSystem.B.dylib 0x94b8a25c dispatch_mgrinvoke + 215
    2 libSystem.B.dylib 0x94b89719 dispatch_queueinvoke + 163
    3 libSystem.B.dylib 0x94b894be dispatch_workerthread2 + 240
    4 libSystem.B.dylib 0x94b88f41 pthreadwqthread + 390
    5 libSystem.B.dylib 0x94b88d86 start_wqthread + 30
    Thread 2 Crashed:
    0 libSystem.B.dylib 0x94bd04be _semwait_signalnocancel + 10
    1 libSystem.B.dylib 0x94bd03a2 nanosleep$NOCANCEL$UNIX2003 + 166
    2 libSystem.B.dylib 0x94c4b2f2 usleep$NOCANCEL$UNIX2003 + 61
    3 libSystem.B.dylib 0x94c6c9a8 abort + 105
    4 libstdc++.6.dylib 0x98c8cfda _gnu_cxx::__verbose_terminatehandler() + 433
    5 libstdc++.6.dylib 0x98c8b17a _cxxabiv1::_terminate(void (*)()) + 10
    6 libstdc++.6.dylib 0x98c8b1ba _cxxabiv1::_unexpected(void (*)()) + 0
    7 libstdc++.6.dylib 0x98c8b2b8 _gxx_exception_cleanup(_Unwind_ReasonCode, UnwindException*) + 0
    8 libstdc++.6.dylib 0x98c8b658 operator new(unsigned long) + 101
    9 libstdc++.6.dylib 0x98c8b703 operator new[](unsigned long) + 17
    10 com.apple.DesktopServices 0x903096c4 TCFURLInfo::CopyExtendedAttribute(char const*, __CFString const*, int, __CFData const**) + 430
    11 com.apple.DesktopServices 0x902c965b TCFURLInfo::CopyExtendedAttributes(__CFArray const*&, __CFArray const*&, unsigned long) const + 713
    12 com.apple.DesktopServices 0x902c8e86 TCopyItem::TCopyItem(unsigned long, TCopyQueue*, TCountedPtr<TCFURLInfo>, TCountedPtr<TCFURLInfo>, TCopyBuffer*, unsigned long) + 454
    13 com.apple.DesktopServices 0x902c89d2 TCopyReader::GetNextItem() + 1792
    14 com.apple.DesktopServices 0x902c704a TCopyReader::Read(unsigned long long, TCountedPtr<TCFURLInfo> const&, TCountedPtr<TCFURLInfo> const&) + 166
    15 com.apple.DesktopServices 0x902fd8ff TFSCopyOperation::CopyToTarget() + 613
    16 com.apple.DesktopServices 0x902ffb00 TFSCopyOperation::DoCopy(TCountedPtr<TCFURLInfo> const&) + 780
    17 com.apple.DesktopServices 0x90300170 TFSCopyOperation::Run() + 174
    18 com.apple.DesktopServices 0x902f5a05 _NodeOperation + 438
    19 backupd 0x0001978c 0x1000 + 100236
    20 backupd 0x00018c90 0x1000 + 97424
    21 backupd 0x0001325b 0x1000 + 74331
    22 backupd 0x0000d96e 0x1000 + 51566
    23 backupd 0x000089a3 0x1000 + 31139
    24 com.apple.Foundation 0x934398dc -[NSThread main] + 45
    25 com.apple.Foundation 0x9343988c _NSThread__main_ + 1499
    26 libSystem.B.dylib 0x94b90a19 pthreadstart + 345
    27 libSystem.B.dylib 0x94b9089e thread_start + 34
    Thread 3:
    0 libSystem.B.dylib 0x94b91262 _semwaitsignal + 10
    1 libSystem.B.dylib 0x94b90f1e pthread_condwait + 1191
    2 libSystem.B.dylib 0x94b92bb8 pthreadcondwait$UNIX2003 + 73
    3 ...ple.CoreServices.CarbonCore 0x94598aee TSWaitOnCondition + 126
    4 ...ple.CoreServices.CarbonCore 0x9458443d TSWaitOnConditionTimedRelative + 202
    5 ...ple.CoreServices.CarbonCore 0x9457fe0f MPWaitOnQueue + 250
    6 com.apple.DesktopServices 0x902c7ce1 TCopyQueue::Dequeue() + 69
    7 com.apple.DesktopServices 0x902c7642 TCopyWriter::GetNextItem() + 42
    8 com.apple.DesktopServices 0x902c730f TCopyWriter::Write() + 131
    9 com.apple.DesktopServices 0x902c6c25 TCopyWriter::WriteTaskProc(void*) + 75
    10 ...ple.CoreServices.CarbonCore 0x94563eb6 PrivateMPEntryPoint + 68
    11 libSystem.B.dylib 0x94b90a19 pthreadstart + 345
    12 libSystem.B.dylib 0x94b9089e thread_start + 34
    Thread 2 crashed with X86 Thread State (32-bit):
    eax: 0x0000003c ebx: 0x94bd0309 ecx: 0xb010008c edx: 0x94bd04be
    edi: 0xa0639b10 esi: 0xb01000e8 ebp: 0xb01000c8 esp: 0xb010008c
    ss: 0x0000001f efl: 0x00000247 eip: 0x94bd04be cs: 0x00000007
    ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
    cr2: 0xffe2aa10

  • Time machine creating new backup for external hd every time it is connected.

    Hi.
    I have recently gotten a Time Capsule to back up my files.
    I want to back up my internal harddrive as well as an external harddrive with master images from aperture.
    Theoretically time machine should skip trying to back up the external drive when it is not connected, and make a backup when it is. (I only connect the disk when working with the images)
    However, the problem is that every time I connect the external hd to back it up, time machine seems to create a total new backup of the whole drive and not just the changes. It seems to not recognise that it has already backed up the disk before. Does anyone know how to fix this?
    I know it is possible, since I have used this system before, but can't quite figure out how to solve the problem.
    Thanks!

    However, the problem is that every time I connect the external hd to back it up, time machine seems to create a total new backup of the whole drive and not just the changes. It seems to not recognise that it has already backed up the disk before. Does anyone know how to fix this?
    If the drive is not recognised.. you should see multiple external drives in the backup.. is that in fact what is happening.
    What makes you think it is doing a whole new backup??
    One factor you may not have considered is that Time Machine does need to do a deep scan of the disk when it has missed more than a few days. A deep scan can take ages over wireless as it will have to actually compare the backup with the files on the disk. Determine what has changed, make up a list of files that need backup and then start and actually do the backup.. this might even take longer than a straight clean backup.
    Have you checked the TM log for what it is really doing?? Pondini widget will give you that info. See A1 here.
    http://pondini.org/TM/Troubleshooting.html
    I have a simple solution.. that will cost you around $40.. use Carbon Copy Cloner.. not Time Machine. It simply handles this kind of thing better.
    There are a number of other solutions that you can buy.. 3rd party backup software.. you can even do it manually via rsync.. however.. a tool like CCC which is based on rsync is a heck of lot easier than writing your own backup scripts.

  • Time Machine: Can I backup an external hard drive?

    Hi,
    I've been using time machine to back up my internal drive to an external with no probs. its really a boon to use. I make music mainly using logic. I have recently started using an external drive to record all my audio to and to save all my logic projects. My question is:
    Can I get Time Machine to recognise and back up my (other, new) external drive that holds all my audio files as well? I thought it might do it automatically when i connected the new drive and also connected my Time Machine dedicated back up drive, but it only backed up my main system drive as before. I can continue to back up manually but I'm keen to use the Time Machine feature to manage backing up my other, new audio dedicated drive - it'll save me time and worry!
    I hope this makes sense!

    open system preferencs->time machine->options and remove your new drive from the exclusion list. TM will back it up from now on along with your main drive.

  • Time Machine 'growing' during backup.

    I've had this issue before, but has only just become a problem.
    Basically, Time Machine starts, and (in Console) says it needs to backup 28.2MB of files ... here's the console text:
    29/08/2012 18:53:09.181 com.apple.backupd[27535]: Will copy (28.2 MB) from iMac
    29/08/2012 18:53:09.191 com.apple.backupd[27535]: Found 455 files (28.2 MB) needing backup
    29/08/2012 18:53:09.227 com.apple.backupd[27535]: 403.3 MB required (including padding), 16.93 GB available
    However, when it backs up, this size grows (it's currently counting up from about 6.95GB) until it says there's not enough room on the backup disk. If it only needs 28.2MB, why is it appearing to do a full 'first' backup?
    I now cannot backup via Time Machine, as it's saying that I don't have the space. I've tried deleting the 'in.progress' file from the backup disk, and the .plist file from the root Library directory – but no joy: it still gets bigger and BIGGER.
    Any one having the same issue?

    I've heard virtual machines can cause issues, but I don't have any!
    The only solution I've had is to manually (via TM's interface) a handful of my oldest backups. Afterwards, it backed up 58.4Gb and is working okay at the moment.
    As with your backup, it said it was backing up much more than this (around 90-100GB), despite only copying 58.4Gb. I think it's just a case of TM not deleting outdated backups effectively when disk space is tight. My TM disk was rather full – but I hoped TM would deal with that!
    I'll keep an eye on it, as much of what is backed up I wouldn't consider 'new' or altered files (many of my Apps, for instance, in the last big backup. Whether this is a Mountain Lion issue, I can't say, as it's taken two years to fill up my disk, so it's seen a few system migrations in its time.
    Anyway, I'll keep an eye on it and see what happens when my free TM space gets to around 30Gb (which is when the problem occured).

Maybe you are looking for