A couple of Questions if someone could clue me in. I going to Tiger and am deeply concerned with this indexing with the problems I've had in the Past with Apple/indexing. (some of you may remember)
First some background OSX Server 10.3.7, Clients are OS 9 MMgr, and 10.3.7 Network Homes.
My plan was this All OS 9 Client are getting Mini's 10.4.2 Network Homes first(Homes should just link up but we will see some early tests seem fine).
10.3.7 Client to 10.3.9 till i get my Radmind & base 10.4.2 image for them setup.
Then Server to 10.3.9 Followed by 10.4.2 ASAP. (If anyone has input on this rollout especially problems please post them even if they are off-topic)
To the Topic at hand:
1. Will mds force an index of the Mount Volume?
2. Will each new Tiger Unit index the 10.3.7-9 Server Volumes as mounted and if they don't finish what happens?
3. What kind of Network overhead are we talking about here if indexing happens on the Client level?
4. How big are these indexes? And Mounted Volume indexes local or on Mounted?
5. Network overhead on a Mounted Volume Spot-Search?
Ok you see where I'm headed with this So feel free to point out any problem you have had with this Spotlight. This had better not be another Sherlock set of problems with indexes on Servers.