Time Machine Bug

I believe there is a major bug with time machine being unable to restore a case sensitive file system. If i do a clean install with a case sensitive file system then do a full time machine backup. I am then unable to restore that backup onto an new system with either the disk formatted as case sensitive or case insensitive.
I do have a log of the restore crash but it's a bit big to paste it all here.
Can anyone confirm this bug and if so can it please be fixed as I'm now relying on 3rd party backup software as time machine is unable to perform it's job.
K

It's a full restore from a clean install onto a same spec mbp using the osx install cd to boot from and do the restore. this has been tested on 3 different laptops all suffering from the same issue. restoring a clean non case sensitive install onto the same mbp works fine.
Dec 31 16:28:54 localhost LCA[79]: Folder Manager is being asked to create a folder (cach) while running as uid 0
Dec 31 16:28:57 localhost configd[65]: subnetroute_ifindex: can't get interface name
Dec 31 16:28:59 localhost LCA[79]: Using keyboard layout 2
Dec 31 16:29:00 localhost LCA[79]: Found primary language hint "en"
Dec 31 16:29:45 localhost LCA[79]: Launching the Installer using language code "English"
Dec 31 16:29:45 localhost OSInstaller[145]: Mac OS X Installer application started
Dec 31 16:29:45 localhost OSInstaller[145]: 1 display(s) found.
Dec 31 16:29:45 localhost OSInstaller[145]: Display[1] is using OpenGL acceleration.
Dec 31 16:29:45 localhost OSInstaller[145]: @(#)PROGRAM:Install PROJECT:Install-580
Dec 31 16:29:45 localhost OSInstaller[145]: @(#)PROGRAM:Mac OS X Installer PROJECT:OSInstaller-262
Dec 31 16:29:45 localhost OSInstaller[145]: Hardware: MacBookPro6,2 @ 2.66 GHz (x 4), 4096 MB RAM
Dec 31 16:29:45 localhost OSInstaller[145]: Running OS Build: Mac OS X 10.6.3 (10D2084)
Dec 31 16:29:45 localhost OSInstaller[145]: Env: DYLDNO_FIXPREBINDING=1
Dec 31 16:29:45 localhost OSInstaller[145]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
Dec 31 16:29:45 localhost OSInstaller[145]: Env: PWD=/
Dec 31 16:29:45 localhost OSInstaller[145]: Env: SHLVL=1
Dec 31 16:29:45 localhost OSInstaller[145]: Env: OS_INSTALL=1
Dec 31 16:29:45 localhost OSInstaller[145]: Env: _=/System/Installation/CDIS/LCA.app/Contents/MacOS/LCA
Dec 31 16:29:45 localhost OSInstaller[145]: Using install media product at /System/Installation/Packages
Dec 31 16:29:45 localhost OSInstaller[145]: Opening OSInstall package '/System/Installation/Packages/OSInstall.mpkg'.
Dec 31 16:29:50 localhost OSInstaller[145]: Memory statistics for 'Install Mac OS X' pane:
Dec 31 16:29:50 localhost OSInstaller[145]: Physical Memory Allocation: 818 MB wired, 130 MB trapped, 76 MB active, 31 MB inactive, 3041 MB free, 3148 MB usable, 4096 MB total
Dec 31 16:30:25 localhost Unknown[80]: 2000-12-31 16:30:25.631 Disk Utility[153:903] ********
Dec 31 16:30:25 localhost Unknown[80]: 2000-12-31 16:30:25.692 Disk Utility[153:903] Disk Utility started.
Dec 31 16:30:25 localhost Unknown[80]:
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.556 Disk Utility[153:903] Preparing to remove partition from disk: ‚ÄúTOSHIBA MK5055GSXF Media‚Äù
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.580 Disk Utility[153:903] Partition Scheme: GUID Partition Table
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.581 Disk Utility[153:903] 1 partition will be removed
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.582 Disk Utility[153:903]
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.582 Disk Utility[153:903] Partition 1
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.583 Disk Utility[153:903] Size : 499.76 GB
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.583 Disk Utility[153:903] Filesystem : Free Space
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.584 Disk Utility[153:903]
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.638 Disk Utility[153:903] Unmounting disk
Dec 31 16:31:11 localhost Unknown[80]: 2000-12-31 16:31:11.797 Disk Utility[153:903] Creating partition map
Dec 31 16:31:12 localhost Unknown[80]: 2000-12-31 16:31:12.225 Disk Utility[153:903] Waiting for disks to reappear
Dec 31 16:31:12 localhost Unknown[80]: 2000-12-31 16:31:12.262 Disk Utility[153:903] Partition complete.
Dec 31 16:31:12 localhost Unknown[80]: 2000-12-31 16:31:12.263 Disk Utility[153:903]
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.077 Disk Utility[153:903] Preparing to partition disk: ‚ÄúTOSHIBA MK5055GSXF Media‚Äù
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.086 Disk Utility[153:903] Partition Scheme: GUID Partition Table
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.087 Disk Utility[153:903] 1 partition will be created
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.087 Disk Utility[153:903]
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.088 Disk Utility[153:903] Partition 1
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.089 Disk Utility[153:903] Name : ‚ÄúUntitled 1‚Äù
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.089 Disk Utility[153:903] Size : 500.11 GB
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.090 Disk Utility[153:903] Filesystem : Mac OS Extended (Case-sensitive, Journaled)
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.090 Disk Utility[153:903]
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.803 Disk Utility[153:903] Unmounting disk
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.828 Disk Utility[153:903] Creating partition map
Dec 31 16:31:27 localhost Unknown[80]: 2000-12-31 16:31:27.019 Disk Utility[153:903] Waiting for disks to reappear
Dec 31 16:31:27 localhost Unknown[80]: 2000-12-31 16:31:27.656 Disk Utility[153:903] Formatting disk0s2 as Mac OS Extended (Case-sensitive, Journaled) with name Untitled 1
Dec 31 16:31:32 localhost Unknown[80]: 2000-12-31 16:31:32.822 Disk Utility[153:903] Partition complete.
Dec 31 16:31:32 localhost Unknown[80]: 2000-12-31 16:31:32.823 Disk Utility[153:903]
Dec 31 16:31:49 localhost Unknown[80]: 2000-12-31 16:31:49.062 Disk Utility[153:903] NSDocumentController's invocation of -[NSFileManager URLForDirectory:inDomain:appropriateForURL:create:error:] returned nil for NSAutosavedInformationDirectory. Here's the error:
Dec 31 16:31:49 localhost Unknown[80]: Error Domain=NSCocoaErrorDomain Code=642 UserInfo=0x106db1290 "You can‚Äôt save the file ‚ÄúAutosave Information‚Äù because the volume ‚ÄúMac OS X Install DVD‚Äù is read only." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=30 "The operation couldn‚Äôt be completed. Read-only file system")
Dec 31 16:31:49 localhost Unknown[80]:
c 31 16:36:41 localhost OSInstaller[145]: [RESTORE] 5: restoring Developer
Dec 31 16:36:41 localhost OSInstaller[145]: from source path: /Volumes/test/Backups.backupdb/berry/2010-08-06-162655/plum/Developer
Dec 31 16:36:41 localhost OSInstaller[145]: to destination path: /Volumes/plum
Dec 31 16:39:31 localhost LCA[79]: Child exited with status 11
Dec 31 16:39:36 localhost Unknown[204]: Launching the Installer Crash Log Viewer
Dec 31 16:40:11 localhost ReportCrash[203]: Process: Mac OS X Installer [145]
Dec 31 16:40:11 localhost ReportCrash[203]: Path: /System/Installation/CDIS/Mac OS X Installer.app/Contents/MacOS/Mac OS X Installer
Dec 31 16:40:11 localhost ReportCrash[203]: Identifier: Mac OS X Installer
Dec 31 16:40:11 localhost ReportCrash[203]: Version: ??? (???)
Dec 31 16:40:11 localhost ReportCrash[203]: Code Type: X86-64 (Native)
Dec 31 16:40:11 localhost ReportCrash[203]: Parent Process: LCA [79]
Dec 31 16:40:11 localhost ReportCrash[203]:
Dec 31 16:40:11 localhost ReportCrash[203]: Date/Time: 2000-12-31 16:38:59.284 -0800
Dec 31 16:40:11 localhost ReportCrash[203]: OS Version: Mac OS X 10.6.3 (10D2084)
Dec 31 16:40:11 localhost ReportCrash[203]: Report Version: 6
Dec 31 16:40:11 localhost ReportCrash[203]:
Dec 31 16:40:11 localhost ReportCrash[203]: Exception Type: EXCBADACCESS (SIGSEGV)
Dec 31 16:40:11 localhost ReportCrash[203]: Exception Codes: KERNINVALIDADDRESS at 0x000000000745c40c
Dec 31 16:40:11 localhost ReportCrash[203]: Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Dec 31 16:40:11 localhost ReportCrash[203]:
Dec 31 16:40:11 localhost ReportCrash[203]: Application Specific Information:
Dec 31 16:40:11 localhost ReportCrash[203]: objc_msgSend() selector name: release
Dec 31 16:40:11 localhost ReportCrash[203]:

Similar Messages

Bit by Mountain Lion's Time Machine bug - how to proceed best in the simpler cases?

My MacBook Air mid-2012 had never been updated to Mavericks. I had backed it up just a week before a big coffee spill that killed it (June 2014).
I finally got a replacement never-before-used 2012 Macbook Air running Mountain Lion (great to make the Time Machine restore seamless).
That's when I tried "Restore from Time Machine" and it showed the "last full backup" as being from June 2013!!! Then in Migration Assistant, couldn't locate my disk. I've been bitten by the "Exclusion" bug and my Library/ Applications / System folders have not been backed up since a year ago. I'm one of the ones that "found out after it was too late."
So I'll try the workaround. Thanks to Pondini for his great website:
http://pondini.org/TM/D10.html
http://pondini.org/TM/D10r.html
My plan is to restore from Time Machine to my 2013 full system.
Then swap out the Users folder to bring it up to date to the June 2014 version that I have backed up.
Luckily I have only one user account so this can't get TOO complicated.
After that, I'll reset Time Machine and check it periodically via the Command-R trick to make sure it's backing everything up fully.
Still, I'm left with a few questions/concerns that I'm hoping Pondini or others can help to allay before I proceed....
-What will I have lost in a year from those folders that did not back up? I know I may have lost non-Mac applications that I downloaded and also any software updates to said applications. What problems might I encounter in the way of error messages, etc.? I feel like i don't understand the contents of these folders well enough to realize how in trouble I'm in (or not) regarding these folders being out-of-date by a whole year.
-Is it really as simple as swapping out the Users folder on the new system with my most recent backup from June 2014? Any hiccups I should expect from this process? Will all of my photos go back into iPhoto? Will all of my mail files go back into the Mail app? Or in these cases, is there something I need to initiate to smooth out this process? Photos and Mails are the two big concerns; as for the other stuff, I have yet to find out if it's relevant until a problem occurs.
-Once I have restored Apps/Systems/Library to the 2013 backup and Users to the 2014 backup, then what? I'll reset Time Machine but then should I assign it to the new computer? Should I tell it to inherit the new computer? Should I wipe it clean and start fresh? How to proceed after so that I don't have more and more problems down the line, and hopefully don't lose any of the data that I at least have managed to save/restore up to now...
Thanks in advance for any help and sorry if I'm not more clear; I'm not so technologically literate so I'm not sure how best to phrase these things to get my point across.
And special shout out to Pondini who made the discovery of this bug a lot easier to stomach thanks to your helpful website.

A clone is an option.
Clone - Carbon Copy Cloner (Often recommended as it has more features than some others)
Clone – Data Backup
Clone – Deja Vu
Clone - SuperDuper
Clone - Synk
Clone Software – 6 Applications Tested
Commonly Used Backup Methods

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 Bug - Indexer Unavailable - Is there a Fix?

Like others who have posted, I to am experiencing the "Indexer unavailable (1) Waiting for index to be ready (100)" bug.
Like others who have posted about this:
*Time Machine worked flawlessly for a long time, but has now become essentially dysfunctional;
*I've tried every proposed fix and combinations of fixes for months now and they don't correct the problem; any apparent correction is very shortlived;
*I've dealt with phone support to no avail;
*Even brought it up when I had the computer in for a hardware issue with no evidence that any attention was paid to the problem.
Has anyone been able to fix this?
Or should I just give up and move to Carbon Copy Clone for all my backups?

Ecologist wrote:
*I've tried every proposed fix and combinations of fixes for months now and they don't correct the problem; any apparent correction is very shortlived;
Since you don't specify what "every proposed fix" means, and haven't posted anything here before so we could figure it out, see #D2 of [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

Time Machine bugs-still outstanding in 10.5.2

Having done 2 full backups & restores to a newly formatted machine, I can confirm the following issues are still open as of 10.5.2. The context is doing a 'full restore' from Time Machine when re-installing Leopard from the installation DVD.
1. Printers missing: while most applications, data, and settings are restored fine, printers dissapear
2. Applications don't work: Aperture 2.0 and the Cisco VPN client are two applications which need to be reinstalled--others seem to work fine
3. Excluded folders (aka 'do not backup'): I had excluded 3 folders (pictures, virtual machine files, etc.), then before reformatting my machine I removed the exclusion. Told Time Machine to do a backup (twice). Assumed that the previously excluded folders would now be added to backup--nope.
Net-net: love the tool-just some more bugs need fixin'
GKJ

The previous version of Preview, in Tiger, didn't have this blurry resampling problem. This is a new problem introduced by Leopard. There's an example image of the problem here:
http://img171.imageshack.us/img171/7348/appleleopardpreviewblurjs3.jpg
I just think this is pretty unacceptable when you consider that Preview is the DEFAULT app for viewing images on a Mac. Macs are supposed to be the best for graphics. Yet the default app can't resample an image properly without blurring it.

Time machine bug after upgrading system

Hello,
I just upgraded my macbook pro from Lion to Mountain Lion.
After this upgrade, I created a new admin account and tried to install back my previous account with my entire files thanks to migration assistant with a time machine data.
Unfortunately, it seems that my 150go of personal data are in my hard drive after time machine'work but I can see my last account with my entire file. I have just the choice to loggin to my new ML admin account. Moreover, I can use some application with this new account but the fact is that I can found my important files.
Do you have any solution in order to find my previous account?
Thank you,
Regards,
Niels.

See the pink box in Problems after using Migration Assistant for an explanation. One of the workarounds in the green box (probably #4) should set things right.

IMac 27" won't boot (after Time Machine bug?)

Hi everyone,
Firstly, I don't know if my iMac is an Intel machine or not.
I recently had my failing hard drive (seagate, I think) replaced by Apple.
I had backed up using a hard drive using Time Machine.
I attempted to restore my back up to my now fixed iMac. It failed after about 3%. I ran 'verify' in disk utility and it told me the hard drive with the back up was fine.
I tried again to get my back up onto my iMac. It failed again. Again after about 3%
Now, this is when I think I made my big mistake - I asked my computer to boot from the Mac harddrive. Does this mean I told my computer to boot from something that was only 3% installed?
Anyway, it will not boot. Lots of text pops up on the screen, it goes round and round in circles for a while. Then an icon resembling a no entry road sign pops up and it gives up.
I have tried holding down command and r both with the Mac OS X Install DVD in the optical drive and not in.
I have tried holding down 'c' with the Mac OS X Install DVD in the optical drive.
No luck.
Can anyone help please? Please tell me how I can provide further information. Take a video of what happens, perhaps?
Thank you.

Please make a Genius Appointment and take it in for service.

Time Machine Bug with iTunes ?

On my MacPro, Time Machine does not backup the "Local" folder, inside user/music/itunes/album artwork
(i have erased the backup and relaunch Time Machine: same behavior)
(it does however backup the "download" folder which is also in the same folder)
In the "Local" folder are some artwork i have added manually.
I have checked: they are not included inside the song they relate to (the mp3 file)
So the consequence is that if i had to backup after a hard disk crash, i would loose a great number of the art covers I manually added (the ones that are currently in the Local Folder), which is ...bad
This is particularly strange, since the download folder (containing artwork from apple) is backupped
Does anyone have the same problem ?

I have the same problem and my music is kept all in the iTunes folder using the default settings (i.e. iTunes keeps the folder organized). So I dont' have any songs anywhere else besides the iTunes music folder.
I don't like this thing either, since I have a LOT of album artwork manually set up for my albums and I don't want to get it manually back if I have some issues later on and I have to use Time Machine to get my computer the way it was. I remember Steve Jobs saying: "We back up EVERYTHING!" Not so, Mr. Jobs. Disappointed.

Time Machine BUG: Without warning, one or more of your disks stops being backed up...

Hi all
Just discovered an interesting and potentially dangerous bug in TM running 10.7.4 (like many others I've downgraded from 10.7.5 because of the Spotlight/TM problems noted in this forum).
Here's the bug: You set up TM and specify certain items -- files, folders or volumes -- to be excluded in the "Options" pane of TM Preferences. If you exclude a volume (e.g. a cloned backup volume), that volume must of course be mounted in order for it to be added to the "Exclude" list. But if you subsequently umount the excluded volume, TM SIMPLY REPLACES IT WITH SOME OTHER MOUNTED VOLUME without warning. The result: unknown to you, one of your disks, that you think is being backed up, isn't. You can actually see this happen if you unmount the disk you want to exclude while your exclusions list is open.
This bug is 100% reliable. Tried permissions repair, clear caches, verify backups, reset TM by deleting /Library/Preferences/com.apple.TimeMachine.plist and re-entering excluded items -- same result.
Question: Have others found this bug? Has anyone found a way of adding a volume to the TM exclusions list so that it "sticks" regardless of whether or not the volume is mounted??
The only workaround I can see: Never unmount any disks in your exclusions list -- if you do, something else will be excluded instead. If like me you want easy access to the disks you work with but not others (e.g. backup clones), one option is to make the excluded disk mounted-but-not-visible.
Appreciate others comments before reporting to Apple in case there's something weird in my setup (don't think there is).
Pondini: Checked your great site, couldn't see this noted - apologies if I missed it.
Ta much.

For Windows 7 I corrected the problem using the steps below. Since Windows 8 is setup for touch screen you will need to find these controls.
Corrective Action. Note that several of these steps require the computer to process the action and may take 20 minutes to complete, depending on the configuration.
DELETE INTERNET EXPLORER PERSONAL RECORDS
(This step may not be necessary)
Start Windows Operating System (OS) in Safe Mode (Restart windows using F8)
Select “Start” button
Select “Control Panel”
Select “Internet Options”
Select “Advanced” tab
Select “Reset” tab for “Reset Internet Explorer settings”
Select “Delete Personal Records”
Select “Reset”
DISABLE INTERNET EXPLORER
If not in WINDOWS SAFE MODE start Windows OS in Safe Mode (Restart windows using F8) Select “Start” button
Select “Control Panel”
Select “Programs and Features”
Select “Turn Windows Features On or Off” (Left pane)
Uncheck IE# checkbox (# will be the IE version number)
Select “OK”
Reboot the computer
RE-ENABLE INTERNET EXPLORER
Windows OS will restart in normal mode, or select normal operation
Select “Start” button
Select “Control Panel”
Select “Programs and Features”
Select “Turn Windows Features On or Off” (Left pane)
Check “IE# checkbox” (# will be the IE version number)
Select “OK”
Reboot the computer
RESTORE YOUR DESKTOP
Select “Start” button
Select “Control Panel”
Select “System & Security”
Select “System”
Select “System Protection”
Select “System Restore”
Select “Chose a different restore point”
Select a restore point at least 2 weeks ago (Check “Show more restore points” checkbox, if necessary)

Time Machine Taking a Long Time to Index / Back Up

Hi everyone.
I noticed this on the latest backup to my Time Capsule device. I'm backing up over a WiFi connection to a time capsule device. It is taking a long time to index the backup. Here's the code from the latest backup.
10/17/12 9:43:03.799 PM com.apple.backupd: Starting standard backup
10/17/12 9:43:04.091 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
10/17/12 9:43:12.657 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
10/17/12 9:43:34.015 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
10/17/12 9:43:37.440 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
10/17/12 9:43:37.459 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
10/17/12 9:45:23.296 PM com.apple.backupd: 500.1 MB required (including padding), 3.27 GB available
10/17/12 9:46:48.844 PM com.apple.backupd: Copied 1436 files (3.4 MB) from volume Macintosh HD.
10/17/12 9:46:51.897 PM com.apple.backupd: 448.1 MB required (including padding), 3.27 GB available
10/17/12 9:46:51.898 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:47:53.681 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:48:55.642 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:49:56.511 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:50:56.564 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:51:57.643 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:52:57.903 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:53:59.341 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:55:01.281 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:56:03.171 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:57:03.966 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:58:33.083 PM com.apple.backupd: Copied 824 files (1.2 MB) from volume Macintosh HD.
10/17/12 9:58:40.359 PM com.apple.backupd: Starting post-backup thinning
10/17/12 9:59:51.851 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-213620 (5.6 MB)
10/17/12 10:00:17.440 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-113505 (1.6 MB)
10/17/12 10:00:30.046 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-103509 (1.6 MB)
10/17/12 10:00:43.781 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-093513 (1.3 MB)
10/17/12 10:00:43.781 PM com.apple.backupd: Post-back up thinning complete: 4 expired backups removed
10/17/12 10:00:45.207 PM com.apple.backupd: Backup completed successfully.
10/17/12 10:00:56.988 PM com.apple.backupd: Ejected Time Machine disk image.
10/17/12 10:00:57.550 PM com.apple.backupd: Ejected Time Machine network volume.
I am just curious as to why this is, and what I might do to fix it. I did see one suggestion in another website suggesting diabling spolight indexing of the backup image with sudo mdutil -i off /Volumes/Time Machine Backups, but don't know where to type that in. It then states to reenable it, but don't know where to type that in, either. Any advice would be helpful. I did run a verification not too long ago, and here's that code.
10/14/12 3:44:14.289 PM com.apple.backupd: Backup verification requested by user.
10/14/12 3:44:41.503 PM com.apple.backupd: Running backup verification
10/14/12 4:04:31.602 PM com.apple.backupd: Backup verification passed!
If any of you have or had a similar problem, I'd appreciate your help. For the time being, I may just disable time machine during the evening, and only have it run during the day when I'm at work.

Is your sig still current (10.7.3)? Or did you update to 10.7.5? Because 10.7.5 had a Spotlight/Time Machine bug that slowed down a lot of backups. If that's what it is, there's now a 10.7.5 Supplemental Update that fixes the slow Time Machine problem.
If it isn't 10.7.5, I don't know what the problem might be.

Is it possible to boot or Time Machine restore from an external Thunderbolt disk drive?

(There are several questions - search for "?".)
I purchased a Seagate Backup Plus for Mac Desktop Drive 3 TByte with default USB 3.0 interface, and also acquired the Seagate Thunderbolt Adapter for Backup Plus Desktop Drives and Thunderbolt cable.
I do a redundant backup to the Seagate Drive using both Carbon Copy Cloner (nightly) and Time Machine (hourly) using its Thunderbolt adapter. BTW: One never knows when Time Machine will choke - see discussion titled, "UPDATED: Serious Time Machine bug on Mountain Lion", which I had; Rest In Peace Pondini (James Lewis Pond).
Booting from the external Seagate Backup Plus via Thunderbolt inteface from System Preferences -> Startup Disk:
I select the Time Machine OS X, 10.8.5 Startup Disk (Thunderbolt attached drive), click Restart, confirm my choice, the computer reboots, however, it reboots from the internal Macintosh HD OS X, 10.8.5, NOT the selected external Thunderbolt drive. The SSD drive was used as the Startup Drive, not the selected external Time Machine volume as indicated by the display free disk space command (df(1)) and seeing that the Macintosh HD OS X, 10.8.5 volume is mounted as root. That is very deceptive in that both the internal and external drives will appear in the same manner from a GUI point of view! OS X doesn't even inform me that it did not boot off the selected volume. This is the first half of the problem, that is, Is it possible to boot from an external Thunderbolt disk drive? In my case, the answer is deceptively No. Can anybody else boot off a Thuderbolt attached disk drive? Note that if I remove the Thunderbolt adapter, and attach the drive via its USB 3.0 cable, the MBP boots off the external Seagate Backup Plus just fine, as is expected.
Booting from the external Seagate Backup Plus via Thunderbolt inteface from boot-time "Option - Select startup disk" method:
When I restart the MBP using the startup Option key to select the startup volume, the externally connected Seagate drive ONLY SHOWS UP if it is attached with the USB 3.0 cable, not when it is attached with via the Thunderbolt interface. Can anyone else boot off a Thunderbolt drive with the startup Option key sequence? At least the MBP doesn't deceive me in this case - I know right away that the external Thunderbolt drive is not an option when connected as such.
Time Machine restore from the external Seagate Backup plus via Thunderbolt interface from the "command-R - Recovery Parition" method:
After booting from the recovery partition, I attempt to perform a Time Machine restore from the Thunderbolt connected Seagate Backup drive. When Time Machine attempts to present me with a viable backup Time Machine volume, the external Thunderbolt drive is never offered as an option. So I switch the Time Machine volume to use its USB 3.0 interface, and then Time Machine displays that drive as an option, and the MBP proceeds with the restoration as expected. The interesting thing to note is that while booted in the recovery partition via the Thuderbolt cable, the MBP Disk Utility may be selected, and the Thunderbolt attached drive may be operated on just fine. Can anybody else restore their MBP using Time Machine and the Recovery Partition via the Thunderbolt interface?
This is also a big problem for me in that I am forced to restore my MBP via Carbon Copy Cloner using the USB 3.0 interface, because I cannot even boot off that volume's Thunderbolt interface. Of course, the option may be that I could use yet another eternal USB 3.0 drive, boot from it, and then use Carbon Copy Cloner to restore the Macintosh HD via the aforementioned drive connected by a Thunderbolt cable, but that is less than ideal and not elegant, so I'm not going there.
Another side issue is that the commercially available program, TechTool Pro 7's eDrive, which I installed on the Time Machine volume, will not boot off that eDrive as advertised, but I won't got through those steps here, because that would be beyond the scope of this issue, however, I must say, It does not work either when the Time Machine volume is connected via the Thunderbolt interface, but works just fine when connected via the USB 3.0 interface.

If this helps anybody else make a decision about whether to consider Apple because of Apple's superior customer service:
Apple sells this entire line of drives right in their store, from 1TB to 4TB. I spent 1 and 1/2 hours, yesterday, confirming that the 3TB model IS NOT 100% Thunderbolt compliant. A MBP cannot boot, nor can it Time Machine restore from this drive, though EVERYTHING about the drive is normal.
Apple's South Coast Plaza store management had at least two responses to me personally about how to proceed:
1. Buy a different drive from another drive manufacturer, and to attempt to return the drive to COSTCO. A lead genius suggested going with GTech drives, for instance.
2. Wait for Seagate to fix their problem.
I told Apple management in the store that the drive is advertised as Mac Compatible (see picture) and that it is advertised as being a Thunderbolt drive (see picture). I pressed management that my purchasing decsion to get the best possible MBP Retina was based on the availablity of Inexpensive Devises (raID), and that not having this complete compatibility is a show-stopper for my needs, and that I wanted a refund. Their response? They needed to talk with "Merchendising" to see if they are on or off the hook for these kind of 3rd party assertions, and would get back to me.
I am not holding my breath.
Note: I do not hold this against the Geniuses that helped me, nor against the management I've dealt with, nor the upper level engineers that I've corresponded with through Apple Care - their problem solving skills were helpful - although I could have arrived at similar conclusions given enough $$$. (For instance, try a Lacie TB drive and see if that works - we did, and it did not work. Or, we have a different TB cable and a different TB adapter, let's try those - we did, and it did not work.) I blame myself for not doing enough homework before going with Apple's solutions.

Can't restore from Time Machine using recovery partition

I came up with the idéa to put in an extra disk (SSD) into my mid 2009 13" Macbook Pro running Mountain Lion and create my own fusion drive.
In order to make sure not to lose all of my data I made sure to back up all my files using Time Machine so that simply could restore my entire system to the new drive.
Careful as one should be when about to wipe the entire drive on a computer I wanted to check so that I could make a proper restore from my TM backup disk. So I booted into recovery mode and choose to restore from Time Machine and then I selected my external drive, but then nothing. Where the list of my latest backups should be there was nothing.
I've tried to format the disk several times, changing disk permissions etc.
Does anyone have a clue what could solve this? Is it possible that it has something to do with the fact that I'm (probably) running 10.8.3 and that my recovery partition is 10.8.2?

Is the TM backup complete? When you Enter Time Machine, do you have snapshots going back in time?
See here for info on a problem Pondini has found with Time Machine that may have affected you:
UPDATED: Serious Time Machine bug on Mountain Lion (Updated)
You may just have to restart your TM backups to get those folders backed up.
If you do have that issue, please post at his link. He is trying to get enough background info to pass to Apple to solve the problem.

Time machine missing content

I have an MBA with 256 GB SSD. Updated to Mavericks including iMovie 10 (which filled the disk during conversion of iMovie 9 files).
Just checked Time Machine for possible restore and found, that the content is missing!
The only directories are "Users"(!) this happened possibly through thinning of local backups?!
How can I tell Time Machine to backup the whole boot disk (again)?
Tried
Michaels-MBA:tmp michael$ sudo tmutil removeexclusion /Applications
Michaels-MBA:tmp michael$ tmutil isexcluded /Applications
[Excluded] /Applications
How /Applications (and all the other items) are Excluded and it seems I can't change that?!
Any help appreciated…

You've probably found your solution by now, but if not, according to this test it looks like you were affected with a Time Machine bug...
http://pondini.org/TM/D10.html
More info regarding the bug on this thread:
https://discussions.apple.com/thread/5125969

Time machine makes too many full back-ups

Yes, this has been written about ad nauseam almost since Time Machine's been around. But I am really tired of going through 3 and 4 TB hard drives because of a Time Machine bug/error/glitch/what-have-you. The latest message (from the Time Machine Buddy widget) is this:
Deep event scan at path:/Volumes/LaCie reason:must scan subdirs|new event db|
Why? Nothing's changed with this drive. Nothing's changed with the Time Machine Drive.
Thanks in advance for intelligent help.
James

Thanks for the quick reply Eric.
Yeah, I'm certainly aware of these pages. I'm running Mavericks, and there is nothing after 10.8 listed in the otherwise comprehensive resource. But more to my issue, there was only a small bit (D3) that I could find about doing full backups, none of which applied to my situation. Basically I'm wondering why there is a "new" event data base.
Same drive
not many, if any new files (it's an external sound library storage drive),
Weeks went by with none of these issues
but I have noticed issues when waking from sleep
I'm not aware of any potential issues with the Mac's routine maintenance operations. But again, it's an external drive (via FW)
The 2nd link did not work.

Time Machine restore point failure - a WARNING!

I have an iMac 21.5", Late 2012, which has spontaneously died three times, so Apple are going to replace it (and good on them for that too!). Usual question from the Genius Bar techo - 'do you have a backup you can restore from, or should we data migrate for you?'
The iMac (10.8.2) in question has had, since it was installed in December 2012, an external HDD, selected as (and exclusively so) the Time Machine backup drive. It has faithfully done its backups once a day daily (using Time Machine Editor to adjust frequency of backups). I've used it to 'go back in time' to restore various files over the past six months no problem. Looking into the mounted sparesimage you can see and access the dailies. This iMac had gone through 10.8.2 > 10.8.3 > 10.8.4 updates before it died.
So, to be able to answer the Genius Bar techo, I hooked it up to my 10.8.4 iMac, booted into the recovery partition, selected Restore from TM backup option for this drive, and found out that the last actual 'restore point' was actually months ago!!! Even though TM had been dutifully and (proven) done the TM backups, it's official 'restore point' is actually way months - so all the data accumulated/changed since then is actually not restorable through Migration Assistant, and would have to manually restored piecemeal from the retsore point!!
Bottom line: in this particular case, the HDD is OK - so a clone from the old drive to the new iMac's drive is OK. However, had the old iMac's drive failed in any way, the daily Time Machine backup would have been worthless as a 'restore-and-go' backup.
So - be warned: check the state of your Time Machine backup by looking to see what it's last 'restore point' actually is. If it isn't your last backup, as far as i can tell, deleting the current TM backup, and starting over again is the only way forward for a 'restore point' backup; if you need the incrementals, then get a new backup drive and harness that.
[Notes: I'm talking from a purely Mountain Lion perspective - I can't say for other iterations Leopard-onwards.
Also, for the record, my other iMac's external third-party backup drive recently failed and was replaced, and the (now) 10.8.3 > 10.8.4 TM backup restore point is today current from that point forward - so I can't give another historical perspective on whether it was a particular update that might have caused the restore point issue].

San Lewy wrote:
After checking 'backup folders' in TM, and a few other things, they concluded there was nothing wrong with my system.
But, I asked, what about the missing 'full backup' restore points missing when a cmd-R restart is done. And how do I get them started again? "No worries" was the response. "We have better ways of recovering a full system than by the cmd-R restart method, should you ever need it" were the exact words used.
That's outrageous! Things you didn't exclude are not being backed-up, and they think that's ok?!?!
There is a different method, not a better one. It involves erasing your HD, installing a fresh copy of OSX (4+ GB download, unless you saved the installer), then using Setup Assistant to transfer everything except OSX from your backups.
However, if you do have the bug in question, that won't work either: The hidden private folder, also at the top level, isn't backed-up either, and that prevents Setup Assistant or Migration Assistant from even recognizing the backups as backups!
Is this the problem you are seeing?
Sure sounds like it.
Here's what I'd recommend: Start up Migration Assistant (in your Applications/Utilities folder), go through the first few windows, far enough to see if the backups are recognized. See Using Migration Assistant on Mountain Lion or Lion. If your backups don't appear in the Select Your System window (in the tan box), that's what's happening.
If so, call them back and ask what their "better" method is; if they mention either Setup Assistant or Migration Assistant, tell them you've tried that. Then refer them to any or all of the following:
My thread here: UPDATED: Serious Time Machine bug on Mountain Lion.
My web page on the issue: #D10 at http://pondini.org/TM/Troubleshooting.html Also tell them I have evidence of something changing the Time Machine "plist" on several other Macs running with Mountain Lion with this same problem. While I don't know how to reproduce it on my Mac, I would be GLAD to talk or e-mail with them to help get this identified.

Time Machine Bug

Similar Messages

Maybe you are looking for