Time Machine Freezes during full backup

I just got a new MacBook Pro. I am trying to create an initial Time Machine full backup.
The process freezes after processing 6.39GB out of 462.76GB. Further, Time Machine
also globally freezes after the following steps:
Reboot
Try full backup
-- it freezes
Stop backup
-- backup stops
Try to start backup again
TimeMachine is now completely frozen. Further, all the top-right menus seem frozen.
Try to restart machine
Machine cannot completely shutdown -- it stays in a zombie state trying to shutdown forever
Force shutdown (pressing power button continously until the machine shuts down).
I've tried this process about 10 times.
Same behavior using 4 different types of backup disks.
(network attached via afs, direct usb, direct fire-wire).
Here's the console output is below.
The "freezing" seems to coincide with the output of:
"kernel[0]: AppleVTD: waiting space (512)"
Does anybody have any suggestions on how to fix this problem?
Thanks!
Luis.
====== Console output======
10/23/12 12:14:48.677 AM com.apple.backupd[1052]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
10/23/12 12:14:48.700 AM com.apple.backupd[1052]: Ownership is disabled on the backup destination volume.  Enabling.
10/23/12 12:14:49.283 AM com.apple.backupd[1052]: Forcing deep traversal on source: "Macintosh HD" (mount: '/' fsUUID: 6C558E68-8F4B-337F-8BB6-6721988887F1 eventDBUUID: 54A53EDD-B4AA-4C26-830B-37AE17F0CA69)
10/23/12 12:14:53.278 AM coreservicesd[24]: Received request to reset fmod watch. Latest received id is 14820719323154. Latest sent id is 14820719323154
10/23/12 12:14:53.463 AM com.apple.backupd[1052]: Backup content size: 440.85 GB excluded items size: 20.16 GB for volume Macintosh HD
10/23/12 12:14:53.464 AM com.apple.backupd[1052]: Found 1095112 files (420.69 GB) needing backup
10/23/12 12:14:53.465 AM com.apple.backupd[1052]: 504.83 GB required (including padding), 7.41 TB available
10/23/12 12:14:53.471 AM com.apple.backupd[1052]: Waiting for index to be ready (100)
10/23/12 12:15:31.916 AM mdworker[1136]: Unable to talk to lsboxd
10/23/12 12:15:31.977 AM sandboxd[1137]: ([1136]) mdworker(1136) deny mach-lookup com.apple.ls.boxd
10/23/12 12:15:32.000 AM kernel[0]: Sandbox: sandboxd(1137) deny mach-lookup com.apple.coresymbolicationd
10/23/12 12:16:01.962 AM mdworker[1142]: Unable to talk to lsboxd
10/23/12 12:16:02.019 AM sandboxd[1143]: ([1142]) mdworker(1142) deny mach-lookup com.apple.ls.boxd
10/23/12 12:16:02.000 AM kernel[0]: Sandbox: sandboxd(1143) deny mach-lookup com.apple.coresymbolicationd
10/23/12 12:17:03.350 AM mdworker[1153]: Unable to talk to lsboxd
10/23/12 12:17:03.355 AM mdworker[1154]: Unable to talk to lsboxd
10/23/12 12:17:03.433 AM sandboxd[1155]: ([1153]) mdworker(1153) deny mach-lookup com.apple.ls.boxd
10/23/12 12:17:03.441 AM sandboxd[1155]: ([1154]) mdworker(1154) deny mach-lookup com.apple.ls.boxd
10/23/12 12:17:03.000 AM kernel[0]: Sandbox: sandboxd(1155) deny mach-lookup com.apple.coresymbolicationd
10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (463)
10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (128)
10/23/12 12:19:04.717 AM mdworker[1168]: Unable to talk to lsboxd
10/23/12 12:19:04.721 AM mdworker[1167]: Unable to talk to lsboxd
10/23/12 12:19:04.782 AM sandboxd[1169]: ([1168]) mdworker(1168) deny mach-lookup com.apple.ls.boxd
10/23/12 12:19:04.788 AM sandboxd[1169]: ([1167]) mdworker(1167) deny mach-lookup com.apple.ls.boxd
10/23/12 12:19:04.000 AM kernel[0]: Sandbox: sandboxd(1169) deny mach-lookup com.apple.coresymbolicationd
=====

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
*Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.
Test while in safe mode. Same problem?
After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Similar Messages

  • Time Machine Freezes During Initial Backup

    I have a 500gb external Western Digital HDD I am trying to use as my Time Machine backup drive. The computer I'm using is a 24" iMac with about 250gb of data on it. The external drive is partitioned as a GUID / Mac OS Extended (Journaled).
    When I try to run the initial backup, it will randomly freeze during the process. Sometimes it gets halfway through the backup and freezes, other times, right away. Sometimes there is an error, other times there isn't.
    I have tried re-partitioning the drive many times, manually starting the backup and also letting the backup start on its own. All of my applications are closed when the backup begins, but no matter what I do, I cannot get the initial backup process to complete.
    Ironically, I had the same problem on ANOTHER iMac of mine, with the same model Western Digital drive. The backup would freeze randomly during the initial process but I would keep manually re-starting the backup until it magically finished the backup. Now that computer seems to be working fine.
    However, I still can't get this other iMac to work. I find it strange that two separate computers with two separate 500gb Western Digital drives would have the same problem with Time Machine, unless the problem is with Time Machine itself.
    Any ideas out there how to resolve this?

    Bruno321 wrote:
    However, I still can't get this other iMac to work. I find it strange that two separate computers with two separate 500gb Western Digital drives would have the same problem with Time Machine, unless the problem is with Time Machine itself.
    Why do you assume it's TM, not WD?
    There are many possibilities.
    Did you completely erase the drive before formatting it? Sometimes the utilities, etc., that come on new drives can interfere with TM.
    Is your iMac an Intel? If it's an older PPC, you need the Apple Partition Map, not GUID.
    Is this USB or FireWire? USB is often much slower and less reliable.
    If it's USB, does it have it's own power, or does it draw from your Mac? Often there's just barely enough to run a drive; if you have another USB peripheral, it can take enough power to interfere with the disk.
    Does it have an automatic "spin down" feature? If so, can you disable it?
    Does it have the latest updates? I thing I saw a post here recently that a WD update fixed, but I can't find it now.
    Are you running any anti-virus scanning? If so, exclude your TM drive from it.
    Sometimes excluding it from Spotlight as well, at least during a large initial backup, can prevent conflicts between TM and Spotlight.

  • Time Machine freezes during automated backups

    I have a Mac Pro running Mac OS 10.6.4 that freezes during incremental time machine backups. The initial backup will run fine, but during a subsequent backup the machine will always lock up and need to be restarted.
    I've tried repairing the permissions looking for trouble in log files, but haven't had any luck.
    Any ideas?

    thatweskid wrote:
    I have a Mac Pro running Mac OS 10.6.4 that freezes during incremental time machine backups. The initial backup will run fine, but during a subsequent backup the machine will always lock up and need to be restarted.
    I've tried repairing the permissions looking for trouble in log files, but haven't had any luck.
    Try verifying your internal HD, per #A5 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum). If that fails, you'll have to use your Install disc to repair it, per the yellow box there.

  • Time Machine freezes during back up to Passport Ext drive

    Time Machine freezes during first back up to My Passport Ext drive. It is a 1TB, and seems to keep stopping at 6 to 10GB stage so never actually backs up. I have excluded files to limit first backup to about 40GB.

    you sure this is a Mac Pro and not a MacBook Pro first. Most every report  of issues with bus powered like Passport are best solved using a drive case with its own power instead.

  • Time machine freezes during back-up.

    Time machine freezes during back-up. Have to unplug HD before I can regain controll over Time Machine In System Preferences. Tried loading folders the old fachion way—sometimes freezes during that also.
    At first I thought I had a bad exteral HD, but I am on my fourth and still the same problem. My first Time Machine HD (THAT WORKED) now has the same problem.
    I have been working with someone with apple support for weeks. We just replaced the interal HD, and still have the same problem. My iMac is only five months old
    Any ideas ? ? ? .

    you sure this is a Mac Pro and not a MacBook Pro first. Most every report  of issues with bus powered like Passport are best solved using a drive case with its own power instead.

  • 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 Does Excessive Full Backups

    Time Machine used to just backup changed material on a hourly basis. It seems that recently every time I look at the progress indicator it is trying to do a full backup of my entire hard drive. Any ideas why?

    Have you recently done a restore?
    I have the same problem. I did a full restore, and TM did a full backup afterwards. This is a "documented feature". Then it did skims every hour. However, if I reboot, it does a full backup the first time after the reboot. It's done 5 full backups (50 GB each) in the past 5 days. I can't afford to shut down my Mac until I figure this out. I only have 170GB of free space on my Time Machine drive.
    Is there any way to see how big each backup is, and delete un-needed ones?
    I'd really like to figure out what causes this problem, before Time Machine starts deleting old stuff I want backed up to make room for all these wasteful new backups.

  • Time machine issue: always full backup after upgrade to Mavericks

    I just upgraded to OS X Mavericks - since then, each Time Machine backup is a full back (Instead of just backing up the differential between backups) - I couldnt find the answer on the web, pls help! Thanks

    Claude Crider wrote:
    You say you think indexing is now done. Is that because everything else seems to be working with no delays?
    Because you said "The CPUs stayed maxed and machine hot for about 3 more hours." That sound like it was done indexing your internal HD.
    To be sure, look at the Spotlight index at the right of your menubar.  If it has a tiny dot inside it, it's indexing something.  Click it to see what.  If not, it's caught up.
    Oddly, the indexing of your backups may or may not appear there.
    And when you say leave it for awhile, are you thinking more like 4 hours? or more like maybe 20 hours?
    It depends on how large your backups are, and how you're connected.  Ethernet will be faster than WiFI, of course, but will still take a while.  The indexing may be done at the beginning of the backup, during it, or after it seems to be done (if the backup says it's done, but it doesn't eject the Time Machine Backups disk image, it's probably still being indexed).
    I'd guess a few hours, again depending on how large your backups are.
    At what point should I give up on it?
    When you run out of patience?

  • Time Machine fails during automated backups

    I use a 1.5Tb external drive connected by USB as my backup drive for Time Machine. I reformatted it, and the first backup Time Machine did was successful. However, it can never do the regular automated backups, it keeps saying "Unable to complete backup. An error occurred while creating the backup folder." I tried going into Disk Utility and "repairing disk" and it doesn't help. The only way it works again is if I eject the drive (which it has to be forced to do every time), turn off the drive, and turn on again. It can then usually do an initial backup, and then again it fails the automated backups. I'm beginning to think it is the drive's issue. It is an internal drive that's housed in a external enclosure.

    thatweskid wrote:
    I have a Mac Pro running Mac OS 10.6.4 that freezes during incremental time machine backups. The initial backup will run fine, but during a subsequent backup the machine will always lock up and need to be restarted.
    I've tried repairing the permissions looking for trouble in log files, but haven't had any luck.
    Try verifying your internal HD, per #A5 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum). If that fails, you'll have to use your Install disc to repair it, per the yellow box there.

  • Anyone having Time Machine "freeze" while "Preparing Backup"

    Time Machine won't get past the "Preparing Backup" phase, just get the spinning candy bar in preferences.  It did do a full new backup to start after the Mavericks install and two subsequent smaller backups but now this "freeze".  Stopping the back up cancels it ok, restarting hasnt helped, neither has turning time machine on and off in preferences.  I'm using a 2TB Apple Timecapsule.

    Hi BellMonk,
    Thanks for using Apple Support Communities.  This article has some information for lengthy "Prepare" phases:
    Time Machine: Troubleshooting backup issues
    http://support.apple.com/kb/HT3275
    Message: "Preparing" phase takes a long time
    Time Machine keeps track of files and folders that have changed since your last backup so that it only backs up those files and folders. If Time Machine loses track of files and folders that have changed since the last backup, it compares an "inventory" of your current data to an inventory of your backup. When this happens, Time Machine preferences displays a "Preparing..." status message for a longer period of time. See Mac OS X 10.5: Time Machine preferences may display "Preparing" for a longer time.
    I would probably let it go to see how long it takes to actually complete, or possibly start a brand new full backup and see if the issue persists after that.
    Cheers,
    - Ari

  • Time Machine repeatedly does full backups, including FileVault while logged in

    So let me preface this - for months I'd hoped for a way that Time Machine could backup my FileVault encrypted account without logging out.  Last night Snow Leopard spontaneously started doing this.  I know many may think that I'm looking a gift horse in the mouth, but read further and hopefully someone can help me make sense of this.
    Last night I attached my external 1TB USB hard drove to my 15" MBP (spring 2010 model) running OS X 10.6.7.  It started doing a Time Machine backup automatically, as usual.  Since I was logged into my account that uses FileVault (a massive home folder - 220GB) I expected a fast backup of things only outside my home folder.  As i looked at the details, however, i quickly realized that it was backing up all 270GB of data on my hard drive - including my FileVault account while still logged in! 
    At first i thought i just got lucky - i'd been craving this feature for years and it just happened to me without even doing anything.  Curious guy that i am, i logged out of my acct with my USB drive still attached to see what would happen.  After FileVault cleared out space in my home folder, it did _another_ backup, that took about 10 minutes to complete.  This seemed strange so i logged back in and started another backup manually.  To my utter shock, it started doing the whole 270GB over again! 
    I even cleared out my TM drive, erased, reformatted, checked permissions, etc etc and did the same on my system drive, hoping that it was just a matter of broken permissions.  No change.
    So there's two things going on here and i'm pretty concerned about both:
    1) Why is TM backing up my entire encrypted home folder while i'm still logged in??? Apple has clearly designed TM and FV to NOT work this way for data integrity reasons and the fact that it's happening has me freaked out a bit over the reliability of my backups.
    2) Why is TM doing full backups after each time i login to my account?  If i stay logged in, it appears to only do incremental (normal) backups but if i logout, then re-login and allow the hour to pass and let a backup start on its own, it starts the whole 270GB again.
    I'm getting to the point of wiping the system and starting from scratch but since i presently live in a country with no Apple store and extremely poor internet access, that prospect horrifies me
    any ideas?
    many thanks,
    -Tim

    Thanks for the input Pondini -
    I tried deleting the file as mentioned in #A4 and it still had the problem.  Last weekend i finally got a brand new hard drive and reinstalled OSX 10.6.3 from scratch, then promptly applied the 10.6.7 combo update.  I purposely chose to NOT import my old user from backup and instead set up everything again manually (royal pain, but the only way i could be sure that i wouldn't bring the problem with me).  Today i whipped out my TimeMachine drive and set it up for backups.  I crossed my fingers and it AGAIN started backing up all 250+GB of my system from within my FileVault protected account. 
    My wife's MBP is still running 10.6.4 and i'm beginning to wonder if his is an issue with 10.6.7 since i'm relatively certain i didn't experience this before that upgrade. 
    I've checked my wife's exclusions under Options and her home folder is NOT in that list, yet her TM is not attempting to backup everything until she logs out of her FV acct.
    In response to Linc Davis, _yes_ it was backing up my info into a sparsebundle file, not just the raw unencrypted data, which is extremely strange.
    If i DO add my home folder to the exclude list, will it still be backed up when i log out?
    At this point, i'm thinking my next steps are:
    1) try a different TM backup drive, even though i've wiped and checked my current drive numerous times
    2) downgrade to an older version of Snow Leopard to see if 10.6.7 is the culprit
    Any other ideas?

  • Time Machine randomly performing full backups instead of incremental

    I've been using a Time Capsule since October 2009 with my 13" MBP running Snow Leopard with no issues.
    A few weeks ago, I noticed Time Machine decided to do a full 160GB backup, which then filled the Time Capsule and then deleted older backups. It then kept trying to do full backups every single time, resulting in the error 'Not enough space'.
    I archived the backups from the Time Capsule, disabled Time Machine and completely erased the Time Capsule.
    I set up Time Machine again and it's been working for about a week, but it's doing the same thing again - trying to do another large HD sized backup of 160GB or so (the amount of data my drive has).
    I have noticed in the logs the following line
    *17/02/2010 13:36:16 com.apple.backupd[946] Event store UUIDs don't match for volume: HD*
    Which seems to appear as Time Machine starts to do it's full backup.
    Any ideas? It's getting to the point that Time Machine is becoming unusable as I can't rely on it.

    Cool, I'll give that a try.
    Log files are here. I did rename my machine to remove spaces and punctuation but haven't backed up since then (only a few hours ago).
    Should I resume this backup or erase the TC and start again? (I've also renamed the TC network and drive)
    Feb 20 00:16:14 marty com.apple.backupd[8919]: Starting standard backup
    Feb 20 00:16:14 marty com.apple.backupd[8919]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:16:22 marty com.apple.backupd[8919]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:16:32 marty com.apple.backupd[8919]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
    Feb 20 00:16:32 marty com.apple.backupd[8919]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Feb 20 00:16:38 marty com.apple.backupd[8919]: No pre-backup thinning needed: 1.13 GB requested (including padding), 264.22 GB available
    Feb 20 00:16:47 marty com.apple.backupd[8919]: Copied 8 files (15 KB) from volume HD.
    Feb 20 00:16:47 marty com.apple.backupd[8919]: Starting post-backup thinning
    Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-234422: 264.22 GB now available
    Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-225109: 264.22 GB now available
    Feb 20 00:16:48 marty com.apple.backupd[8919]: Post-back up thinning complete: 2 expired backups removed
    Feb 20 00:16:48 marty com.apple.backupd[8919]: Backup completed successfully.
    Feb 20 00:16:50 marty com.apple.backupd[8919]: Ejected Time Machine disk image.
    Feb 20 00:16:51 marty com.apple.backupd[8919]: Ejected Time Machine network volume.
    Feb 20 00:23:42 marty com.apple.backupd[9017]: Starting standard backup
    Feb 20 00:23:42 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:23:52 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:24:11 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
    Feb 20 00:24:11 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Feb 20 00:24:11 marty com.apple.backupd[9017]: Backup canceled.
    Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
    Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine network volume.
    Feb 20 00:25:24 marty com.apple.backupd[9017]: Starting standard backup
    Feb 20 00:25:24 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:25:25 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:25:30 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
    Feb 20 00:25:32 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Feb 20 00:34:44 marty com.apple.backupd[9017]: No pre-backup thinning needed: 200.38 GB requested (including padding), 264.22 GB available
    Feb 20 00:35:46 marty com.apple.backupd[9017]: Copied 283 files (6.5 MB) from volume HD.
    Feb 20 00:35:46 marty com.apple.backupd[9017]: Backup canceled.
    Feb 20 00:35:49 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
    Feb 20 00:35:50 marty com.apple.backupd[9017]: Ejected Time Machine network volume.

  • Time Machine doing a full backup every time it runs

    My Time Machine seems to be doing a full backup every time it runs on the hour. The backup size is about 19GB. Shouldn't hourly and daily backups be much smaller after you run Time Machine for the first time?
    I remember a while back, my hourly backups were a couple of minutes.....now they are 30 minutes.
    John

    Hi Steve,
    http://pondini.org/TM/12.html
    https://discussions.apple.com/thread/3687285?start=0&tstart=0
    http://pondini.org/TM/Troubleshooting.html

  • Time Machine gives different full backup sizes

    After this recent Time Machine update I am no longer able to back up. When Time Machine computes the backup it tells me that it is 320GB, which is larger than my backup drive, so it can't back up. However, when I go into the Time Machine preferences it computes the estimated backup size as 272.52GB. Before this Time Machine update was applied my backups were happening with no issues.

    Mark Trolley wrote:
    Thank you. They must have changed the amount of extra space required with this latest patch
    It's been 20% since the early days of Leopard.
    because it was working fine up until that point.
    It may be a combination of things: the drive is clearly too small; while it varies widely depending on how you use your Mac, our general "rule of thumb" is that TM needs at least twice the space of the data it's backing-up.
    If you're like most of us, the amount of data on your system has been growing.
    And apparently Time Machine is doing a full backup, so it just got beyond the capacity of the disk to hold it all.
    Looks like I need a larger Time Machine disk.
    Yup. The good thing is, they continue to get less and less expensive.

  • Time Machine Repeatedly Does Full Backup

    I have five volumes with about 3.7TB of data backing up to Time Machine on a four drive Drobo with 4.9TB available.  I've excluded troublesome files such as the Aperture Library.  I've only two internal drives, one SSD and another two SSD raid.  All other drives work via USB, USB 3.0, Firewire 800 (Drobo) and a proprietary 3waresidecar raid drive.  The external drives are not always present.
    It takes days to do a fresh backup of 3.7TB and then things work fine for a few days and then, once again, a full backup is started.
    I've  not changed the computer name, done a restore, or done any service to any drives.
    I would be appreciative of any suggestions as to what I must do in order to get Time Machine functioning.
    Thanks...

    Thanks for the input Pondini -
    I tried deleting the file as mentioned in #A4 and it still had the problem.  Last weekend i finally got a brand new hard drive and reinstalled OSX 10.6.3 from scratch, then promptly applied the 10.6.7 combo update.  I purposely chose to NOT import my old user from backup and instead set up everything again manually (royal pain, but the only way i could be sure that i wouldn't bring the problem with me).  Today i whipped out my TimeMachine drive and set it up for backups.  I crossed my fingers and it AGAIN started backing up all 250+GB of my system from within my FileVault protected account. 
    My wife's MBP is still running 10.6.4 and i'm beginning to wonder if his is an issue with 10.6.7 since i'm relatively certain i didn't experience this before that upgrade. 
    I've checked my wife's exclusions under Options and her home folder is NOT in that list, yet her TM is not attempting to backup everything until she logs out of her FV acct.
    In response to Linc Davis, _yes_ it was backing up my info into a sparsebundle file, not just the raw unencrypted data, which is extremely strange.
    If i DO add my home folder to the exclude list, will it still be backed up when i log out?
    At this point, i'm thinking my next steps are:
    1) try a different TM backup drive, even though i've wiped and checked my current drive numerous times
    2) downgrade to an older version of Snow Leopard to see if 10.6.7 is the culprit
    Any other ideas?

Maybe you are looking for

  • Complete data transfer to another iPhone with different iOS

    i have migrated from iPhone 4 to 5s, and my apps and contact been backed up through iTunes, While Photos and Messages still not. whenever i try a get a message that backup session has expired.... using lastest iTunes. Some Body kindly Guide Please

  • How to restrict multiple executions of a report by same user

    During month end closing user execute multiple sessions of the same report. In order to improve system performance want to put restriction on such executions espcially for system exhaustive reports. So user can execute report second time once first j

  • P35 Neo doenst start

    I'vd just bought a new mainboard and CPU, which are: - mainboard MSI P35 Neo - Intel Core Quad Q6600 and started building up a new system with my old components: - ATI HD 3870 graphic - 2 GB RAM DDR2 533 - 250GB Hardisk Everything was in its place, b

  • Re-install OSX without losing Windows7 partition? (preserving Bootcamp)

    Recently my computer stopped booting into mac OS (apparently unfixable, details on that deduction are below). The question: I plan to reinstall MacOSX (from my startup disc). However, I'd like to be sure that this won't destroy Bootcamp's partitionin

  • Disabled apple id

    My newphew set my mom up with an ipad and apple/itunes id I too set my Mom up with an Itunes/apple ID for her Ipad. I try to login with the information I set up and I get "APPLE ID IS DISABLED".  I've reset the password to the ID I set up 4 times and