time machine slow in 10.7.5

I'm not sure if this is helpful to anyone or if it provides any long term fix, like a 2nd attempt at indexing something, but Spotlight performance seems to have been returned by doing the following…

1) Placing all drives into the Privacy of the Spotlight System Preference

2) Manually destroying the Spotlight index directory which is the .Spotlight-V100 directory at the top level of each drive in Terminal

3) Removing all drives from the Privacy of the Spotlight System Preference

Now, be aware I have not tried indexing anything substantial but an MBP with not much more than OS X and software installed. I use this system with network user accounts so there no user data on it other than a single, near empty, administrator account.

That said, upon a first clean re-index it's gotten to here in about 25-30 mins which seems about normal for this system and the mds/mdworker processes are running as I'd expect without stalling to < 0.5% CPU usage…

UPDATE : Just finished indexing. 😮

NB - I would NOT do this with Time Machine enabled in the Time Machine System Preference so I suggest disabling it first and then trying it… if you're going to try it.

Message was edited by: infinite vortex

Same here; after upgrading to 10.7.5 TM stopped working.

Doing what you're saying in this post DOES NOT solves, for me.

It seems that the 10.7.5 update destroys TM capabilities.

Please note that last backup I tried (1,3 GB) has NOT been completed OVERNIGHT.

Thank for you suggestions.

* * *

Please excuse my poor English 🙂

Apple Support told me they never heard of this problem and I should download the update again and re-install it.

Didn't solve the problem.

Very frustrating.

I did just that. Useless. The error is real. Apple fix it

all the morning to reinstall and set up 10.7 server with combo 10.7.4 downloaded directly from Apple.

240 gb trasferred to Time Machine (in other internal disc) in two hours! Wonderful!!

I've got the same problem just after updating to 10.7.5. I used the terminal command Larry Nolan suggested in this thread (sept.23 3.54 Italy time), and they worked (thanks Larry).

However this is not a solution, but a workaround... I still have to use those commands every time I need to backup!

Piero

I can confirm this issue. My mid 2010 13" MacBook Pro has tried to copy about 120 MB to the backup disc the last four nights resulting in me cancelling the update every time since it's taking forever... This is probably just another way of Apple telling us to buy 10.8 which will resolve the issue...........

10.8 will not resolve the problem!

Thanks for the heads up! 🙂

After a morning test, this "solution" doesn't work.

Result for 100MB ... 30 minutes 😟

How do you do step 2?

2) Manually destroying the Spotlight index directory which is the .Spotlight-V100 directory at the top level of each drive in Terminal

This didn't seem to work for me and I've tried it a few times. I had disabled time machine in the preferences,as per your suggestion, but I'm still getting spotlight hanging up at "Estimating Indexing Time".

What did you use at the terminal command line to delete the spotlight v-100 directory?

I have all hidden files/folders visible on my machine (which includes the spotlight v-100 directory), so I just trashed. Am I missing something by doing it that way?

When I remove the drives from the privacy list in the spotlight system preference (as per step 3) I can see that it is recreating the spotlight v-100 directories for each drive, so I know that it's attempting to recreate the index... but it's still hanging up.

Maybe I should just upgrade to ML.... grrr...

Thanks,

D

infinite vortex wrote:

I'm not sure if this is helpful to anyone or if it provides any long term fix, like a 2nd attempt at indexing something, but Spotlight performance seems to have been returned by doing the following…

1) Placing all drives into the Privacy of the Spotlight System Preference

2) Manually destroying the Spotlight index directory which is the .Spotlight-V100 directory at the top level of each drive in Terminal

3) Removing all drives from the Privacy of the Spotlight System Preference

Now, be aware I have not tried indexing anything substantial but an MBP with not much more than OS X and software installed. I use this system with network user accounts so there no user data on it other than a single, near empty, administrator account.

That said, upon a first clean re-index it's gotten to here in about 25-30 mins which seems about normal for this system and the mds/mdworker processes are running as I'd expect without stalling to < 0.5% CPU usage…

UPDATE : Just finished indexing. 😮

NB - I would NOT do this with Time Machine enabled in the Time Machine System Preference so I suggest disabling it first and then trying it… if you're going to try it.

Message was edited by: infinite vortex

@ Mahonske

How do you do step 2?

2) Manually destroying the Spotlight index directory which is the .Spotlight-V100directory at the top level of each drive in Terminal

If I do: ls -al /

I see the .Spotlight-V100 directory in the root of my Machintosh HD.

You can do this for you connected drives.

To remove a directory, run the 'rm' command like this: sudo rm -r .Spotlight-V100

Take care with the sudo rm -r command ... you can delete the whole content of a disk.

I re-read all messages of this discussion and if I well understand there are not true solutions/workaround ...

1) Do a downgrade to 10.7.4. My question is, in this case, do the downgrade by applying the combo 10.7.4 on the top of 10.7.5 or via a clean install? How can I do a TM backup? Maybe do this backup by cloning the HD?

2) Upgrade to the 10.8.2 ... but it seems that is not solved the issue ... could you confirm please?

3) Disable & restart Spotlight ... When do I the TM? Between stop and start spotlight or after the restart?

Could you help me to clarify my ideas please?

Thanks ... and sorry if my english is a little "strange" 😉

Nothing mentioned above works for me... Deleting the Spotlight-V100 directories neither. Apple! Wake Up! Has someone called or have contact about this issue with the technicians at Apple's?