Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Time Machine seems to stop backing up

I've spent the better part of a day attempting to get TM to perform either an inremental or full backup but have been unsuccessful so far. I'm a relative newbie with MACs so please bear with me.


My system is running 10.7.3 and has 8GB RAM with 500GB drive.


I have been using TM since getting my MacBook Pro last summer without issue to a Seagate GoFlex Desk 2TB drive via FireWire. I haven't performed a backup since January and decided it was time. I've not been able to get TM to perform an incermental since last night. I even let it run over night.


Today I attached another external drive, same general type but using USB 2.0 and set TM for a new Backup set. Now when I try to perform a backup the status gets to "14.39GB of 144.91GB" and then it seems to stall. I've let it set for several hours only to see the "About - x hours" continually climb up to over 12 hours but the amount of data copied never moves.


I've installed the widget so that I can see the log information and the most information I see is "waiting for index to be ready (101)". I have verified and repaired my internal disk and verified and repaired the permissions. I've also deleted the progress file on the TM drive after canceling any backup.


I have tried many of the steps for the site "http://Pondini.org/TM/Troubleshooting.html" but I've not been sccessful. I'm stuck with what to do next to try and solve this, anyone have other ideas?


Thanks,

MacBook Pro, Mac OS X (10.7.3)

Posted on Mar 11, 2012 9:29 AM

Reply
13 replies

Mar 11, 2012 4:29 PM in response to ajmonroe

ajmonroe wrote:

. . .

I've not been able to get TM to perform an incermental since last night. I even let it run over night.

What happens? What does the log show?



Today I attached another external drive, same general type but using USB 2.0 and set TM for a new Backup set. Now when I try to perform a backup the status gets to "14.39GB of 144.91GB" and then it seems to stall. I've let it set for several hours only to see the "About - x hours" continually climb up to over 12 hours but the amount of data copied never moves.

Does the new drive have the GUID Partition Map Scheme? If not, reformat it.


I've installed the widget so that I can see the log information and the most information I see is "waiting for index to be ready (101)".

That's on the new drive, right? Do you see a few of those messages, or a bunch?



I've also deleted the progress file on the TM drive after canceling any backup.

That's usually not required. Time Machine should "recover" it on the next backup.


If you've having the same problem on both drives, something in your installation of OSX may be damaged. You might want to install the 10.7.3 "combo" update (and perhaps the "Supplemental Update"), perInstalling the ''combo'' update and/or Reinstalling OSX.

Mar 11, 2012 4:44 PM in response to Pondini

TM didn't give me any error other than the "waiting for index to be ready (101) 3 or for times.


I set the new drive as MAC OS (Journaled).




If you've having the same problem on both drives, something in your installation of OSX may be damaged. You might want to install the 10.7.3 "combo" update (and perhaps the "Supplemental Update"), perInstalling the ''combo'' update and/or Reinstalling OSX.

I did some digging and found where the system logs are and how to read them. From what I can see it seems there may be an issue with the indexing. Per your comment above, is it okay to run the "combo" update since I'm already at 10.7.3?


Thanks,

Mar 11, 2012 4:48 PM in response to ajmonroe

ajmonroe wrote:

. . .

I set the new drive as MAC OS (Journaled).

That's the Format. You need to be sure it has the GUID Partition Map Scheme. Click the main line for the drive in Disk Utility's sidebar, and it will be shown at the lower right.


I did some digging and found where the system logs are and how to read them. From what I can see it seems there may be an issue with the indexing. Per your comment above, is it okay to run the "combo" update since I'm already at 10.7.3?

Yes, that's a common fix for OSX problems. It contains all the changes from 10.7.1, 10.7.2, and 10.7.3, so installing it will fix anything that's been damaged in any of those updates.

May 26, 2012 3:47 PM in response to kbarrans

If "ajmonroe" can't tell you … I can! Because I just spent a couple of hours banging my head against the wall wondering why my laptop's Time Machine backup would hang at exactly the same spot each time -- even after I erased my Time Capsule's drive and started over!


I remembered reading elsewhere on the web that Time Machine backups that stall or hang may be affected by some kind of Spotlight issue. I then thought to go to the CONSOLE application in the Utilities folder and see if the logs could tell me anything. I saw dozens of 'em, all created right at the sane time I had come in and noticed the Time Machine backup had stalled out again. And they were all for the same cause: a plugin, installed by Finale 2012, called "finale.mdimporter" that is in the main LIBRARY's "Spotlight" folder. I trashed that plugin, restarted and … bada-bing! My Time Machine backups are working again.


I don't know if this was always the case with Finale 2012, or was introduced with the new Finale 2012a maintenance release which I installed on both my desktop and laptop Macs a few days ago… right after that my Time Machine backups stopped working, so I suspect it's this update that is the cause. I will attempt to let the company know, although I'm not all that confident they listen to anyone.


PONDINI … your excellent Time Capsule and Time Machine pages were what first turned me onto the idea that Spotlight indexing could be a root cause. You may want to make note of this.


Ken Gruberman, The Tech Daddyâ„¢ / Quill Music

May 26, 2012 4:01 PM in response to Tech Daddy

Tech Daddy wrote:

. . .

PONDINI … your excellent Time Capsule and Time Machine pages were what first turned me onto the idea that Spotlight indexing could be a root cause. You may want to make note of this.

Yes, I've noted that, thanks!


Have you (or others) notified the makers of that app? If not, by all means do so, and include a link to this thread.


How common an app is Finale? I've already got a rather long list of things at the beginning of #D2 in Time Machine - Troubleshooting, so if this is fairly rare, and/or may be fixed soon by the maker, I'm a bit reluctant to add it there.

May 26, 2012 4:14 PM in response to Pondini

I just notified MakeMusic.com, the company behind Finale, about the issue, but they are notorious for not responding. I also registered for their Help Forum, but it takes a bit before someone there OK's me; then I'll post on the Finale Forums as well.


As to how 'common' Finale is? That's a relative question. I would say that anyone who has ever worked with music and computers in ANY way knows about it, as it's the music notation software that's been around the longest that's still actively developed. Although I personally espouse Sibelius, the better, faster, easier to use music notation software; I have Finale because I often receive files made with it that I then convert to Sibelius. Finale and Sibelius are the two top-dogs when it comes to computer-based music notation.


The software is well-known in music circles; educators, hobbyists, church people, studio musicians, arrangers, orchestrators and composers, etc., who all use it. Are there as many people who use music notation and orchestration software as use Microsoft Word? In a word, no. But there are enough that it would warrant a mention IMHO.

May 26, 2012 5:41 PM in response to Tech Daddy

I'm a bit reluctant to tell folks to delete an mdimporter.


I'm not real familiar with Spotlight's "works," but wonder what it will do when it can't find it. Or are you putting a previous one there?


Even if Spotlight doesn't object, wouldn't it mean the files either aren't indexed, or aren't indexed properly? Isn't that a problem?


Do you have to delete the importer? Would merely excluding it from being backed-up work?

May 27, 2012 8:50 AM in response to Pondini

Just found this on the MakeMusic forums; turns out a couple other people have encountered the same problem:


http://forum.makemusic.com/default.aspx?f=6&m=352764


The plug-in is a Spotlight "importer", which adds metadata from Finale to Spotlight's indexing. For some reason, it doesn't seem to work well in Lion and causes the crashes and load that you are seeing. I'm not sure if it is unique to 2012's mdimporter, or whether any version on Lion will cause the issue. The solution is to remove the file Finale.mdimporter in /Library/Spotlight.


It's a shame, as when it works, it provides info to Spotlight such as Title, key sig, time sig, instruments, fonts used, and much more. So you could search Spotlight for files in D major that use a trumpet. Or Adagios that use Times. Or Soprano pieces more than 50 pages long.

Time Machine seems to stop backing up

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.