time machine slow in 10.7.5

THANKS, this make my Time Machine backup possible and as fast as before!

BUT after using the second terminal-code to activate Spotlight again,
the troubles came back and Time Machine an Spotlight didnt work any more
(as slow as anyhow possible, 4 weeks ...).

LETs use this website to send Feedback directly to apple support an get them
start with update 10.7.6! http://www.apple.com/feedback

; )

Just wanna say that i had extremely slow TM backup to a usb-drive on my Macbook Air running Lion. Did the sude tmdiagnose - no help. Restarted - no help. Turned of spotlight - no help. Turned on spotlight - no help. Let it do the spotlight indexing again - BINGO! It started to work. It was very fast up to 1.4 Gb of 65 Gb. Now it seems to have slowed down to a halt around 1.77 Gb.

I am using a shareware program called Spotless to disable and enable Spotlight. It is easier than termnal commands and probably safer.

This might be easier for you than doing a downgrade to 10.7.4.

I suspect Apple will have a fix in a few days.

Apple Support told me to copy this into the Terminal:

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

I have no clue what this means (I don't speak the language), but Time Machine is working again like a charm.

Apple seems to be working on solving the problem.

This code means that Apple started to read this thread...

They are at the page 4: https://discussions.apple.com/thread/4324046?answerId=19702754022#19702754022

Well, I've do a collection of issues since I've start the 10.7.4 reinstall.

Issue with language of MS Office 2011:mac -> restart the 10.7.4 install from scratch

Issue with dmg files during the 2nd installation -> restart for the 3rd time the install

I lanch the 3rd installation round midnight and I go to my bed

Morning, I go to my MBA to launch the data migration from my clone ... Crash during the installation

Okay, go to the office and in parallel with my job done today on a windows pc ... Yes yes ... I restore my clone to my HD. Okay it's running.

I try to do an internet recovery but the guest wifi is very slow at my client site.

@ home, nice internet speed, the internet recovery has been done in 45 minutes. After the data migration (without software, not a good idea to recover software when a downgrade has been occured) has been done and for finishing, I reinstall all of my softwares.

Now, a Time Machine is running with a size of 66GB at normal and usual speed.

So now, I'm back to 10.7.4 and I've a system up & running, light (-300k files & -20GB) and TM works fine.

In conclusion, for me the unique workaround is a clean install and a downgrade to Lion 10.7.4 ... Not yet tested and tried ML.

Tobit wrote:

This code means that Apple started to read this thread...

They are at the page 4: https://discussions.apple.com/thread/4324046?answerId=19702754022#19702754022

Somehow, I don't think Apple learned that command from OSXDaily. 😉 But it does suggest that the recognized solution seems to be to disable Spotlight, at least temporarily.

oshilumbo wrote:

Apple Support told me to copy this into the Terminal:

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

I have no clue what this means (I don't speak the language), but Time Machine is working again like a charm.

Apple seems to be working on solving the problem.

What that command does in Terminal is disable Spotlight. That's what was making TM so slow. So now your Time Machine is fine but you may notice Spotlight doesn't work (or only brings up limited results).

See this article for the disable and reenable commands.

http://osxdaily.com/2011/12/10/disable-or-enable-spotlight-in-mac-os-x-lion/

Why is this discussion group no longer generating posts? The problem hasn't been solved, after all

Perhaps because

oshilumbo wrote:

Apple seems to be working on solving the problem.

Perhaps there is simply nothing left to discuss. Something is broken that we can't fix.

It's frankly refreshing not to read post after post of pointless Apple-bashing.

How has yours been running since Apple had you reinstall OS X? Unless I missed something, the last you reported was this:

FYI, Apple techs had me run an archive and restore tonight, effectively reinstalling Lion 10.7.5. Seems actually to have resolved the problem.

Has it been behaving since?

Actually, I am sorry to say it did not fix the problem. It ran OK for one automatic backup and two manuals. The next day when I rebooted, it was back to the same--TM backups 1 hr+ etc. In other words, no improvement.

Anyway, with respect, I'm not sure it's pointless apple-bashing. It key to maintaining the sense of urgency that the problem be resolved. In three years as a devoted Mac user, this is by far the worst bug I've seen--in fact, pretty much the only bug. But it's a serious one.

Here's what worked for me. In Spotlight's Privacy settings, the TM disk was listed in my exclusions list because I had put it there a long time ago (and rightfully so). You don't see it unless the TM disk is mounted, and it may take 30 seconds to show up after you have mounted. Once you've gotten that far, remove it from the Privacy list. Then eject the TM disk and reconnect it. When it mounts the second time, drag it to the Privacy list again. Close the Spotlight preferences (anytime is ok) and run your backup. It starts off slow as usual but this time it plowed through 3GB in about 30 minutes. Still way too slow, but not taking 72 hours and still hanging like it was earlier this week. Hope this works for you.

10.7.5 with an external TM disk that we plug in or not depending on whether we need the backup taken today.

michaelfromseal beach wrote:

Actually, I am sorry to say it did not fix the problem.

😢

Most of the time, when a problem like this is solved a thread like this just fades away. I was hoping that was the case given your report.

Apple does not read or care about what is posted here, as long as it conforms to the TOU. Irate users in contact with AppleCare will be more than sufficient motivation. The fact that several people reported Engineering is aware of the problem bodes well for a fix. Give it time.

Well, i'll be ticked if the ultimate solution is to upgrade to ML, as I have one or two apps that are incompatible