Time machine issues after HD upgrade

I replaced and upgraded my internal HD today in my MacBook Pro (OSX 10.6.5). I restored OSX from my time machine backup to this new drive.
However, when I next tried to run Time Machine, it tried to back everything up on the new drive, which is about 150Gb of data. Is there any way to avoid doing this and just have time machine back up the files that have actually changed since the last backup? It seems a senseless waste of space on my backup HD to have essentially two copies of everything on my HD...

For Time Machine it is essentially a completely changed version of your old HDD, so it does backup the changes. Only that everything changed.
One solution is to let it back it all up and let it delete older backups when it needs more space and the other is to delete the existing backup and save some disk space...

Similar Messages

  • Time Machine Backups after recent upgrade to Mountain Lion

    Basically to keep a long story short - i need to take my computer in for repair tomorrow. I recently did an upgrade to Mountain Lion a day or two ago. I haven't done a Time Machine backup until today (a couple days after i upgraded to Mountain Lion) because i wanted to make sure that my previous TM backup (Snow Leopard 10.6.8) was the most up to date and best update that i could revert back to if i had any issues with Mountain Lion, or any application compatibility, etc etc.
    I don't have any broken applications and it seems like Mountain Lion is running better than Snow Leopard. However, as i said - i'm taking my computer in for repair tomorrow, i would like to know that i have the most up to date Time Machine backup with the new Mountain Lion so that when i restore it back from my Time Machine backup after i get it back from repair, i won't have any issues with the migration, which could potentially lead me into more technicalities.
    I have a 500GB Harddrive, with about 70GB left of free space....I did the initial backup prior to upgrading to Mountain Lion, and it upgraded 400+GB of info, now, since Mountain Lion - the first backup with Mountain Lion initially said 46GB - then it went down to 14GB by the time it was all said and done....so what exactly did it back up?
    Did it back up all the necessary files to keep Mountain Lion running smoothly when i restore it back to the way it was after i get it back? Did it not back everything up that it needs to? Is it safe to erase my internal drive and do a clean installation so i can take it in, and not worry about not being able to migrate things back over or applications not working correctly?
    When i get it back, i presume it will come with Mountain Lion back on it and i can just boot up into the Recovery Disk and restore it from a Time Machine backup that way, correct?
    Thanks for the help.
    - Jason

    I received the same error and experienced the same issue that you have described but after performing a Time Capsule soft reset and then toggling the TM Off and then back On I was able issue a backup now and see my previous backups.
    Here is the link to where I posted my fix; https://discussions.apple.com/message/19069543#19069543. Someone else had success using a different method. The only comment / complaint that I have since the ML OS X upgrade is that TM now takes at least 20 to 30 seconds before I can click/select a backup.
    I hope this helps.

  • Time machine issue after Yosemite install

    After performing a clean install of Yosemite and migration from my TimeMachine backup I experienced the following:
    I opened iTunes and selected some music to play, then got a dialog box saying the files could not be found.  Spotlight couldn't find them either... they were just gone.  Naturally I went to my Time Machine backups and was surprised the music was gone from the backups, all the way back to the first backup.  Very wierd.  During the migration I went through the "Cleaning up old backups" process, not sure exactly what this process is.
    I was pretty bummed that I had permanently lost a lot of music, some was recordings of friends playing live that could never be replaced.  I then remembered that some time ago, just for the **** of it, I copied my sparsebundle backups to an external drive and stashed it in a drawer.  I browsed it, and lo and behold there were the missing files.  So I narrowly escaped a big problem, but wy did this happen?  What are they doing over at Apple?

    Hatrabbit wrote:
    Naturally I went to my Time Machine backups and was surprised the music was gone from the backups, all the way back to the first backup.  Very wierd.
    This is really bad luck. And what can be seen here, it is not related to Yosemite but Mavericks, since I asume your backups were made with Mavericks. Though, it is possible that this bug still persists with Yosemite.
    I have a similar problem. I am still on Mavericks. I see missing files in ~/Library/Preferences on a regular basis. When I come aware of it, I fix it manually by excluding Preferences folder from backup, run backup, include folder Preferences and finally backup again. But this fix does not last for long. Suddenly after some weeks I see a again missing files in that folder, when browsing the "Latest" backup.
    I have found some related discussion:
    Time machine missing files
    http://forums.macnn.com/90/mac-os-x/509489/potential-time-machine-issue-maverick s-leaving/
    http://apple.stackexchange.com/questions/130955/some-files-are-gone-after-recove ry-from-time-machine-backup-why/150230
    http://apple.stackexchange.com/questions/136453/time-machine-not-detecting-chang es-in-certain-folders
    https://twitter.com/ThatDJJP/status/526429152153714690
    missing mail after installation
    No solution until today. Very frustrating.
    My feeling is, that many users do not recognize, that they are victim of this horrible bug, cause in most cases only few folders are hit by this bug.
    And now since Yosemite is out, people are actually using there backups for the first time since Mavericks and run into a disaster.
    Atm I am trying to test, if maybe fsevent daemon is the problem, in the past there have been issues like http://openradar.appspot.com/10207999
    I did a check on my drive, and I found issues with realpath()/readdir(). Though, those issues may just be old and have not been detected by me for a very long time. My MBP is 5 years old and I upgraded all the way from 10.5 to 10.6 to 10.9.
    With 10.6 I never had such an issue.
    But more likely, the issue is related to the "Cleaning up old backups" process. Cause I also have the feeling, that when my backup drive gets full and  the shrink process took place, then the result are missing files in younger backups then the ones cleaned. If that is true, then maybe the hard-link-approach of Time Machine is somehow involved.

  • Error-1 time machine backups after lion upgrade

    I upgraded to Lion on both my computers. My iMac Time Machine Backups are fine - it's connected by firewire to an external hard drive.
    BUT my Macbook Tim Machine Backups are wireless using our Time Capsule and the backups are stored on the Time Capsule.
    Since upgrading, The backups fail & I get this error: The backup disk image “/Volumes/Brunnertime/LittleOne (2).sparsebundle” could not be accessed (error -1).
    Just like so many other unhappy Lion users.
    One positive abberation - Last night, I went into Time Machine Preferences, re-selected the appropriate backup disk (our Time Capsule), entered the password, started a backup and VOILA it backed up fine. All night long, it did hourly backups.
    This morning? Once again, the backups are FAILING with that same error - The backup disk image “/Volumes/Brunnertime/LittleOne (2).sparsebundle” could not be accessed (error -1).
    Plus, now there are NO backups on the disk. Huh?
    At this point we are disgusted that both Lion and iCloud (that's another longer story) were released before they should have been. Too many bugs.

    Hey, finally I found a permanent fix for this issue. I read about it at another Apple Discussions Forum, but right now I don't remember where.
    It worked for me at least. In my case it seems that some Western Digital (WD) software was causing the issue. I just uninstalled WDSmartWare from my iMac using that application's own uninstaller, rebooted my Mac and, finally, after months of calling Apple Support with no luck, it all started to work normally again, so check if you have some WD software running on your Mac. In my case I didn't even need that WD software, as I had it because I used to back up to a WD Drive which I don't use anymore since I bought my Time Capsule.
    Feel free to reply if you require any further assistance.
    Good Luck.

  • Time machine issues after installing lion server

    I have a macbook pro and an imac in my home network, both running lion 10.7.3.
    For some time, I used time machine to back up the macbook over ethernet to an external usb drive attached to the imac, which worked fine.
    A couple of days ago, I installed the server.app on the imac, but disabled all services after a couple of days.
    But now, all of a sudden, I can't complete my time machine backups anymore, I get this error message:
    "Time Machine could not complete the backup. The network backup disk does not support the required AFP features."
    I am not sure what to do here,
    thanks for your comments,
    geb

    I am having a similar issue, but in my situation, my users cannot log in.  All of my users are network users on Mini's.  I am running 10.6.8 on my server.  I have created users before with no issues, but have not done so in months.  When I try to log the new user in, I get the following error:
    xpchelper: Could not get path of user account (uid:1029) home directory:/Network/Servers/server.xxx.net/Volumes/Data/Users/username; error; The operation couldn't be completed. No such file or directory. Using home directory.
    CFPreferences: user home directory at file://localhost/Network/Servers/server.xxx.net/Volumes/Data/Users/username/ is currently unavailable. User domains will be volatile.
    Authorizationhost: error |-[homedirmounter mount NetworkHomeWithURL: attributes: dirPath: username:]|PremountHomeDirectoryWithAuthentication (url=AFP://server.xxx.net/Users/homedir= /Network/Servers/server.xxx.net/Volumes/Data/Users/username, name=username) returned 5.
    I have no idea of what to do.  I have verified that the user looks the same as my other users in WGM. The user's folder was created on the server.  The user has access to the folder.  I'm not sure what else could be wrong here.

  • Spotlight and Time Machine broken after restore/upgrade

    I've found a few similar threads to this but none of those solutions has worked for me.
    Two things happened at nearly the same time, so I don't exactly know the source of my problem:
    I upgraded my old MacBook Pro (approx. Oct 2010, 2.66GHz I think, 300GB-ish HD) from Lion to Mountain Lion
    The hard drive on my old MacBook Pro developed a terminal fault, so I had to buy a new one (8GB, 750GB HD) and restore a month-old Time Machine backup from my external drive.
    I can't remember whether my last Time Machine backup to my external drive was before or after I upgraded to Mountain Lion.
    Now I'm on OS X 10.8.2 on this new machine and I have two problems that seem to co-exist for a lot of other people too:
    Spotlight won't index: this is f***ing infuriating, I love spotlight and I use it all the time. When I first restored from the TM backup I think the old index restored with the backup as I did get a decent number of search results (both in spotlight and in MS Outlook), but new files didn't seem to get recognised. I tried adding my hard drive to the exclusion list and removing it again in an attempt to get it to rebuild the index, but all that did was wipe the old index without building a new one, so now I get no spotlight results whatsoever. I tried this solution and sadly it hasn't worked either. Basically I can't search for anything. Even applications (which I like to launch from spotlight) don't appear. All I get is "estimating indexing time", and it never gets any further.
    Time Machine won't back up: the first time I tried to backup my new machine it got a few hundred megabytes in before stalling; then a few hundred kilobytes in the next time I tried; and now it just doesn't get anywhere at all. The external drive I'm trying to backup to is recognised fine, I can see all the other files on it, and Time Machine seems to know that it's there, but the backup gets nowhere.
    There are reports of this kinds of crap all over the Apple Support forums, but no definitive answer, especially for 10.8.2.
    I could really do with some help on this. I need a backup before I screw another laptop, and I need spotlight to survive day-to-day life.
    Thanks,
    Craig

    Hi Craig - I had the exact same problem - I'm using an old early 2009 MacBook Pro upgraded to 8 Gb Ram, 1 TB internal Hitachi HD, 10.8.2 - tried the fixes suggested - got it to work with these steps- everybodies mileage is different but hopefully it works for you as well.
    a) I repaired disk permissions with Onyx (free utility)  and then  started  up with Command-R using Disk Utility to repaired/check the Volume (harddisk checked out fine but the volume needed some minor repairs )- Onyx repair disk permission seems to go deeper -had to reinstall some apps - don't know if this solved it-seems to bring it back to the default state - you might get away with doing all from Disk Utility (but starting up with  Command-R)
    b) restart from my internal hd
    c) downloaded the 10.8.2 combo update ( not the incremental shell update or whatever you call it which automatically gets installed with software update - combo update installs everything fresh from the .0 version)
    d) with  Onyx  I deactivated spotlight and erased the spotlight index
    d) restart
    e) started TM backup - prep took pretty long 30 minutes but then 450 GB got backed up in 6 hours to my external HD which is fast enough for me
    f) activated spotlight and 450 Gb were indexed in 9 hours or so
    g) for 2 days everything runs fast and very responsive
    best,
    Franz

  • Time Machine Backup After HDD Upgrade

    I recently updated my drive on my MBP with a larger size where I successfully cloned the system from the old drive over the new one with Carbon Copy Cloner to safe me the hassle of the migration. The task was flawless and transparent to the system and me--as a user, except for Time Machine.
    I've maintained a regular backup with Time Machine on a 500gb external drive, instead of transparently picking the backup where it left off, Time Machine is attempting to redo the backup as a complete new set for the new drive where I no longer have enough space?
    So the question is:
    - Is this behavior by design?
    - Is it possible to trick Time Machine to continue backing up without starting over? So the 6 months old worth of backup data is intact since this is the same set of data?
    Thank you.

    wiriawan wrote:
    I recently updated my drive on my MBP with a larger size where I successfully cloned the system from the old drive over the new one with Carbon Copy Cloner to safe me the hassle of the migration. The task was flawless and transparent to the system and me--as a user, except for Time Machine.
    I've maintained a regular backup with Time Machine on a 500gb external drive, instead of transparently picking the backup where it left off, Time Machine is attempting to redo the backup as a complete new set for the new drive where I no longer have enough space?
    So the question is:
    - Is this behavior by design?
    yes.
    - Is it possible to trick Time Machine to continue backing up without starting over?
    no. TM will do a full backup after hard drive cloning. there is no way around that. you have to either delete some old backups (this can be done from TM interface) or reformat the TM drive and start backups from scratch or use a different backup drive.
    So the 6 months old worth of backup data is intact since this is the same set of data?
    Thank you.

  • Time machine crashes after Yosemite upgrade

    I recently upgraded to Yosemite 10.2.2. on a mid-2010 MacBook, but am having problems backing up using TimeMachine.
    I can access my past backups, which is good news, although I need to select one of the disks being backed up in the left column of the finder window (if I just select my username it doesn't seem to work). However, when I attempt a backup the computer crashes during the beginning of the backup process ("Processing backup").  I don't get any particular error message when Time Machine crashes, the computer just restarts and sometimes I will get an error message once the computer has finished restarting indicating that the computer restarted because of a problem.
    I back up onto a non-Apple (Seagate) connected to the WiFi network drive, which has been working well for about 6 months under the previous OS.
    Anyone have any thoughts on this? I've run the disk utility to repair disk permissions, removed the network disk as backup then re-added.

    And here is the Problem Details and System Configuration in case its helpful:
    Anonymous UUID:       B73BF844-60BD-9880-938A-BEF0C404EA33
    Thu Jan 29 23:20:29 2015
    *** Panic Report ***
    panic(cpu 1 caller 0xffffff8019735d11): "hfs_UNswap_BTNode: invalid backward link (0x00012299 == 0x00012299)\n"@/SourceCache/xnu/xnu-2782.10.72/bsd/hfs/hfs_endian.c:303
    Backtrace (CPU 1), Frame : Return Address
    0xffffff8085e63030 : 0xffffff801932fe41
    0xffffff8085e630b0 : 0xffffff8019735d11
    0xffffff8085e63100 : 0xffffff8019726327
    0xffffff8085e63130 : 0xffffff801957b5e5
    0xffffff8085e63240 : 0xffffff801957aa5a
    0xffffff8085e632f0 : 0xffffff8019578ff4
    0xffffff8085e63340 : 0xffffff801975e7b1
    0xffffff8085e63370 : 0xffffff8019763cd0
    0xffffff8085e63430 : 0xffffff80197429ba
    0xffffff8085e63550 : 0xffffff8019570cb6
    0xffffff8085e635e0 : 0xffffff80197ac9d8
    0xffffff8085e63f50 : 0xffffff801984b386
    0xffffff8085e63fb0 : 0xffffff8019436e86
    BSD process name corresponding to current thread: mds_stores
    Mac OS version:
    14C109
    Kernel version:
    Darwin Kernel Version 14.1.0: Mon Dec 22 23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64
    Kernel UUID: DCF5C2D5-16AE-37F5-B2BE-ED127048DFF5
    Kernel slide:     0x0000000019000000
    Kernel text base: 0xffffff8019200000
    __HIB  text base: 0xffffff8019100000
    System model name: MacBook7,1 (Mac-F22C89C8)
    System uptime in nanoseconds: 3182901727712
    last loaded kext at 3016699200744: com.apple.filesystems.afpfs 11.0 (addr 0xffffff7f9bfb2000, size 364544)
    last unloaded kext at 338817335836: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f9bf3a000, size 61440)
    loaded kexts:
    com.apple.filesystems.afpfs 11.0
    com.apple.nke.asp-tcp 8.0.0
    com.apple.filesystems.smbfs 3.0.0
    com.apple.driver.AppleBluetoothMultitouch 85.3
    com.apple.driver.AudioAUUC 1.70
    com.apple.driver.AppleHWSensor 1.9.5d0
    com.apple.driver.AGPM 100.15.5
    com.apple.filesystems.autofs 3.0
    com.apple.iokit.IOBluetoothSerialManager 4.3.2f6
    com.apple.driver.AppleOSXWatchdog 1
    com.apple.driver.AppleMikeyHIDDriver 124
    com.apple.driver.AppleMikeyDriver 269.25
    com.apple.driver.AppleHDA 269.25
    com.apple.driver.AppleUpstreamUserClient 3.6.1
    com.apple.driver.AppleLPC 1.7.3
    com.apple.iokit.IOUserEthernet 1.0.1
    com.apple.GeForceTesla 10.0.0
    com.apple.driver.AppleBacklight 170.5.0
    com.apple.driver.AppleMCCSControl 1.2.11
    com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.2f6
    com.apple.Dont_Steal_Mac_OS_X 7.0.0
    com.apple.driver.AppleHWAccess 1
    com.apple.driver.AppleHV 1
    com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
    com.apple.driver.SMCMotionSensor 3.0.4d1
    com.apple.driver.AppleUSBTCButtons 240.2
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
    com.apple.BootCache 35
    com.apple.driver.AppleUSBTCKeyboard 240.2
    com.apple.iokit.SCSITaskUserClient 3.7.3
    com.apple.driver.XsanFilter 404
    com.apple.iokit.IOAHCIBlockStorage 2.7.0
    com.apple.driver.AirPort.Brcm4331 800.20.24
    com.apple.nvenet 2.0.22
    com.apple.driver.AppleUSBHub 705.4.2
    com.apple.driver.AppleSmartBatteryManager 161.0.0
    com.apple.driver.AppleAHCIPort 3.1.0
    com.apple.driver.AppleUSBEHCI 705.4.14
    com.apple.driver.AppleUSBOHCI 656.4.1
    com.apple.driver.AppleRTC 2.0
    com.apple.driver.AppleHPET 1.8
    com.apple.driver.AppleACPIButtons 3.1
    com.apple.driver.AppleSMBIOS 2.1
    com.apple.driver.AppleACPIEC 3.1
    com.apple.driver.AppleAPIC 1.7
    com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
    com.apple.nke.applicationfirewall 161
    com.apple.security.quarantine 3
    com.apple.security.TMSafetyNet 8
    com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
    com.apple.security.SecureRemotePassword 1.0
    com.apple.driver.AppleMultitouchDriver 262.33.1
    com.apple.AppleGraphicsDeviceControl 3.8.6
    com.apple.kext.triggers 1.0
    com.apple.driver.AppleBluetoothHIDKeyboard 176.2
    com.apple.driver.IOBluetoothHIDDriver 4.3.2f6
    com.apple.driver.AppleHIDKeyboard 176.2
    com.apple.iokit.IOSerialFamily 11
    com.apple.driver.DspFuncLib 269.25
    com.apple.kext.OSvKernDSPLib 1.15
    com.apple.iokit.IOUSBUserClient 705.4.0
    com.apple.driver.AppleHDAController 269.25
    com.apple.iokit.IOHDAFamily 269.25
    com.apple.iokit.IOAudioFamily 203.3
    com.apple.vecLib.kext 1.2.0
    com.apple.nvidia.classic.NVDANV50HalTesla 10.0.0
    com.apple.nvidia.classic.NVDAResmanTesla 10.0.0
    com.apple.driver.AppleBacklightExpert 1.1.0
    com.apple.driver.AppleSMBusController 1.0.13d1
    com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.2f6
    com.apple.iokit.IOSurface 97
    com.apple.iokit.IOBluetoothFamily 4.3.2f6
    com.apple.driver.IOPlatformPluginLegacy 1.0.0
    com.apple.driver.IOPlatformPluginFamily 5.8.1d38
    com.apple.driver.AppleSMBusPCI 1.0.12d1
    com.apple.iokit.IONDRVSupport 2.4.1
    com.apple.iokit.IOGraphicsFamily 2.4.1
    com.apple.driver.AppleSMC 3.1.9
    com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.3
    com.apple.driver.AppleUSBMultitouch 245.2
    com.apple.iokit.IOUSBHIDDriver 705.4.0
    com.apple.iokit.IOUSBMassStorageClass 3.7.1
    com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.3
    com.apple.iokit.IOBDStorageFamily 1.7
    com.apple.iokit.IODVDStorageFamily 1.7.1
    com.apple.iokit.IOCDStorageFamily 1.7.1
    com.apple.driver.AppleUSBMergeNub 705.4.0
    com.apple.driver.AppleUSBComposite 705.4.9
    com.apple.iokit.IOAHCISerialATAPI 2.6.1
    com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.3
    com.apple.iokit.IO80211Family 710.55
    com.apple.iokit.IONetworkingFamily 3.2
    com.apple.iokit.IOAHCIFamily 2.7.5
    com.apple.driver.AppleEFINVRAM 2.0
    com.apple.driver.AppleEFIRuntime 2.0
    com.apple.iokit.IOUSBFamily 710.4.14
    com.apple.driver.NVSMU 2.2.9
    com.apple.iokit.IOHIDFamily 2.0.0
    com.apple.iokit.IOSMBusFamily 1.1
    com.apple.security.sandbox 300.0
    com.apple.kext.AppleMatch 1.0.0d1
    com.apple.driver.AppleKeyStore 2
    com.apple.driver.AppleMobileFileIntegrity 1.0.5
    com.apple.driver.AppleCredentialManager 1.0
    com.apple.driver.DiskImages 396
    com.apple.iokit.IOStorageFamily 2.0
    com.apple.iokit.IOReportFamily 31
    com.apple.driver.AppleFDEKeyStore 28.30
    com.apple.driver.AppleACPIPlatform 3.1
    com.apple.iokit.IOPCIFamily 2.9
    com.apple.iokit.IOACPIFamily 1.4
    com.apple.kec.corecrypto 1.0
    com.apple.kec.Libm 1
    com.apple.kec.pthread 1
    Model: MacBook7,1, BootROM MB71.0039.B0B, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.60f6
    Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3032362E4130314C4620
    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3032362E4130314C4620
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.24)
    Bluetooth: Version 4.3.2f6 15235, 3 services, 27 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: TOSHIBA MK2555GSXF, 250.06 GB
    Serial ATA Device: HL-DT-ST DVDRW  GS23N
    USB Device: Ext HDD 1021
    USB Device: Built-in iSight
    USB Device: BRCM2070 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: Apple Internal Keyboard / Trackpad
    Thunderbolt Bus:

  • Time machine issues after migrating to a new MBP

    I just migrated to a MacBok Pro (new, late 2008) 2.4 GHZ with 4 GB RAM. I backed up my older iMac and then during an erase and install, i chose to use the time machine to migrate my data from the installation process. Everything went well and it all migrated over, but when I turned on TM, it failed. I also noticed that the MBP was now named iMac (2). I guess the name transfered over as well. I am not so concerned about this and can change the name in the Sharing Prefs, but it will not pick up where the last TM back up ended. It wants to create a new back up folder and re-back everything up again.....eats into my storage...
    Can this be fixed? Can I just continue on where TM last left off?
    Thanks.
    I did go through and repair permissions, ran the daily/weekly scrips, etc....

    Yep, I found that out this AM when I called support. I also sent feedback to Apple RE this. It really should be able to merge and pick up where it left off.....
    Other than forcing me to really look at all the crap on my mac (a good thing), I am loving the new MBP.

  • Time Machine issues after replacing HD

    Hi all,
    I recently bought a larger replacement HD for my old MacBook. Last night I cloned the original drive using SuperDuper and then swapped the drives over. However, every time Time Machine now tries to backup, it thinks it's a full backup and starts deleting old backups to make room.
    I've seen this tutorial on the web:
    http://www.macosxhints.com/article.php?story=20090213071015789
    I followed it about halfway, then it asked me to type in "my_partition" saying "Replace my_partition with the name of the partition that you'll be swapping the UUIDs on."
    At that point I got totally confused. What's the name of the partition, and when it says the partition I'll be swapping the UUIDs on, which partition is it referring to? The Time Capsule partition? I don't want to mess with the whole Time Capsule partition surely, cos that has backups from other machines on it...?
    Anyway I wasn't 100% sure and I was worried I might screw something up. So I've switched TM backups off and have come to ask you guys in your wisdom how to do it
    Thanks!
    :-Joe

    xairbusdriver wrote:
    Well, you're obviously more informed about the technical aspects of all this. I am just trying to confirm the easiest way to start using an added drive, not sure I want to have the whole, current back up added to the new one, anyway. It's big enough as it is. How long do I really want to trust any data to a mechanical device?
    Yes, the easiest way is to just let TM start fresh on a new drive, and keep the old one "on the shelf" until you're sure you don't need anything from it.
    Nor do I understand the TM backup to be a 'sparse image.' Not saying it isn't, I'd just not heard it described that way.
    Some are, some aren't. If you back up to an internal HD or a directly-connected external HD (Firewire or USB), your backups are in a "normal" folder named Backups.backupdb. If you back up to a network drive, such as a Time Capsule, the Backups.backupdb folder is enclosed in a +sparse bundle disk image,+ a rather odd sort of container.
    But I have also seen many threads here about the troubles people have in moving old TM back ups to a new drive.
    That depends on a couple of things; it's mostly impossible to continue backing-up to the same set of backups if you change from directly-connected to wireless, or vice-versa.
    But you can copy the backups from an old drive to a new one, and continue backing-up in the same way. See #18 in the Frequently Asked Questions *User Tip,* also at the top of this forum.

  • Imac keeps crashing in time machine backup after upgrade to mountain lion

    2008 imac kept crashing (shutdown and restart) during first backup after upgraded to mountain lion. The backup size was about 10GB but time machine crashed after a while (at most 2GB) and never completed backup. So, I don't have any backup since right before I upgraded from Lion. Any suggestion?

    Something strange happened. I was able to get time machine to work by going out to the login screen (the account kept logged in) and let it run the backup with the screen off (screen auto off after a few min). I tried it on two different external drives and that did the trick on both. Since the initial Mountain Lion backup was huge (155 GB), I was quite surprise that it worked at all. I assume your MBP was a Lion to ML. I also just did a 2012 MBP upgrade but that one was smoother. I did not recall having crashing issue. One thing I did find during this was that my WD passport USB drive was corrupted. Not sure it was the cause or not. I had to erase and reformat to get it back to work. Maybe do a verify disk to confirm. Good luck.

  • Time Machine Locked after MacBook Air reformatted. My MacBook Air was overfull due to an Address book issue (duplication) so after many attempts to clear space, I ended up wiping out the system and reloading Lion.

    Time Machine Locked after MacBook Air reformatted. My MacBook Air was overfull due to an Address book issue (duplication) so after many attempts to clear space, I ended up wiping out the system and reloading Lion. This resulted in the Time Machine thinking that it was now connected to a different computer. Apparently this diables the existing information. 
    Now I can see that the back-ups exist (back to Sept 2012) but they are greyed out, therefore unavailale to restore. Again, this seems like an issue that shouldn't be happening. The whole point of the Time Machine is to enable reinstatement of data after catastrophic failure. What if my computer actually had to be replaced due to a hardware issue? How would I beableto restore anything?
    The path already (unsuccessfully) taken;
    Open Library on the computer, Open Time Machine, Select Correct date, drill down to correct data you wish to restore, click "Restore".
    This did not work because the correct date was greyed out. Restore key was greyed out.

    Time Machine Locked after MacBook Air reformatted. My MacBook Air was overfull due to an Address book issue (duplication) so after many attempts to clear space, I ended up wiping out the system and reloading Lion. This resulted in the Time Machine thinking that it was now connected to a different computer. Apparently this diables the existing information. 
    Now I can see that the back-ups exist (back to Sept 2012) but they are greyed out, therefore unavailale to restore. Again, this seems like an issue that shouldn't be happening. The whole point of the Time Machine is to enable reinstatement of data after catastrophic failure. What if my computer actually had to be replaced due to a hardware issue? How would I beableto restore anything?
    The path already (unsuccessfully) taken;
    Open Library on the computer, Open Time Machine, Select Correct date, drill down to correct data you wish to restore, click "Restore".
    This did not work because the correct date was greyed out. Restore key was greyed out.

  • Time Machine Bug after Restore

    Hi all,
    I've been learning Time Machine and will share two possible bugs if it is helpful.  I am working on a 2011 MacBook Pro, upgraded to Mountain Lion some months back, with 50 GB data on SSD being backed up to and restored from a LaCie SSD 80 GB partition so the speed is very nice: 14 minutes for initial backup and 7 minutes for a Reboot + Command + R restore.
    Bug #1.  Both (initial) backup and restores begin with large 60 minute estimated times in Time Machine Prefs Progress Bar but, once it gets going, finishes in 14 and 7 minutes respectively.  If symptom is due to some quadratic journal searching algorithm, it may explain why APL-CARE warned me about potential 16 hour restores and could be a bug.  If it is due to Time Machine just counting what has been transferred so far, then maybe not a bug (but maybe a possible enhancement request).
    Bug #2.  It appears that the first time Time Machine runs after a Cmd+R restore, it tries to rebuild an entire journal or record of what it has and, if you interrupt this initial backup, you break Time Machine.  The next time you try to backup, Time Machine thinks Everything needs to be backed up (even though your disk is identical to what it just restored), and it Fails in my case with message "Time Machine couldn't complete the back to [my LaCie drive because my 50 GB of data is already there and it thinks it needs a full 50 GB more]" in so many words.  APL-CARE (and its expert advisor) tried to call this a feature and sent me to your article HT3275 but that seems like a different issue.  Since I did not believe Time Machine was so stupid, I ran the sequence again and carefully avoided interrupting Time Machine during its initial backup following my Cmd+R restore and, indeed, it took about 8 minutes to backup 4.5 MB (and rebuild whatever it does that first time).  So this feels like a straight-up bug, Time Machine should scare me with a popup if I interrupt it while it is rebuilding its critical list for the first time after a restore.  If APL-CARE were correct, it would mean everyone loses all history after a restore, everyone needs to Erase their backup disk and start from scratch, and methinks that too would be a bug.
    Hopefully this is helpful, Time Machine is otherwise very cool and I love the Star Trek GUI. 
    Regards,
    Dave.

    And this is an ERROR in time machine.  I just did a test restore again, went quickly, then Time Machine is GONE, GONE, gone trying to restore 5MB, waiting over an hour when a fresh backup takes about 15 minutes.
    So only solution is DESTROY all my backups, then start over.  Really dumb, and this page has no option to change my post back to a question, also really dumb.
    I am going to swear now:  cr*p.  OK.  Fix your **** software please.  I'll deal with workarounds till then.
    -dave

  • Time Machine issues with OS 10.6.8

    Hi all,
    after updating to 10.6.8 I noticed a Time Machine issue.
    Backup takes very long but only a few MB were backed up.
    And after it was finished, Finder crashed and I had to do a hard reset.
    There´s also a "in progress" file on my USB Backup HDD after finishing.
    Checking my HDD´s and repairing it wasn´t the problem.
    Today I tried a new USB HDD to make a fresh Backup via Time Machine.
    After a few hours it was finished, but only 7,8MB were backed up and still there is an "in progress" file on my new Backup HDD.
    Here´s a troubleshoot:
    Starting standard backup
    Backing up to: /Volumes/My Book/Backups.backupdb
    Ownership is disabled on the backup destination volume.  Enabling.
    Backup content size: 368.5 GB excluded items size: 75.7 GB for volume Macintosh HD
    No pre-backup thinning needed: 351.34 GB requested (including padding), 930.54 GB available
    Waiting for index to be ready (101)
    CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    Copied 7.2 MB of 292.8 GB, 5 of 1058420 items
    Copied 11 files (27.1 MB) from volume Macintosh HD.
    No pre-backup thinning needed: 100.0 MB requested (including padding), 930.52 GB available
    Copied 165 bytes of 0 bytes, 4 of 0 items
    Error: (-36) SrcErr:YES Copying / to (null)
    Copied 7 files (236 bytes) from volume Macintosh HD.
    Error -50 deleting backup: /Volumes/My Book/Backups.backupdb/Computer/2011-07-19-180247.inProgress
    Starting post-backup thinning
    No post-back up thinning needed: no expired backups exist
    Backup completed successfully.
    Can anyone help me?

    A  whole  lot  about  Time  Machine for help with TM problems.  Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM.  See also Mac 101- Time Machine.
    There are two important errors noted in the backup:
    I-O error -36 « fuzzybrain|daisychain|blogdrain
    The following comes from the LaCie web site but is applicable to any other external drives whether home brew or commercial.
    Getting error -50 when copying data in OS X.
    Some LaCie drives ship out formatted FAT32 so they will be ready to use on either a Mac or a PC. If you are getting error -50 when copying to a LaCie drive, or any drive formatted for PC, it is because of the following:
    Certain characters that can be used in a Mac OS X filename are not allowed in MS-DOS filenames. This can prevent the file from being copied, and can occur when a filename contains non-printing ASCII characters, or any of these characters: ? / \ < > " | > *.
    Either copy the data off of the drive and use Apple's Disk Utility to erase the drive in Mac OS Extended format, or change the filenames of the documents that cannot be copied.

  • Time machine broken after 10.9.5 update

    Time machine will not run after installing 10.9.5.   TM was successful 10.9.4 20 minutes before I updated.  When TM does a backup, the dialog says  "711GB free of 1TB" and "backing up X of 6GB".  After a while it says "time machine unexpectedly ran out of disk space" and quits.  This happened twice.  The third time TM tried to backup, it took 30 minutes to get to "backing up 90K of 6GB", so I gave up.
    Anybody else having issues like this?

    Hey northsidemike,
    Thanks for the question and detailed information. I understand that you are experiencing issues creating a Time Machine backup after updating to OS X 10.9.5. The following resource includes multiple links for troubleshooting Time Machine issues. I’ve included a few that are related to your issue:
    OS X Mavericks: Time Machine problems
    http://support.apple.com/kb/PH14187
    Time Machine is slow or seems stuck
    If your Time Machine backup disk runs out of space
    If Time Machine is slow
    If Time Machine remains in the “preparing” stage
    Thanks,
    Matt M.

Maybe you are looking for