Larry Nolan
Level 2 (191 points)
Apple Watch

Q: time machine slow in 10.7.5

Since updating to 10.7.5 using the Combo updater, Time Machine on my iMac seems much slower.  Anyone else seeing this behavior?

iMac, Mac OS X (10.7.5), iMac 21.5 in.; i5; iPad 32Gb iOS 5.

Posted on Sep 21, 2012 7:23 AM

by Larry Nolan,Solvedanswer
Larry Nolan Larry Nolan
Level 2 (191 points)
Apple Watch
A:

Well I installed the 10.7.5 supplement.  Here's my first backup (with Spotlight running) with Time Machine.  Noticed that the indexing took a little while and it wasn't as fast as usual.  After this first backup I duplicated a small JPEG file on the desktop and did another backup that went quickly.  So far so good.

 

 

10/4/12 4:37:07.796 PM com.apple.backupd: Starting standard backup

10/4/12 4:37:07.916 PM com.apple.backupd: Backing up to: /Volumes/Larry Time Machine/Backups.backupdb

10/4/12 4:37:09.199 PM com.apple.backupd: Event store UUIDs don't match for volume: Macintosh HD

10/4/12 4:37:09.343 PM com.apple.backupd: Deep event scan at path:/ reason:must scan subdirs|new event db|

10/4/12 4:42:29.548 PM com.apple.backupd: Finished scan

10/4/12 4:43:31.075 PM com.apple.backupd: 1.51 GB required (including padding), 21.26 GB available

10/4/12 4:43:31.231 PM com.apple.backupd: Waiting for index to be ready (101)

10/4/12 4:47:15.871 PM com.apple.backupd: Copied 15059 files (369.3 MB) from volume Macintosh HD.

10/4/12 4:47:17.977 PM com.apple.backupd: 1004.6 MB required (including padding), 20.89 GB available

10/4/12 4:47:28.248 PM com.apple.backupd: Copied 2117 files (104 KB) from volume Macintosh HD.

10/4/12 4:47:34.621 PM com.apple.backupd: Starting post-backup thinning

10/4/12 4:48:16.940 PM com.apple.backupd: Deleted /Volumes/Larry Time Machine/Backups.backupdb/Nolan iMac/2012-09-04-182017 (279.4 MB)

10/4/12 4:48:33.831 PM com.apple.backupd: Deleted /Volumes/Larry Time Machine/Backups.backupdb/Nolan iMac/2012-10-02-173549 (27.2 MB)

10/4/12 4:48:33.831 PM com.apple.backupd: Post-back up thinning complete: 2 expired backups removed

10/4/12 4:48:33.958 PM com.apple.backupd: Backup completed successfully.

10/4/12 4:49:03.708 PM com.apple.backupd: Starting standard backup

10/4/12 4:49:03.713 PM com.apple.backupd: Backing up to: /Volumes/Larry Time Machine/Backups.backupdb

10/4/12 4:49:04.521 PM com.apple.backupd: 1006.8 MB required (including padding), 21.19 GB available

10/4/12 4:49:09.709 PM com.apple.backupd: Copied 1102 files (1.5 MB) from volume Macintosh HD.

10/4/12 4:49:09.902 PM com.apple.backupd: 1005.0 MB required (including padding), 21.19 GB available

10/4/12 4:49:14.018 PM com.apple.backupd: Copied 955 files (8 KB) from volume Macintosh HD.

10/4/12 4:49:16.397 PM com.apple.backupd: Starting post-backup thinning

10/4/12 4:49:16.397 PM com.apple.backupd: No post-back up thinning needed: no expired backups exist

10/4/12 4:49:16.480 PM com.apple.backupd: Backup completed successfully.

Posted on Oct 4, 2012 2:53 PM

Close
Larry Nolan

Q: time machine slow in 10.7.5

  • All replies
  • Helpful answers

first Previous Page 7 of 43 last Next

  • by __NP,

    __NP __NP Sep 24, 2012 10:48 PM in response to michaelfromseal beach
    Level 1 (0 points)
    Sep 24, 2012 10:48 PM in response to michaelfromseal beach

    I tried upgrading to ML and it seems to have taken care of the issue so far. I did a completely new re-index once I had upgraded to 10.8.2 and now both Spotlight and Time Machine are behaving themselves.

     

    At first I was getting some weird diagnostic reports generating related to the Microsoft Office mdimportor but I haven't seen any recently.

  • by infinite vortex,

    infinite vortex infinite vortex Sep 25, 2012 12:48 AM in response to __NP
    Level 7 (21,405 points)
    Sep 25, 2012 12:48 AM in response to __NP

    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…

     

    spotlight.png

     

    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

  • by Eugenio MORASSI,

    Eugenio MORASSI Eugenio MORASSI Sep 25, 2012 3:05 AM in response to infinite vortex
    Level 1 (0 points)
    Sep 25, 2012 3:05 AM in response to 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

  • by oshilumbo,

    oshilumbo oshilumbo Sep 25, 2012 3:29 AM in response to Larry Nolan
    Level 1 (0 points)
    Sep 25, 2012 3:29 AM in response to Larry Nolan

    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.

  • by ppithermo,

    ppithermo ppithermo Sep 25, 2012 3:55 AM in response to oshilumbo
    Level 1 (0 points)
    Sep 25, 2012 3:55 AM in response to oshilumbo

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

  • by Nick_16,

    Nick_16 Nick_16 Sep 25, 2012 4:54 AM in response to Larry Nolan
    Level 1 (0 points)
    Sep 25, 2012 4:54 AM in response to Larry Nolan

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

  • by PieroF,

    PieroF PieroF Sep 25, 2012 4:58 AM in response to Larry Nolan
    Level 5 (4,283 points)
    Video
    Sep 25, 2012 4:58 AM in response to Larry Nolan

    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

  • by Danne217,

    Danne217 Danne217 Sep 25, 2012 5:22 AM in response to Larry Nolan
    Level 1 (0 points)
    Sep 25, 2012 5:22 AM in response to Larry Nolan

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

  • by klickman,

    klickman klickman Sep 25, 2012 6:19 AM in response to Danne217
    Level 1 (14 points)
    Sep 25, 2012 6:19 AM in response to Danne217

    10.8 will not resolve the problem!

  • by Danne217,

    Danne217 Danne217 Sep 25, 2012 6:32 AM in response to klickman
    Level 1 (0 points)
    Sep 25, 2012 6:32 AM in response to klickman

    Thanks for the heads up!

  • by andre.s,

    andre.s andre.s Sep 25, 2012 6:34 AM in response to andre.s
    Level 1 (0 points)
    Sep 25, 2012 6:34 AM in response to andre.s

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

     

    Result for 100MB ... 30 minutes

  • by Mahonske,

    Mahonske Mahonske Sep 25, 2012 6:39 AM in response to infinite vortex
    Level 1 (0 points)
    Sep 25, 2012 6:39 AM in response to infinite vortex

    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

  • by Doug Lockett,

    Doug Lockett Doug Lockett Sep 25, 2012 6:48 AM in response to infinite vortex
    Level 1 (0 points)
    Sep 25, 2012 6:48 AM in response to infinite vortex

    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…

     

    spotlight.png

     

    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

  • by andre.s,

    andre.s andre.s Sep 25, 2012 6:56 AM in response to Mahonske
    Level 1 (0 points)
    Sep 25, 2012 6:56 AM in response to Mahonske

    @ 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.

  • by andre.s,

    andre.s andre.s Sep 25, 2012 7:06 AM in response to andre.s
    Level 1 (0 points)
    Sep 25, 2012 7:06 AM in response to andre.s

    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"

first Previous Page 7 of 43 last Next