Vault Update

It seems that with Aperture 2, the vault does not need updating after making adjustments to images.
The update progress indicator remains black. If I remember correctly, with Aperture 1.5.6, the update progress indicator would turn yellow after making an adjustment to an image. Am I correct in my recollection? If so, how is 2.0 updating adjustments to the Vault?

I, too, have the same issue.
In aperture, making adjustments to a RAW file, or even a JPG file, in the adjustments section no longer yields a yellow vault icon indicating the master image has been altered.
However, if you crop, rotate, straighten, stamp etc, the yellow vault icon changes from grey to let you know the master files have been altered.
I called Apple tech support, and they recreated the issue.
They mentioned they will be speaking with their Aperture team to correct this in future updates, but as of now, there is no work around.

Similar Messages

  • How do I find the date of my last vault update?

    How do I find the date of my last vault update? All but one picture in a folder is missing from my library. I want to go back in Time Machine to the date/time of my last update to restore the lost images.

    Thanks, Frank. I was trying to make it too complicated, wasn't I

  • Aperture 3 Vault - Updating Vault issue

    I've upgraded to Aperture 3.
    I created a new Vault.
    I started a backup to the new vault 14 hours ago and it's still chugging away with the progress bar at about the 50% mark with a status of "Updating Vault". It hasn't made any progress since it stopped copying the masters about 2 hours ago.
    My library is around 1.5TB and 175K files.
    This is the third time I have tried backing up to a new vault and it always hangs at this point. I'm currently using Superduper to make a copy of my library so I have a current backup of some kind.
    Is anyone else experiencing this?

    You guys aren't backing up these vaults to an external Western Digital hard drive are you? If so, the problem could be that the drives are formatted in fat-32. Aperture 3 doesn't support fat-32 drives. Aperture 2 didn't support them either but was, apparently, more tolerant about them. Aperture 3 flat out doesn't work with them.
    Any external drives used with Aperture 3 MUST be formatted in Mac extended format.
    FWIW, I updated the vault on my Mac Pro for the first time (since installing Aperture 3) this morning. It completed without issues and took the normal amount of time for a brand new vault creation.
    BTW, I choose to leave my master images in their current location and reference them instead of copying them to my Aperture Library. I believe a vault update of an Aperture Library that is managed (all masters copied to the library) instead of referenced (left in their original location) will take longer and make for a much larger vault backup.
    Mark

  • Can I stop/pause a vault update?

    Okay, I've used vaults for a while but I recently moved my library around and ended up recreating my vault. I think my library is around 250GB and it is taking FOREVER to update. I have already had to force quit Aperture a couple of times when it couldn't finish the vault update overnight, but this time I left it running on my iMac for 24 hours (so far) and it is still not complete. I just cannot wait any longer, I need to use the machine. Does anyone know ift there is a way to stop/pause the vault update and return at a later time? Obviously I can force quit Aperture, but I can't imagine force quitting in the middle results in a very reliable Vault. So, if there's any advice here I would really appreciate it. I mean, time machine can pause in the middle as can many backup apps, I just don't know if I can use something that requires over a day of continuous use to just backup my files!
    Along that same line, does anyone have any opinions on using a different backup app like Carbon Copy Cloner for my Aperture library? I've used TM in the past with poor results (it was very hard to get back the data I needed to recover). Any suggestions would be greatly appreciated!

    What Doug said.
    Note that Masters need only be backed up once (but to multiple backup locations) and that backup should happen immediately after copying to the hard drive from the camera card, before involving Aperture or any other images management app.
    Time Machine is an ongoing regular-routine backup process. Image originals instead need irregularly timed backup, once.
    IMO referenced Masters make far more sense than building huge managed-Masters Libraries.
    • Hard disk speed. Drives slow as they fill so making a drive more full (which managed Masters always does) will slow down drive operation.
    • Database size. Larger databases are by definition more prone to "issues" than smaller databases are.
    • Vaults. Larger Library means larger Vaults, and Vaults are an incremental repetitive backup process, so again larger Vaults are by definition more prone to "issues" than smaller Vaults are. One-time backup of Referenced Masters (each file small, unlike a huge managed-Masters DB) is neither incremental nor ongoing; which is by definition a more stable process.
    Managed-Masters Libraries can work, but they cannot avoid the basic database physics. I recommend putting the Library on the internal drive and keeping Masters on the external drive by reference.
    HTH
    -Allen Wicks

  • Aperture 2.1.2 vault update error

    ever since i have updated to this most recent release i can no longer update my vaults /___sbsstatic___/migration-images/migration-img-not-avail.png i have reformatted my drives just to make sure they have not been corrupted. i was able to get 1 clean vault update but that is it. just as some other aperture users experienced i too am getting on the splash screen, when A. is first launched a notice i have not yet backed up some files. well dah how can i if i get errors upon errors
    i have searched through this forum and specific topic and have not found an answer yet. so perhaps an Aperture support person could take some time out of their busy day and help us all out in this most vexing and annoying matter.
    thanks

    Ha ha you are also as much a support person as any of us.
    I posted it originally hslfway down page 2 of.
     http://supportforums.blackberry.com/t5/BlackBerry-PlayBook/playbook-os-2-1-0-840/td-p/1888743/page/2

  • Does aperture vault update just add new photos and information?

    I am wondering if the Vault function when updated will just add the new photo(s) and new adjustments or replace the entire vault. I have already copied the entire library as a back-up on a different external. Was planning on just manually updating the files but wanted to try out the Vault. The information is unclear that it only updates NEW photos and info while keeping the vault and just adding.... Any answers would be great. Thanks...

    Seattle,
    I think I understand your question, but I got a little fuzzy after reading this:
    The information is unclear that it only updates NEW photos and info while keeping the vault and just adding....
    Anyway, when you perform the "Update Vault" function, Aperture does replace the vault.  It updates the vault such that it reflects changes to your library since the last time that vault was updated.  With a large library, but only a few changes, the vault update is pretty quick.
    nathan

  • Vault Updating VERY Slowly in 3.1 Upgrade

    I have two questions.
    1. First vault update after a successful 3.1 upgrade is progressing VERY slowly. Database is about 70 gb and library is completely referenced. Vault update got through the upgrade process relatively quickly, and then proceeded to write the file at a normal pace. (about an hour or so). But, it got to about 70 gb, and has slowed down to a crawl. It has been churning for nearly 24 hours now, with still no signs of finishing.
    2. With a totally referenced library, backed up regularly via Time Machine to a RAID 5 array, with a secondary offsite backup done automatically to a backup service, is there REALLY any need for me to have a vault in the first place? Isn't it just an unnecessary redundancy?

    I would try to restart your Mac. 24 hours is way to long for a 70gb library.
    If Aperture won't quit for the restart, then you will have to Force Quit.
    Relaunch Aperture, after the restart, then update the Vault again. It should be fine the second time. If you want to be sure it's okay, make a new empty library, then Restore the updated Vault to it.
    I like Vaults, because with databases, it's a good idea to let the programmers handle the data integrity.
    Regarding the backup strategy :
    One backup is not enough, but two the same is slightly redundant. My policy is to have one Vault active and a second one off-site. On top of this I have an Archive of job-folders containing tiffs/raws/MFDB-Galleries/other stuff relevant to commissions/ and a mirror of this off-site.
    The off-site bit adds the not inconsiderable protection from fire, flood, theft, children, mother-in-laws and any other natural disasters.

  • Vault Update problems solved!

    Sorry if this has been posted elsewhere, but I have just discovered a solution to one of my long running Aperture problems and must share in case it helps someone else out! I must say that that I am NOT technically good with computers (which is why I LOVE Macs), but I have found the odd bit of really helpful advice here and hope someone, who is like me, may find this useful:
    Problem: Whenever I would run an update on my Aperture Vault (to a dedicated separate HD), I would ALWAYS get some error messages, every time. At first I did not worry about these thinking, that as long as most of the images have backed up, that would do, as I also backup to DVDs. But then I read that if you ever tried to restore, Aperture would refuse to do so on the grounds that one or more of the files has an error. I consider this a MAJOR fault with the Aperture software, and for some users, renders the vault concept useless (although I am sure that not everyone suffers from this). I would also always be told, on starting Aperture, that several projects and images were not stored in a vault, even when most of the update seemed to work.
    Solution: I have shot a lot of weddings recently and have been adjusting parts of my workflow. I have found out that, if you DELETE all of your rejected files (as it happens, I back them up on DVD, then delete them), then, empty your trash, THEN run the vault update, it seems to work every-time, without any faults. After a year of errors my vault finally seems to be working as it should!.
    Hope this helps someone.
    Paul

    Glad to help, As it was getting frustrating, goes to show newer is not always better, Keep an xp computer handy forever

  • Vault update with AP3 corrupts database for Library

    I have upgraded happily to AP3 (great new feature set) and was updating my vault when everything hung...force quit AP3 and reboot. Now when open AP3 I get a message:
    There was an error opening the database for the library “~/Pictures/Aperture Library.aplibrary”.
    With - only the option to QUIT NOW...
    I suspect I will have to go to time machine and resurrect everything...whatta pain...seems like AP3 will have a "not soon enough" update fix...
    Any suggestions?

    I did notice another thread which ultimately suggested others with a similar issue had it solved with an update - https://discussions.apple.com/message/11200923#11200923
    I am rinning Lion and Aperture, both fully updated. 2.66ghz Core 2 Duo MBP...

  • How does Vault Update - all or only altered data?

    With a vault already established, how does the update vault process works? In other words, let say I modified or created 10 image versions (of the 3,000 plus stored in Aperture). If I update the valut (on a external HD), are all pictures overwritten or just the new data that's changed?

    Hi Jim,
    The vault functionality is basically a sync functions. After updating a vault, the vault will be a copy of you Aperture Lib. This means that images that you have deleted from you lib will be deleted from you vault. Notice that the images are not gone, but copied to a folder called deleted images.
    Best regards - Per.

  • Aperture 3 vault update stops.

    So I reformatted my external HDD to OSX Extended Journaled so that Aperture 3's vault will work with it.
    When creating the vault, everything is fine until it's about 50%, and then it just stops. No progress is made for about an hour. Aperture isn't hung, but I have to force quit it. When I look at the Disk Activity tab in the Activity monitor, it's idling, and not pegged to the maximum of ~17mb/s read/write that it does when it's updating the vault.
    I've deleted the vault and started over twice, but the same thing happens each time.
    All software is up to date.
    Aperture 3
    10.6.4

    It is possible that there is an issue somewhere in your library and that it is struggling to write something to the vault. Perhaps try the steps listed on the Aperture 3: Troubleshooting Basics page.
    http://support.apple.com/kb/HT3805
    Tony

  • Aperture 3: 17179869183.16 GB required for vault update?

    I'm getting the following error when trying to update a vault that I've just created:
    "Not Enough Disk Space
    The vault “ApertureVault” does not have enough space to hold your library.
    17179869183.16 GB is needed, but only 68.86 GB is available."
    My library is 76gb, and my vault is 76gb. I've tried to make a single change to a version of an image and update my vault, and I get this message. I've completely deleted my vault, created a brand new vault, made a single change to a version and tried to update and this is the message I get each time. I've tried this twice so far.
    It's obviously a miscalculation, but is anyone else experiencing this?
    To recap: I've updated my library to Aperture 3 from Aperture 2, and everything seems to be working fine. I created a vault (it took about an hour), and I get the green arrows and green space indication (meaning everything is OK). I attempt to update my vault without any changes and it tells me there's nothing to update. I make a single change to a version (not even a master), and then try to update (I get the yellow arrows now, indicating a change to a version) and 17179869183.16 GB is needed for the update.
    My backup drive where my vault is located is formatted Mac OS Extended (journaled).
    Help!!

    Kevin J. Doyle wrote:
    You will be much better off building a new V3 vault on a freshly formatted dedicated volume.
    It goes much faster than conversion as it is a much less complex operation, and since it is being created in entirety from scratch on an empty disk, will not be subject to the unavoidable fragmentation and other issues in the conversion of large, mature files.
    Always best to have your main backup in fresh shape, we do this fresh volume/new vault on a monthly basis as part of our maintenance routines. Does not take that long, and is worth the piece of mind.
    Disk are cheap, problems restoring a backup is an expensive nightmare.
    Sincerely,
    K.J. Doyle
    I'm seeing this bug while doing exactly what you suggest -- using a freshly formatted dedicated volume with a brand new Aperture 3 vault. I didn't even attempt to upgrade my vault, as it just seemed easier to create a brand new one.

  • How does a corrupted file affect the vault update?

    If I would have updated the vault after the files got corrupted, wouldn't the corruption get updated as well? Wouldn't that defeat the purpose?

    I believe it's meant to only copy files that it knows have changed.
    I.e. old masters wouldn't get re-copied, but version updates, metadata changes, new imported masters would.
    Of course, many people here reported having a lot of problems with the Vault mechanism in version 1, but others seem to have no problem at all (suggesting a subtle system configuration difference.)

  • Should Vault Update Take So Long

    MacBook Pro, Western Digital 750 GB Firewire Drive (brand new with 700gb available)
    I recently started using Aperture instead of iPhoto and brought over all my old pictures and several camera uploads worth of new photos. I have about 6000 masters now. I created a vault on the external drive and expected the initial copy to take a while and that was fine. The vault takes about 19 gb on the hard drive.
    I think I added a few new masters, then edited ONE version, and the vault status was yellow. Then I decided I would update the vault and clicked the yellow icon. Aperture asked me to confirm updating the vault, then I think it took over half an hour (I stopped watching) to "compare" the vault and update.
    That seems like a lot of time and waiting when all I did was edit one version and maybe add a few masters. I would think backups would be incremental and pretty quick if you hadn't changed many things.
    Am I missing something here? Thanks!

    Maybe:
    iOS: Troubleshooting backup issues in iTunes

  • Quitting Aperture During Vault Update

    Hello,
    I am using Aperture 3 in OS 10.6.8.  The library has about 70k photos (managed) on an external FireWire drive.  There are 3 vaults, two on external USB 2 drives and one on our iMac 27".  I usually backup the vaults one at a time since the USBs are so slow.  But this time I did them all at once and Aperture has been working for about 72 hours.  The progress bar is about an inch from the end and not progressing but is "rippling" normally.  The two external vault drives cycle on and off on a regular basis.  Activity Monitor indicates Aperture is functioning.  My problem is that I am going to have to disconnect the library drive in the next few days.  If the update is not finished then is it OK to use the Terminal command recommended by leonieDF in the Aperture User Tips ("If Aperture is unresponsive, how to avoid force quitting?")  to quit Aperture?  I assume I would have to recreate the vaults (on FW drives this time!) but I am concerned about possible effects on the library.  Any thoughts or suggestions on this?  Many thanks!
    Mike

    I would just go ahead and delete the  vaults in Finder with Aperture CLOSED. Then start Aperture and remove the vaults in Aperture.
    When a disk that is being used gets full it is hard to predict what behavior you will see and it might be different each time it happens.  So it is possible that the symptoms you had might have been caused by running out of disk space, really no way to say for certain. What you can say is that running out of or low of disk space is a condition you really want to avoid.
    The vault like the library is really a folder containing lots of folders and files so deleting it is not as simple a task as deleting a single file. However when I go to remove a vault in Aperture I get the following dialog
    Which shows both Remove and Remove and Delete options. If I select just Remove the vault is removed from Aperture but remains on the disk. Did you not see the same thing?
    Anyway given all you've been through you're doing pretty good. You have your library intact and a backup of it. I'd just go ahead and delete the vaults make sure you have enough room on the disk and then create new vaults. You should be good to go after that,
    good luck
    regards

Maybe you are looking for