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

Similar Messages

  • 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't Hide Aperture During Vault Backup

    Running the latest Mac OS and Aperture on a Mac Pro with a ton of RAM. Whenever I run Aperture's vault backup (I backup onto another hard drive), Aperture is essentially locked up during the backup. I can't even hide the app in the background as I continue to use my Mac. I can use other apps in front of Aperture, but the desktop is always hidden by the Aperture window, and this makes it a lot more difficult to access apps and windows in the Finder, especially if Aperture is backing up for a long time.
    This has been true for all versions of Aperture that I've owned, if I remember, back to 1.0.
    Does anyone else have this problem? Is there some workaround?

    So it's not just me, eh?
    I didn't know spaces would help. Thanks, I'll give that a try.

  • 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 vault update problems

    I recently upgraded to Aperture 3. I have two problems with it:
    - The size of my library is somewhat north of 700 GB. The libary is stored on one external (Firewire 800) disk and so is the vault. I have worked today on some of my pictures and wanted to update the vault. When I do so on the general update vault icon the program goes on to calculate the disk space and then turns off. When I try to update by pressing the icon next to the specific vaults graphic it gives me a note that the disk space is not enough mentioning that a ridiculous amount of GBs are needed (numbered in the millions) and there is thus not enough space. Can anybody help?
    - The use of the keyboard shortcuts work at times and at other times they stop working at all. I have no clue what the trigger in each direction is. Any clues?

    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.03 when quitting gets stuck in "Updating information for preview

    Hi there,
    i notice that maybe 3 out of 10 times when i quit aperture, it hangs.
    There is a progress bar at the top saying "updating information for preview images" (translated, so the english original may be a bit different) but the bar wont move, the disc doesnt make any sounds and when i look in the actvity monitor it says aperture has around 35 threads and uses 1% of cpu power.
    i usually then force quite aperture after some time.
    if seems to occur more often after emptying the trash.
    any ideas?
    i get rather frustrated with force quittung becaus i get the feeling its no good for my library, however i run into problems repairing my library as explain elsewhere.
    alexander

    Alexander, have exactly the same problem, as do many others:
    http://discussions.apple.com/message.jspa?messageID=11628321#11628321
    Hopefully there will be an update soon to fix it.

  • Mountain Lion 10.8.2 reset during apps update (iPhoto 9.4, Aperture 3.4.1, Xcode)

    I'm experiencing a lot of troubles, after Mountain Lion automatic update.
    system during apps update such as iphoto 9.4, Aperture, etc, freeze, screen become white, then retart automatically.
    Even today during my new iphone 5 installation made the system reset by itself. Quiet unusual for a Mac, especially this new Retina display.
    My configuration,
    Mac Book Pro Retina Display 15" -  i7 2,6 - 16GB Ram, 768 Gb SSD
    Intel HD4000
    Nvidia GT M650
    Can anybody help me to get out of this big issue? FYI, I rein stalled Mountain Lion manually, downloading the file from Apple website.
    Thanks
    Steve8869

    Welcome to Apple Support Communities
    http://support.apple.com/kb/HT3964

  • Launched software update on MacBook v. 10.5.8 during restart, update stalled now nothing will launch-quits unexpectedly. Help!

    Launched software update on MacBook v. 10.5.8 during restart, update stalled now nothing will launch-quits unexpectedly. Help!

    As long as the report ends up with 'Permissions repair complete' then, as far as permissions go, you are fine. You can ignore the various statements in the report:
    Permissions you can ignore on 10.5 onwards:
    http://support.apple.com/kb/TS1448
    Some general advice on updating Leopard:
    It is worth noting that it is an extreme rarity for updates to cause upsets to your system, as they have all been extensively beta-tested, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
    So before you do anything else:
    If you can, make a full backup first to an external hard disk. Ideally you should always have a bootable clone of your system that enables you to revert to the previous pre-update state.
    Turn off sleep mode for both screen and hard disk.
    Disconnect all peripherals except your keyboard and mouse.
    1. Repair Permissions (in Disk Utility)
    2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
    At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
    3. Download the correct version of the COMBO update from the Apple download site.
    The Combo updater of Leopard 10.5.8 can be found here:
    http://support.apple.com/downloads/Mac_OS_X_10_5_8_Combo_Update
    If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
    Full details about the 10.5.8 update here: http://support.apple.com/kb/HT3606
    More information on using Software Updater here:
    http://support.apple.com/kb/TA24901?viewlocale=en_US
    Using the Combo updater ensures that all system files changed since the original 10.5.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.5.7 to 10.5.8. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
    Now proceed as follows:
    4. Close all applications and turn off energy saving and screensaver.
    5. Unplug all peripherals except your keyboard and mouse.
    6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
    7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
    8. Once your Mac is awake, repair permissions again, and you should be good to go!
    If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious! In fact a second restart can be recommended.
    9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them compliant with the latest version of your operating system. Give them a week or two while you regularly check their websites for updates.
    N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
    Lastly, Apple's own article on the subject of Software Update may also be useful reading:
    http://docs.info.apple.com/article.html?artnum=106695
    [b]If you are updating Safari (or just have):[/b]
    Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up.  If you have installed an OS update and Safari is crashing, the very [i]first[/i] thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
    So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari.
    Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party add-on.
    Additional tips on software installation here:
    http://docs.info.apple.com/article.html?artnum=106692
    To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for  problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
    Again, the advice is to remove all Input Managers from the following directories:
    /Library/InputManagers
    ~/Library/InputManagers
    especially prior to system updates (they can always be added back one-by-one later).
    Solutions for troubleshooting installation, startup, and login issues in Mac OS X v10.5
    http://support.apple.com/kb/TS1541?viewlocale=en_US

  • 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.

  • 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

  • Aperture 3.3.1 frequently "Updating Library" when I quit Aperture

    Since I've upgraded to Aperture 3.3 (now 3.3.1), Aperture frequently (almost 100%) spends time "Updating Library" when I quit Aperture.  This takes like 40 mins to do.  I've fixed permissions and repaired the library but no difference.
    Does anyone else have this problem?  I was hoping 3.3.1 would fix this problem but it doesn't.  Next plan would be to rebuild the library but that will take a long time!
    Jason

    Sadly, you are on the cutting edge of the deployment of Aperture 3.3.x (along with many other posters here).  The answer to your unasked questions -- "What is going on, and how can I fix it?" -- is "We don't know yet".  Since you have upgraded to 3.3.1, and have let Aperture more than once run through whatever it is doing when it says "Updating Library" and it continues to update the Library for 40 minutes every time you close the Library, I advise you to go ahead with rebuilding the database.  IME, this rarely takes longer than 10 hours, and can be run overnight.
    I have rebuilt Libraries many times and have never seen a Library damaged by the rebuild.  Nevertheless, you should have a complete and verified back-up before doing any maintenance on any Library.
    Let us know what you do, and what the result is.  Thanks.

  • ITunes Quit During iPod Update Now I Get An Error Message

    iTunes quit while i was updating my 1 gen iPod touch to the 2.2 firmware now I get an error message everytime i connect my iPod thay says.
    An iPod has been detected, but it could not be identified properly. Please disconnect and reconnect the iPod, then try again. AN unknown error occurred (2001).
    What do i do now? I tried everything and nothing worked can someone please help

    I would start by removing and reinstalling iTunes: http://support.apple.com/kb/HT1747
    Followed by a reset of the touch - hold down the Sleep/Wake key and the home button until the Apple logo appears (about 10 seconds). Try your update again. If you still have problems with the touch, you are going to have to reset it: http://support.apple.com/kb/HT1238 and try again.

  • 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

  • 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...

Maybe you are looking for