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.

Similar Messages

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 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 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 does a full backup after a full restore

Hi,
To test Time Machine (as you should always do with any backup system) I decided to do a full restore of one of my Macs. This went fine (after figuring out how to mount my remote backup disk).
However I noticed that when the restored machine did its first scheduled Time Machine backup after being restored it did what pretty much amounted to a full backup (taking ages).
I believe Time Machine should be clever enough to know that the restored files are the same as the backed up ones, and there is no need to copy new versions.
Cheers, Ed.

Indeed not unexpected, however it would be easy to fix this in the future by linking the restore into the existing baseline (given that it is a direct copy of it) as it writes the files.
It is worth mentioning because if you have a smallish backup disk (I don't) then writing the second baseline may flush out a number of your older weekly backups that you would rather have retained. It will also eventually mean that you will always have those two baselines and therefore restrict the number of valid backups that you can keep.
Cheers, Ed.

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 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 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 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 does not recognize backup disk after Yosemite

I have this issue in both macs I own, a 2010 MBP, and a 2012 Mac mini. After I upgraded to yosemite, Time Machine will not find my backup disk. I have been using the same network attached storage drive for 4 years for time machine backups. I has worked fine with all the macs I've owned until now. I can see the disk in Finder, I can go to disk utility and mount the Time Machine disk, but when I go to Time Machine preferences and try to select the list, the disk is not listed there, even though is mounted.
Any ideas?
Thanks!

A third-party NAS is unsuitable for use with Time Machine, especially if it's your only backup. I know this isn't the answer you want. I know Time Machine accepted the NAS as a backup destination. I know that the manufacturer says the device will work with Time Machine, and I also know that it usually seems to work. Except when you try to restore, and find that you can't.
Apple has published a specification for network devices that work with Time Machine. None of the third-party NAS vendors, as far as I know, meets that specification. They all use the incomplete, obsolete Netatalk implementation of Apple Filing Protocol.
If you want network backup, use as the destination either an Apple Time Capsule or an external storage device connected to another Mac or to an 802.11ac AirPort base station. Only the 802.11ac base stations support Time Machine, not any older model.
Otherwise, don't use Time Machine at all. There are other ways to back up, though none of them is anywhere near as efficient or as well integrated with OS X. I don't have a specific recommendation.
If you're determined to keep using the NAS with Time Machine, your only recourse for any problems that result is to the manufacturer (which will blame Apple, or you, or anyone but itself.)

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

Time machine does a full backup every time I reconnect my portable drive to my macbook pro

How do I stop time machine from doing a full backup every time I disconnect & reconnect my backup portable drive to my macbook pro. It doesn't recognize the old backups.

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

Similar Messages

Maybe you are looking for