Well I Rebuilt the database again and it seems to be working. Now Im in the middle of updating a Vault but its taking 5hrs where in the past if I did it after every job it took 20mins. I too fall in that category of impatience cheers.

I Think mine worked but I did have a crash this am in Aperture, strange. Usually before an upgrade a big Version change I move the Vaults to an external HD and make new Vaults after the upgrade. This time I didn’t so ….. well see.

Make new Vaults now and see if that is successful. If not then use disk Utilities for permissions repair and then rebuild your Library Database. see FAQ for details

I backed up my vault today after updating to 3.3. It took quite some time (a few hours) and at one point I thought Aperture was not responding but patience prevailed and the Vault backup completed OK.

Aperture seems to be fine now. But if you have room for another vault start a new one and then go to bed for the night. Move the old one later

Ok I just looked through my Smart Folders and found 3 images missing and 2 without copyrights. No telling if the 3.3 upgrade lost them or just rediscovered they were missing. Anyway Inspect what you expect in your Smart folders. Located, fixed and now doing the vault update again. BTW I have two Vaults but each on different HDs, that I update at the same time.

Ok Aperture crashed again since 3.3. I went through all three steps of repair and rebuild library again. Now doing the Vault Updating again. After the rebuild of the Lib I checked my favorite SmartFolders and another image lost all its exif and iptc info. Hopefully that is it and its now sound.

Ok been spending all day again but I think I got it. Started a new Vault on another HD and after 8 hours and 130 hangs (via Activity Monitor) I defraged (idefrag or Drive genius) the non osX HD. I forced quit the Vault operation to defrag and Safe boot and Rebuilt the database. So the vault was half way done before I forced it to quit and I just started it again on the same vault. one hour later and 2 hangs it finished. Still testing …

Joseph: why would it not be a BEST PRACTICE to kill any vault (and time machine or any other backup regimen) that predates aperture 3.3? Aperture 3.3 won’t read previous vaults will it? Or will it upgrade a vaults library(and time machine’s) should you need the vault or backup?

Hi Vidpix
I had two vaults from 3.2.2 and one upgraded quite nicely but the other failed. I have two of the same library cause I have an extra HD lying around and paranoid. I do think its better to archive the old vault and start with a new one but that takes a lot longer to generate. In my case I had to spend the extra time on one of the vaults. More importantly I should of Rebuilt the Lib database and then updated the vaults before upgrading to 3.3. Now I will remember for AP4

DBmoore: I infer from your response that if aperture 3.3 needs to use a legacy vault it will update the files? I also infer that if time machine needs to restore a legacy file–aperture updates that file? Or does running vault update just start a new database/ based on the new code in aperture3.3 ? If this latter scenario is the case–then it seems to me best to kill legacy vaults. I must be missing a step?

I don’t use TM on my Library or Vaults, old habit / work flow, no specific reason why. I think of the Vaults as a TM back up for the Library and thats why I have two of them on separate drives.
I think, and I am most often wrong, that once you have a new 3.3Vault (whether rebuilt on the old one or started new) you would not need the older vaults. I archive the older Vaults for 3 months to make sure the new upgrade and vaults are working and I don’t have to revert back to an older version of Aperture.

Aperture 3.3 does not need legacy vaults if you have new working ones. If TM needs to restore a legacy file …. UMmmmm….I guess you would get the image out of the vault and not worry about the metadata ……depends on how many you have to restore. Im not that familiar with TM and Aperture Im banking on the Vaults. Im sure others will be more helpful here. Are you in trouble now or just wondering?

DB: Not in trouble. Just trying to think it through so I don’t get into trouble.

Since upgrading to Aperture 3 I have had enormous strife with my Mac Pro (Mid 2010). It does not matter where I build the values - Internal or external drives - they all refuse to update and the software crashes. I have repaired the library many times, without effect. What is the accepted wisdom right now? Is there no fix for this wretched software? It seems Apple could not care less!
Any advice, please?

Boy thats an old thread. Best to create a new thread… but let me give it a go. After an upgrade you probably will have better luck just making a brand new vault for the new version of AP. If that is a problem some people just copy the lib to another HD using Superduper or Copy Cloner. Cheers

Haim, I’m in the same boat. No matter what I do I cannot create a new vault or update an old vault. I’ve tried building on 2 separate EHDs and my internal drive. I’ve repaired the library numerous times as well. If you figure this out please let me know, I am beyond frustrated. Oh, I’m on a late 2010 MacBook Pro as well.

I just installed the update for aperture less than 10 minutes ago. I am currently copying my ap lib to yet another EHD but when it finishes copying I am going to try to make a vault again and hope this software update fixes the problem

Haim and Katy

YOu could temporarily separate you Library into smaller Libraries and back those up via vault. If you get to a smaller lib/vault that wont update in 24 hours then there is an issue with that perticular lib. Put the good lib back together and Vault it. or just clone the lib via SuperDuper or CopyCloner and forget the vault method.