Problem creating new Vault on new HD
I am using AP 3.1.3 on a 17" MacBook Pro on Snow Leopard. I needed to get a new HD, as my current library is growing. I have 2x eSata drives connected by card in slot. I formatted the first drive, and copied the Library across. No problem, and I was happy to see afterwards that the previously fragmented contents were now contiguous. (Inspected with iDefrag, didn't touch them.) This is where the troubles started; I now have a new Library on a 1.5Tb drive that runs like a rocket. SO... formatted new big drive for Vault, created new Vault in AP, and off I went. I was pretty pleased to see that the copying was progressing (according to Activity monitor) at nearly 100Mb a second! After 30 hours, it ground to a halt, and although I could see some disk activity, it was obvious we weren't going to make it. I had a flash (not Adobe 🙂 ) of inspiration, and went to see Spotlight... DUH! It wasn't in the privacy setting, so activity was probably spotlight indexing. Force quit Aperture, (the Activity window is pathetic, doesn't tell you anything of value). Excluded the Vault from indexing, restarted everything, and off I went again. 100Mb/s transfer again, should be done in a few hours, certainly overnight. Got up this morning, and bu**er me, it's slowed to a crawl exactly as before. Aaaaarrrrggghhhhh!!!! 603Mb copied, 47Mb to go. SO, went to check Spotlight in the system Prefs, and sod me, the Vault has disappeared from the excluded panel!!! So; is spotlight indexing it all over again? (it's currently running at around 3Mb/s in the fast bits...)
It's a Vault, for insurance, I don't want it indexed! What the **** is going on?
This seems to be a fundamental problem, and if it weren't a Bank holiday here, I'd need my Mac to be earning it's keep. I am now approaching three days on this and nowhere near an answer. For a piece of allegedly professional software, I'm getting pretty miffed, to put it mildly. If I can't crack it in the next two days, I'm off to LightRoom.