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

Similar Messages

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

Aperture vault with no mother library - how do i update it?

hello. i had an aperture library i created for a project. when i was done with the project i created an aperture vault on an external drive. but stupidly i deleted the actual library that created the vault.
now i have a 50g vault on a drive and i need to get back into the library.
when i try and open the vault, it says the vault was created with an older version of aperture and it needs to be updated. but i can't update it. i can't figure out how to even get aperture to recognize the vault at all... what to do?

Simple, effective answer: Yes, make copies of your Libraries as back-ups and don't use the Vault feature.
Vaults are no more than a back-up created from within Aperture. (I suspect Apple added this feature on the assumption that users of Aperture did not regularly back up their data.) They can be problematic (they can also be problem-free). If you are comfortable with Finder or with a program such as SuperDuper or CCC, use it and don't bother with Vaults. (That's what I do, and that's what other top posters here do as well.)
As far as data back-up goes, I recommend that all users maintain at all time three copies of their data. A working copy, a copy of the working copy that gets regularly updated (no less than once a day, unless the data is unchanged), and another copy of the working copy that is kept off-site. Never have all three copies in the same physical location (don't bring your off-site copy on-site. Take your on-site copy off-site, and then bring the off-site copy on-site, effectively swapping them while never having all three copies in the same location).
As for making on Library for each project ... it is generally not recommended. One of the great empowerments of Aperture is that it functions as an index of all the work it contains. I have _every photo I've ever taken_ in my personal Library. I can search my entire oevre. Your needs may be different -- and may be different enough that making one Library for each project you do is sensible -- but using separate Libraries takes the power of this global indexing away. (Fwiw, the reasons I can think of having separate Libraries: image security, image quarantine, multiple photographers, and Libraries of images where the photographer is not important.)
HTH,
--Kirby.
(Sent from my magic glass.)

Updating Aperture vault will not complete, Aperture quits unexpectedly.

I have a continuing and recurring problem updating Aperture vault after the current Aperture update. The problem also occured after the last update.
Updating the vault does not complete and Aperture quits unexpectedly. This frequently leads to repair to the Aperture library being required. The only solution i have found is to create a new vault. Time consuming and a frustrating waste. I have reloaded Aperture and made updates. This has not solved the problem. I have checked permissions. Nothing wrong there.
My vault and Aperture library are on seperate external drives.

i am experiencing the very same problem updating my vault. Have tried about a half dozen times, creating new vaults (some work some dont) and updating existing vaults (never works). My managed library is 418GB on an external raid array. I have previously created a vault successfully on an external La Cie drive, but then the update failed. After repeated attempts I can not create a new one without Aperture crashing -- which leads to a multi hour repair session. Very very frustraing.
Can someone from Apple comment on whether this is a known bug? What is the work around? Smaller libraries?

Aperture vault is freezing at 50% when updating!

I really need help on this! My aperture vault only seems to freeze and the progress bar is stuck at about 50%. I have to force quit aperture when this happens. I tried to make a new vault on a noter external disk. It is no help. I have a very powerful iMac. i7 SSD only one year old. Aperture version 3.3. The external disk is formated Mac OS Extended (journalført - norwegian Lion 10.7.4).
This is bothering me very!!!!
Someone!?

Hi,
If you have followed all the methods mentioned in "Aperture 3: Troubleshooting Basics" http://support.apple.com/kb/HT3805?viewlocale=en_US&locale=en_US (repair and rebuild etc.) then I would advice to wait and let it work longer. It may seem to get stuck but if you wait (not 5 minutes but 5 or 20 hours) it may go through.
I have already had years issue that taking Vault backup takes tens of hours. I have tried all tricks mentioned in this forum (if you search you should find 20-30 threads about Vault being slow, freezing etc.). Everybody here knows better and says that it should not take that long and will advice you to do this and that, but if you look at those 20-30 threads not even half have resolution for the person who had the issue.
I'm backing up the library instead, from SSD to HD it takes 15 minutes with CCC (block copy including verify), and faster from SSD to SSD. Here is thread I opened to ask if this is OK:
https://discussions.apple.com/message/18877353#18877353
Best Regards,
Samuli

Backup Storage - Aperture Vault versus Time Machine versus daily SuperDuper

What value does dumping the Aperture library to an Aperture Vault give in addition to running Time Machine to one drive and a daily SuperDuper copy to a second drive with irregular SuperDuper copies to an external drive that can be removed from the machine room.

SImon,
Vault and Time Machine address different needs. Probably you will want to have both.
The advantage of Time Machine: incremental backups of previous versions, very compact storage. And you can integrate it into your regular backup of the whole system and include the regular masters as well. But the disadvantage: Time Machine decides for you, what will be deleted, if the backup drives get full. You do not have control over what will be saved and what not from the previous versions.
The advantage of vaults: You can make full backups of your library for well defined moments in time - snapshots of important states. I'd create a vault, whenever I make a major upgrade of the system at least.
Is there anyway of cancelling a stuck Vault update other than the sledgehammer approach of Force Quit?
If the graphical user interface is unresponsive, like when updating a vault, you can use the Terminal to send the "termination signal" to Aperture: Sometimes this will succeed, even if the "Quit" button does not work:
Look for the Process ID of Aperture in the Activity Monitor (launch Applications > Utilities > Activity Monitor" and click the CPU heading. This will bring Aperture close to the top of the list. Make a note of the PID number in the first column, in this case 66550.
Launch a Terminal window and enter the following command:
kill -TERM 66550 (insert Aperture's PID instead of 66550)
This will send the "Software Termination Signal - TERM to Aperture, the same as pressing the "Quit" button should do, but send it directly, and not from the GUI that is unresponsive. This way I always succeded in cancelling a vaul update without force quitting. Not all processes can be terminated this way, however. The Terminal.app is also in the Applications > Utilities folder.
Regards
Léonie

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.

Aperture vault is full

Aperture Vaults.
Aperture 3.3.2
I have a 500gb vault that is now full, if I install another 500gb vault, will aperture continue to updated the new vault with my additional data or will it just fill that with all the original data then tell me that’s full?
Thanks.

Pharaoh,
Unless there are other things on the disk that you can move/delete then you have 3 options: (1) Get a larger drive, set it up inside Aperture and back up to it. This approach will take some time as going to a new drive will require Aperture to back up everything rather than just incremental changes (which is what it does normally). (2) Split your libraries into 2 or more and back the new one up to another (new) drive. (3) Don't use a vault as a backup. NOT recommended. A 1 TB drive is no more or less likely to fail than say a 500MB (assuming equal quality in manufacturing). Aperture vaults do not know how to "span" more than one drive - so far as I can tell.
Personally, I use two work drives (that only contain the library) and alternate between them for increased performance. One library will of course be behind the other at any given moment but has everything from the last overwrite. No matter which drive I work from, they both backup to the same vault drive.
To be honest, high performance large capacity drives have become quite affordable. I consider using 3 drives in this manner to provide a reasonable level of security without going into RAID or other solutions.
HTH
Robert

Aperture vault

I've been updating my monthly Aperture vault for 48 hrs and it seems to be 2/3 finished, but I see no action in past 24 hrs. I have close to 100 K pictures. How long will it take?

Blackbelly wrote:
I'm curious, Andy, how/where you do backup your Aperture pictures? I'd love an easier way to do it because my backup did end last evening after 60 hrs! No, there was no option to cancel because the spinning beachball hovered over every part of Aperture's face. Literally force-quitting was the only thing to do. I think I have my vault going to an external harddrive which is part of my time-machine, but not sure because my son set it up for me.
Rick, I use a MacBook Pro retina with limited internal drive space, so I have only the library on the internal drive, and all the images are referenced and stored on an external drive. The internal is backed up to time machine over wifi. The external image folder is backed up to my time capsure (to a data partition) using an App called Sync Two Folders.
My backup process is geared around my travelling, during which my internal library is also likely to contain managed images taken during the trip. If it's a short trip, I'm only concerned with new images, so I'll just backup new images by exporting the project as a new library to an external drive (and sometimes a USB stick).
For longer trips, where I'm likely to do a lot of editing and organising, I have an extra drive which I keep current using Sync Two Folders. This has a bootable partition which is a clone of my internal, and a data partition which is a clone of my referenced images.
Sync Two Folders is really quick and efficient at just updating changes to keep things current, but like all sync software it can be dangerous if you give it the wrong settings.
Andy

Aperture Vaults on TC

I would like to use TC, without Time Machine, to hold Aperture vaults, i.e., straight Aperture vault backup to the TC as external hard drive. In the CREATE VAULT dialogue box and selecting TC under SHARED DEVICES, the ADD button is greyed-out/unavailable to designate location of the new vault. Any insight into this matter or suggestions would be appreciated.

The permanently connected vault (vault 1) caused me problems and I was forced to recover all images from it into aperture on my imac
Not really sure what this means. What problems were you having and how did you recover all images from it into aperture?
the No2 back up does not seem to sync to the system anymore and I cant back up on it.
What do you mean by sync to the system ? Does the library not see the vault? Something else?
Should I delete the No 2 Back and re create a new vault on it by copying vault no 1 on my external drive that is permanently conected???
As vaults as just snapshots of the current state of the library (not much different then just copying the library except for speed) nothing is lost by making a new vault.
However I'm not sure what you are looking to do by copying one vault (vault 1) I thought that was the vault that was giving you problems?
If you are having troubles I would just create a new vault and update it,
regards

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

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 update stops.

Similar Messages

Maybe you are looking for