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?

Similar Messages

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

  • Time machine not doing incremental backups - instead doing full backups

    hi,
    Time machine does a complete full backup, and then instead of doing incremental backups, it wants to keep doing full backups.
    help.

    why do you think it's doing full backups?
    install TimeMachineBuddy widget and see exactly what it says. also install TimeTracker and see what exactly is being backed up every time
    http://www.charlessoft.com/
    but first, verify both the internal and TM drive with disk utility. verify disk, not permissions. if it reports any errors repair both drives. you'll need to boot from the snow leopard DVD to repair the main startup drive.
    also, see Pondini's troubleshooting tips at the top of the TM forum.
    http://discussions.apple.com/thread.jspa?threadID=2057525
    Message was edited by: V.K.

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

  • 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 forces a Full backup  (173GB) after System restore.

    Hi,
    Just restored my system from the latest backup in Time Capsule. Now Time Machine want to backup the whole disk again (173GB) although the changes between the current status and the latest backup should be minimal.
    Is this the normal behavior?, I would rather avoid the full back up if there any way to do it.
    These are the logs. First it says that the "Event Store UUIDs don't match". I'm not sure this is really normal, because I didn't swap hard drives or anything so I assume that the Event Store UUIDs should match.
    Then it says that the size of the backup is 173.86 GB.
    [October10] [October 10] 10:37:18 AM com.apple.backupd[1196] Starting standard backup
    [October10] [October 10] 10:37:35 AM com.apple.backupd[1196] Network destination already mounted at: /Volumes/Time Capsule
    [October10] [October 10] 10:37:45 AM com.apple.backupd[1196] Disk image /Volumes/Time Capsule/Rubén Laguna Macías’s MacBook Pro_001ff3524896.sparsebundle mounted at: /Volumes/Backup of Rubén Laguna Macías’s MacBook Pro
    [October10] [October 10] 10:37:45 AM com.apple.backupd[1196] Backing up to: /Volumes/Backup of Rubén Laguna Macías’s MacBook Pro/Backups.backupdb
    [October10] [October 10] 10:37:57 AM com.apple.backupd[1196] Event store UUIDs don't match for volume: Macintosh HD
    [October10] [October 10] 10:38:00 AM com.apple.backupd[1196] Node requires deep traversal:/ reason:must scan subdirs|new event db|
    [October10] [October 10] 11:32:39 AM com.apple.backupd[1196] No pre-backup thinning needed: 173.86 GB requested (including padding), 380.26 GB available
    [October10] [October 10] 11:37:57 AM com.apple.backupd[1196] Copied 83.6 MB of 143.7 GB, 3581 of 285647 items
    [October10] [October 10] 12:57:59 PM com.apple.backupd[1196] Bulk setting Spotlight attributes failed.
    [October10] [October 10] 12:58:24 PM com.apple.backupd[1196] Copied 95.2 MB of 143.7 GB, 101822 of 285647 items
    [October10] [October 10] 1:58:30 PM com.apple.backupd[1196] Copied 8.9 GB of 143.7 GB, 289125 of 289125 items
    [October10] [October 10] 2:02:32 PM com.apple.backupd[1196] Copied 291414 files (8.9 GB) from volume Macintosh HD.
    [October10] [October 10] 2:03:26 PM com.apple.backupd[1196] No pre-backup thinning needed: 2.22 GB requested (including padding), 371.79 GB available
    [October10] [October 10] 2:07:38 PM com.apple.backupd[1196] Copied 3601 files (626.5 MB) from volume Macintosh HD.

    Matthew Connolly3 wrote:
    Same problem here. Same machine. Restored from TM drive back to computer - worked fine doing incremental backups immediately after the restore, but now 2 days later, it wants to do a full backup and has gone and deleted all the older incrementals
    Not quite the same problem, as your full backup wasn't the first one after a full restore. Whether it's related or not is anybody's guess.
    Click here to download the +Time Machine Buddy+ widget. It shows the messages from your logs for one TM backup run at a time, in a small window. Navigate to the backup in question, then copy and post all the messages here. They may contain a clue.
    Also see #D3 in the Time Machine - Troubleshooting *User Tip* at the top of this forum for the main known reasons TM will do a full backup.

  • Time machine keeps performing full backup to my new time capsule

    After years of perfect time machine function to a local usb drive, I bought a time capsule and reconfigured time machine to backup there for my wife's macbook air and my macbook pro.
    The macbook air time machine is running perfectly. However after a week or so the time machine on my macbook pro has repeatedly performed a full backup and lost all the backup history. I clearly cannot keep on like this and find it very worrying that this piece of technology, even if it loses connection for some reason, is not robust enough to recover the incremental backup?
    Is this a weakness of time machine design? or is there something obvious I need to check?

    try if this user tip helps.

  • Time machine makes a full backup every time

    I had a 1tb external drive that I was using for Time Machine backups. Fine. No problem. But it got filled up.
    I bought a new external drive - 1Tb. Iwas surprised that within a couple of wweeks, it was filled up.
    I bought a new 2Tb drive.
    Now as I observe what it's doing, it appears ot meaking a FULL BACKUP of my entire hard drive over and over again. I though it was only supposed to do incremental backups? This is nuts! At this rate my 2Tb drive will be filled up in no time. And becasue it's continually backing up many Gb of data it makes the machine run slowly. It is driviing me crazy!!! How do I stop this behaviour? Why is it making a full backup every time? I can't see any preferences to change this. Help!

    Thanks but I think maybe I didn't explain the problem clearly
    My understanding is that Time Machine backs up only the fiels that have changed each time it does a backup. Thi sis how it USED to work. So each hourly backup would take a few minutes, usually, and a 1TB drive lasted well over a year.
    Now it seems to be making a FULL backup of the COMPLETE internal drive EVERY HOUR! So it is currently backing up 135Gb of data and my Time Machine drive is almost half full,, even though I only installed it two days ago!
    When it gets to the point where it needs to start deleting old backups, I would get a new drive and start afresh, saving the old one for reference. I can't buuy a new backup drive every week!
    How do I get it to behave like it used to?

  • 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 starts new full backups

    Two MacBook Pro using Time Machine and Time Capsule: TM never uses the full capacity ot TC but claims "A problem has ocurred preventing TM from using the existing safety copy.", wipes out the existing sparsebundle and starts a new one so old backups go lost. Why this? How to avoid?

    Please visit Pondini's Time Machine FAQ for help with all things Time Machine.

  • Will time machine do a full backup of external volume (extra storage) after new logic board?

    I have a MacBook Pro running leopard, that just had the logic board replaced. I haven't picked it up yet, but I am told that my hard drive and data were not touched.
    I have read Pondini's very helpfull info/site, so I know that time machine will want to start a new set of backups.
    Here is my question, based on my setup:  in addition to the internal HD, I have a firewire drive for additional storage of files. Time machine backs up both volumes to another, larger, FireWire drive
    Now, after the new logic board, will time machine make a whole new copy of the external storage drive as well as the internal?  Or just the internal?
    Basically, I know time machine will think it's on a new machine, but will it treat the external storage as if it were new as well?
    I would appreciate any help or advice you can give me.  Thanks. 

    Still no answer? I do have the same trouble on my iMac G5 PPC with 10.5.8: I just replaced the MOB and Time Machine insists to create a new bkup! Attempted with "tmutil" command but doesn't work on my OS...it is really impossible to tell the machine to learn the new address? I DON'T want to believe it!
    Tks for any help

  • Time Machine not doing any backups.

    Hello,
    Recently, my TM is unable to do any backups on my Imac. It was working before, however when I initiate the backup now... it starts with the message "Calculating changes" and it sat there the whole night.
    When I verify the log it tells me the following:
    "No space left on device...Waiting for index to be ready".
    Can someone help me resolve this issue... I tried deleteing all old backups but while it got to removing 5 million or so files... it gave me an error on delete..
    Can someone help please?
    Thanks,

    _To erase the Time Capsule disk:_
    Open AirPort Utility (Hard Drive > Applications > Utilities > AirPort Utility)
    Click Manual Setup
    Click the Disks icon at the top of the setup window
    Click the Disks tab just below the icons
    Click Erase. The "Zero Out Data" option will work fine, but may take several hours.
    If AirPort Utility cannot "see" the Time Capsule and you are using wireless for this, try temporarily connecting an ethernet cable from your computer to one of the LAN <-> ports on the Time Capsule.
    _To setup Time Machine backups:_
    Open System Preferences (gear shaped icon on the dock)
    Click Time Machine
    Click Change Disk
    Click your Time Capsule to highlight it
    Click Use for Backups

  • 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 very slow when backup disk almost full

    My Time Machine backups on a Time Capsule (first generation, 1 TB) have become extremely slow recently. The disk is almost full, but I don't think that should be a problem as Time Machine deletes the oldest backups by itself. It has been, so I don't think that in itself should cause a problem.
    This becomes particularly annoying because whenever backups are going on, the system doesn't allow me to access the "Open" or "Save" dialogues - probably because it wants to check the Time Machine disk, but can't, or only can very slowly. Whenever I do this, the app in question just freezes.
    Anyone else has this problem, and does anyone know a fix? I don't want to start a new backup if I can avoid it.

    Florian M. wrote:
    Thank you. Did that, and it seems to be working now - though it actually seemed to have got better even before I ran Disk Utility. Before, even rebooting didn't help.
    Yes, if there's a problem inside he sparse bundle, rebooting (the Mac and/or TC) won't help.
    Time Machine is a great technology, but it seems to have strange quirks sometimes
    It does indeed!
    Once again, thank you.
    You're quite welcome, and thanks for the star!

Maybe you are looking for

  • Formula automatically populate the date when inventory goes to "zero"

    Hello- I am trying to create a formula that will automatically populate the date when inventory goes to "zero". Date: Row 3 Columns P-AB Inventory: Rows 5-400 Columns P-AB Column J rows 5-400 is where I want the inventory run-out date to auto-pop wit

  • Opportunity creation: product item category not permitted

    Hi SAP Gurus, After some difficulties, we succeeded in transfering products from R/3 to CRM. Now we would like to create an opportunity, associated with a customer and a product (in fact consultant services). In the 'Products' tab of the opportunity

  • Toshiba Web Camera Application

    HI,  A while ago on my computer the web camera application stopped working after it had previously been for a couple weeks before hand. Whenever I clicked on it my screen would go black and then come back and nothing would happen. Now I am trying to

  • How can we manage the operations subcontracted in B1 ?

    Good morning How can we manage the operations subcontracted in B1? For example. I have a purchased item (a box A0001) I must paint (Service Item  P0001) I have a finished product that I sell (The box painted A0002) I have a BOM  for this item  which

  • SRP526W keine VPN-Verbindung von extern

    Hallo zusammen, in einem kleinem Verlag herscht folgende Konfiguration vor: 1. Cisco SRP526W, statische IP 192.168.2.1, dynamische externe IP -> dyndns.org, funktioniert (mit Oberfläche und FTP getestet), Aufgaben: Herstellen der DSL-Verbindung, NAT,