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

Similar Messages

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

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

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

HT3275 Can some HELP, I keep getting this error with my Time Machine Back up, "The backup disk image "/Volumes/JKPN Safe/JKPN IMAC.sparsebundle" is already in use.

Can some one HELP me , I keep getting this error with my Time Machine Back up, "The backup disk image “/Volumes/JKPN Safe/JKPN IMAC.sparsebundle” is already in use.

See > http://pondini.org/TM/C12.html

HT3275 Have OS 10.7.5. Computer off three days and now message comes that Time Machine could not complete backup because the "/volumes/PH's timecapsulPro.sparsebundle" is already in use. Whats that about?

Have OS 10.7.5. Computer off three days and now message comes that Time Machine could not complete backup because the "/volumes/PH's timecapsulPro.sparsebundle" is already in use. Whats that about?

Two Solutions for "sparse bundle already in use" Error
Simple solution (from Bob Timmons):
1. Make sure that no other Macs are backing up the Time Capsule at the time
2. Pull the power cord from the back of the Time Capsule
3. Count to ten
4. Plug the power cord back into the back of the Time Capsule
If Simple doesn't work:
The Backup disk image ... sparsebundle ... is already in use.

HT3275 time machine error says: The backup disk image "/Volumes/Data/Apple 's iMac G5.sparsebundle" could not be accessed (error -1).

While backing up to Time Machine, I receive this message: time machine error says: The backup disk image “/Volumes/Data/Apple ’s iMac G5.sparsebundle” could not be accessed (error -1).

Welcome to Apple Support Communities
That message is caused by several reasons. Read the Pondini's site to fix the problem > http://pondini.org/TM/C17.html

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 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 Restore After New Logic Board

Older iMac (2009) had hard drive and logic board replaced. Running latest system (10.10.2) before and after logic board replacement.
When attempting to restore from a Time Machine backup made prior to the new logic board, although the iMac sees the Time Capsule and the "Data" file, attempts to proceed with the restore are met with error message "There was a problem connecting to the server [name of Time Capsule] - contact your administrator."
Any experience with this issue? Anybody successfully perform a restore following a new logic board?
Thanks very much.

I would refer you to visit Pondini's Time Machine FAQ for help with Time Machine and full system restore. It also provides instruction on how to restore a backup from another system or Time Machine backup drive.

Time Machine doesn't recognize old sparsebundle after new logic board

Installed new logic board in pre-Isight 20" iMac due to capacitor swelling and kernel panic. I had also erased the internal HD. I was able to restore all my files to internal HD from Time Machine backup on the 1TB Time Capsule. Now I'm trying to back up my restored iMac to Time Capsule, but there is insufficient space. Time Capsule has three sparsebundle files: one for the 20"iMac prior to new logic board, one for a Powerbook, and one for a newer 24"iMac. Time Machine wants to create a new sparsebundle for the restored iMac, but there is not enough room and I would like it use the residing sparsebundle so that I will have backups prior to the point the new logic board was installed. I tried just changing the name of the old IMac Time Capsule sparsebundle file to the new sparsebundle filename that Time Machine creates when attempting backup, but that did not work. Any suggestions?

1. I thought of just deleting the old sparsebundle in order to make room, but it was a less elegant solution because: a) I'd have to do a complete (i.e. lengthy) backup when really only a few things have changed (mostly software updates) since the restore. b)if something should go wrong with that process, then I've lost my backup file to restore the computer. True, I could archive the old sparsebundle to another drive, and then delete it from the time capsule, but somehow I think there should be a quicker, less labor intensive way that doesn't involve bringing in another hard drive.
2. I believe you can restore any Mac with any time machine backup. If you boot from the system disk, go to utilities, and select restore from time machine backup, it then allows you to pick any of the files on the disk that time machine has backed up to. After all, even though Time Machine thinks this is a new computer, the restore that I just did makes it essentially the same computer that I had before the failure of the logic board--the desktop looks exactly the same. BTW, the Apple authorized service center that did the logic board replacement had put a clean version of 10.6 on the internal hard drive, and I was unable to use that system to do the restore--it just hung up. I had to do the restore using my system disk CD (and basically downgrading to system 10.5.8)

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

Similar Messages

Maybe you are looking for