Aperture Vault problem?

New Macbook Air... trying to restore a Vault from ext. HD. I get this: 'The vault “Untitled Vault” has never been updated and contains no library information. Please restore from a different vault.' But there's nearly 70GB of data on this so-called 'never updated' Vault... Any ideas?

Try to repair your vault:
Hold down the ⌥⌘-key while double clicking the vault.
If this does not help, turn your vault into a library - temporarily:
Do you have enough disk space on your external drive to make a copy of the vault? Then you could try the following fix:
Duplicate the vault.
Select the copy and and use the Finder command "File > Get Info ⌘I" to open the Info panel.
Disclose the "General" brick in the Info panel and remove the "Locked" bit.
Disclose the "Name & Extension" Brick and change the filename extension to ".aplibrary".
Now you should be able to repair the vault by holding down the ⌥⌘-key while double clicking the vault.
Select all three repair options in turn, until you can open the vault as a library.

Similar Messages

Reimporting from Aperture Vault problems

I had to reinstall my photo library from the vault when my external hard drive corrupted. When I reinstalled, the various projects in one folder combined into one, and now I have no distinctions between photos in one subject. Anyone ever had this problem?
Since I do the photography for a weekly newspaper, I have thousands of photos and need to keep my library on an external hard drive. My computer was just too slow with the photo library on my computer. Is there a way around this problem?

Yes it is a normal but unreported feature. When you run the vault command the vault created is a snapshot of the current state of the library. If there is a previous vault for this library then images that are in the vault but no longer in the library are moved to the folder you referred to.
If you are certain you do not want any of those images anymore you an delete them.
regard

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

HT1338 my Aperture having problem, does not open and I can not open photos.

why my aperture having problem?
stephen harold

See if you can Force Quit things holding CMD+Option+esc keys.

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

Aperture Vault and Time Machine

Does anyone know how this will operate ?
Will the Aperture Vault be TM 'unaware' ?
Roger

I guess there'll be a new 'vault' mechanism, as TM backs up your hard drive and vaults typically reside on another drive. whether or not TM can work with other drive I don't know.
Perhaps vaults will remain largely unchanged and be used for recovering entire projects or libraries, and TM will allow you to go back through previous version of the current file, or restore individual images that you may have deleted.
Regards
Steve

Folder labeled "Images Removed from Aperture Vault #1"

Hi all,
I was just looking at everything that's on the External Hard Drive on which I have my Aperture Vault. There's another folder on that EHD labeled "Images Removed from Aperture Vault #1." Noodling through that folder, it seems to be every master that I've deleted, broken down my year, month, and even day.
Is this normal behavior? Can I delete all those sub-folders, etc.? Should I keep the folder itself? Did I somehow set this up initally?
Anyhoo, thank you all for any suggestions.

Yes it is a normal but unreported feature. When you run the vault command the vault created is a snapshot of the current state of the library. If there is a previous vault for this library then images that are in the vault but no longer in the library are moved to the folder you referred to.
If you are certain you do not want any of those images anymore you an delete them.
regard

Can't create Aperture vault on my new 1 Terrabyte Hard Disk

Just bought two new Maxtor 1 terrabyte harddisks to back-up my Aperture vault,
my Aperture Library is now about 450 Gb. When I'm making a new vault on the new hard-disk, wich takes several hours, my G5 will "colapse" after a few hours, the whole system is stuck and the only way to get out is too get the power of.
When I restart and look at the disk I see that about 250 GB has been transported, I tried this several times and it's always stuck at about the same point. Also when I'm dragging the Aperture-file to the new disk, the same thing happens.
When I do the same thing to a Maxtor 500 GB disk everything worls fine.
Does anybody have a clue ? Thanks in advance !
With kind regards
Albert Brunsting

It could be that the 1TB drive is heating up and shutting down after turning for several hours causing the system to lockup. Might try adding a cooling fan pointed at the external HD.
One alternative is to reduce the library size. Export projects from that large library into another empty one until both are about equal in size. Then back up each library individually onto the external HD.

Any way of finding out how Apple will solve the Aperture / ACR problem?

Has anyone out there gotten any comments from Apple support or other people "in the know" about how Apple is going to solve the Aperture / ACR problem, and any potential time frame?
Of course, Apple is going to work on problems with its own RAW conversion; that goes without saying. But does anyone have any knowledge of whether Apple is going to open up the ability for Apple to send RAW, unconverted images to Photoshop, so that ACR can handle them?
I think knowing this now is pretty crucial. I am willing to live with the pain Aperture is going to impose on my workflow, in exchange for the file organization benefits it provides, IF I know that I'll be able to use Aperture with ACR soon (near term). But if Apple is going to just tinker with the RAW converter, and not attempt to send RAW files to ACR, then as someone else posted in another topic, this could be a long wait, and other companies have taken years to hone their RAW converters.
This is kind of my last-ditch effort to keep Aperture around, and build my workflow around it. If I know that within a month or two at the most, I'll be able to be using ACR directly when editing new versions, then I'll absorb the pain until then. But if I am looking at waiting six months for it (several man years), or riding out the process of Apple trying to get their own converter fixed, then as much as I don't want to, Aperture is going to get returned or hit eBay.
Does anyone have any idea on this? I've held up my projects for the past week trying to reorganize my workflow to work with Aperture, and I've got to pound the gavel, make a decision, and pursue a direction. Knowing what direction Apple is going to take with this makes all the difference in the world in what I do.
Thanks in advance for any info you can pass on.
Brad
Powerbook G4-1.33GHz-17" / Powermac G4-1.4GHz Mac OS X (10.4.2) PB: 1GB RAM, Radeon 9600-64MB / PM: 1.25GB RAM, Radeon 9000Pro-128MB

This "Open External Editor from Master NEF", versus open from a dynamicaly created version is, I have decided, crucial.
I am getting less clumsy with the interface, but I simply can not get all white balance, and noise reduction done on my best available light shots.
ACR in CS2, and a subsequent "Neat Image" scrubbing is excellent for this.
The automatic association within a stack, of the resulting flattened file would be a big difference. I agree a formal statement from Apple would make me more inclined to really commit to Aperture for all my work.
Going one step further, it would be nice to keep the layers on the round-trip Master file, even if you would work with a dynamicaly created version of the returned "master" within a stack. It would occupy more disk space, but would do so only for those images where the user has made a quality decision.
Michael
Powermac G5 dual 2GHZ, 2.5GB - 2x20in Mac OS X (10.3.4)

Time Capsule, Aperture Vault, Folders

I'm considering acquiring a Time Capsule to replace my WD NAS, which is clunky, unreliable, and absurdly slow. My Aperture library seems to constantly become corrupted by my using the NAS both for Time Machine backups and as a duplicate stoarge place for my Vault.
I understand a TC will allow me to backup using Time Machine. But will it also allow me to set up seperate folders, one for an Aperture Vault, and another for storing documents or other material outside of my Mac's hard drive? I also backup incrementally using Superduper and a portanle USB HD. Does anyone know if I could do additional Superduper incremental backups onto a TC? (That's a lot of backing up, I know, but I'm paranoid about losing my stuff)
OSX 10.9.1
Aperture 3.5.1

The TC will have exactly the same issues as the WD NAS.. it is designed specifically for Time Machine.
Constant corruption of a library is due to network disconnections which over wireless are to be expected.. wireless is not a reliable media for holding open files.
You can use the TC to mix files and backups..
See Q3 here.
http://pondini.org/TM/Time_Capsule.html
But I don't see you getting any further down the road to reliable use than you have now.

Is there a need for Aperture Vaults if I'm using Time Machine and/or SuperDuper?

Hey all
What's the benefit of Aperture Vaults if I'm using Time Machine or SuperDuper for my regular backups?
John

John,
Aperture vaults are snapshots of a certain moment. So you can create a collections of vaults saved at specific intervalls, say one each year, or before you upgrade your system. If you keep your older vaults, you will be able to restore images from many years back. If your library is huge, you may only notice years later that an important image got corrupted.
Time machine backups are very convenient and you can go back in time easily, but you can never be sure, how much back in time your backup will go. You have no control over which older versions will be deleted, when TM runs out of space.
Clones are great, i.e. if you create bootable clones. This way you will be able to revert to a previous system without reinstalling. With respect to Aperture libraries cloning your library will give you the same benefits as vaults.
My experience tells me, that a mixture is good. If you can, keep three backups, and not all in the same place.
I keep one backup at my office and two at home. I have a bootable clone, a TimeMachine backup, and occasionally create a new vault. My most important images are in my dropbox and synced to all my macs.
regards
Léonie

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

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

Similar Messages

Maybe you are looking for