Time Machine and Logos indexer DO NOT like each other!

1) Logos starts indexing some small download (like the Lexham update the other day).

2) Time Machine has the bad taste of finding this an excellent time for the hourly back-up.

3) Done separately these processes would have taken a couple of minutes each. Done simultaneously they take something like 2 hours! During which time the computer is, of course, not all that responsive.

This is slightly annoying...

I can't say with absolute certainty that it happens every time, but it has certainly happened enough times for me to believe it happens every time. I'll try to remember to manually run Time Machine just before indexing in the future, until this is fixed, but of course I'll forget more often than not...

I also just saw another post mentioning Time Capsule as a probable cause for an increased number of errors, so there might be something bigger going on as well: http://community.logos.com/forums/p/26776/197953.aspx#197953.

Find more posts tagged with

Comments

Alan Macgregor

I have noticed this also, though my indexing never seems to last as long.

My guess, FWIW, is that something in the OS backup system is triggered when a new app installation/update is initiated.

If that is the case (and I could be way off beam here) then I reckon that pausing the indexing until the Time Machine update is completed, which doesn't take long. After that restart the indexing which, as you say is done in a fairly short time these days.

fgh

I should probably add -- and I just checked this -- that my Logos Library Index is excluded from being backed-up. So there shouldn't be a problem because Time Machine is trying to back up an index that's changing every split second.

Though, coming to think of it, my Bible Index is not excluded, and Lexham is most definitely a Bible! Did I just figure this one out by myself? If that is so, I'm pretty impressed with myself! I'll exclude the Bible Index as well, and we'll see.

Alan

I don't think there is any triggering; just the ordinary hourly back-up. When I said that I believe it happens every time, I just meant that I believe the excessive indexing/back-up times happen every time Time Machine happens to start while indexing is already going on.

EDIT: Though if my guess above is correct, then it's obviously only happened with Bibles, and not with other resources, and I just haven't noticed the difference. Or Time Machine has never happened to start during any other resource indexing, and I haven't gotten the chance to notice the difference.

Jack Caviness

I don't think there is any triggering; just the ordinary hourly back-up. When I said that I believe it happens every time, I just meant that I believe the excessive indexing/back-up times happen every time Time Machine happens to start while indexing is already going on.

I have never noticed anything like this happening on my system, but I will try to watch in the future to see it it does happen. If it does, I will report here and submit logs.

fgh

have never noticed anything like this happening on my system

Do you have the Library and Bible Indexes excluded from the back-up or not?