Using Vaults

Hello everyone (first post) I am having a little trouble backing up all my aperture photos onto a vault which is going to be stored onto an external hard drive. When i try to add a new vault it says that out of 10668 only 1733 (managed files) will be backed up, and 9212 photos (referenced files) will not be stored in the vault. is there anyone that can help me back up all these photos onto one vault?
PS: out of 10668 photos i have 8991 on Mac HD3 and have moved the library location onto this hard drive.
and im using Aperture 2.1

Referenced files are not stored in the Aperture Library so they can not be backed up in the Vault. You need to develop another backup strategy for referenced files or move them to managed files.

Similar Messages

Can I move photos from one computer to another using Vault?

Can I move photos from one computer to another using Vault? I use an external hard drive as a vault for my Imac and I want to import photos to my Macbook pro. I have aperture 3 on both units. Can I just plug the ext. drive into the laptop and import from the vault?

You can't import from the vault but you can restore that vault onto the MBP. This will restore the complete library that is contained in the vault.

Is there any advantage in using Vault over Time Machine?

Hi all,
Yesterday I imported around 6000+ pictures from iPhoto and consolidated them into my Aperture library. After much re-organisation into projects, folders etc. I decided to update my backup Vault to preserve all my hard work. The Vault is located on a connected external drive with plenty of spare storage. I had previously backed up successfully to the vault when there was only a few dozen pictures in my library.
After initiating the Vault update process I then left it to get on it (and to have dinner and then watch the football...) and after several hours was dismayed to find that the process appeared to be stuck at just over 50% completion. It was obvious that no further progress was being made.
I was also concerned that there appeared to be no mechanism to cancel the process and the only course of action I could take was to apply a Force Quit against Aperture - not something that I care to do, if I can possibly avoid it.
After a rudimentary search of this community I saw that several others had experienced the same problem - although some suggested that a fix had been applied in recent versions (although I am running the latest version).
Given this, I'm reluctant to use the Vault again - particularly as there appears to be no means of cancelling a stuck job. I do however use Time Machine, so my questions are:
1) Do I really need to use Vault if I have Time Machine making regular backups of my Aperture library to an external drive?
2) Does using Vault give any advantages over Time Machine?
3) Is anyone else experiencing this problem with the current version of Aperture (v3.3)?
4) Is there anyway of cancelling a stuck Vault update other than the sledgehammer approach of Force Quit?
Thanks in anticipation,
Simon.

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

Using Vault in Aperture

How are most photogs using vault? Can you restore select projects deleted from Aperture, or only the entire library? If you delete a project from Aperture that is in the vault, then update the vault, is the deleted project still in the vault? Any help would be great!
Thanks,
Kirk

For incremental's on a Mac it is hard to beat Time Machine. TM will backup external drives as well as the internal
There are two concerns with digital images, the originals as they come out of the camera and the work you do to them after they are in Aperture.
While loosing an Aperture library would be painful it can be recreated as long as you have the originals. So the first step is to backup the originals, I backup my originals while importing them into Aperture (there is a setting in the import pane to make this simple)
Then I have two vaults on separate drives for each library and finally I have TM running.
Finally backups are no use if when you need them you find out they weren't doing what you thought so every now and again restore from one of your backups to make sure it is useable. The time to find out it is not useable is not when you really need it.
I move my active library out and restore one of my backups and use that as the new active. This way I know for certain the backup will function as it should,
regards

Using Vault With An External Hard Drive

Finally got my referenced Library in order thanks to Jade. Just wondering now how I can backup the external drive with the masters. I tried using Vault but it clearly is not reading the external drive. Is it possible to use the vault feature with an external drive?

The vault in Aperture will not backup your referenced masters, it will only backup the Aperture library. Remember your masters are not in the Aperture library.
To backup your masters you could use Time Machine, probably the easiest solution.
As to your question regarding external drives and Aperture's vault, you can setup a vault on any drive connected to your Mac. Internal, external, networked. I have my vaults on a network drive connected to an airport extreme.

Backing Up Images - USING VAULT - Does Aperture Use Additional HD Space

I am using Aperture 1.5. My library contains about 500gb of Photos. It is saved to external hard drive 1. I would like to back up the data using Vault to external hard drive 2 (space available is 850GB). However, I receive a message stating there is NOT enough room to perform the back up.
Has anyone experienced this problem? Does anyone have a suggestion? I do not want to just drag and drop the library as its complicated to keep version controls.
Message was edited by: Keith254
Message was edited by: Keith254

Keith - I am having the same problem with Aperture 2.01 & Leopard. It appears that I must have more free space on my vault drive than the entire size of my aperture library file. Which, of course, seems silly since I have added 4gb to my 100gb aperture library since my last vault sync and my vault drive has 103gb of free space. In other words, my next vault sync should ideally only need 4+ gb to update the vault. I hope apple or someone can tell us what we are doing wrong or I hope they can fix that issue.

Restored library in Aperture 3.1.2 using vault from Aperture 2.1.4; in the browser I can not see all the pictures, when i click on the empty frame in browser some of the picture do not appear, how do i fix this?

I tried restore library using a 2.1.4 version vault in version 3.1.2 not all the pictures transferred; how can I fix it, I have 13,195 pictures?

Perhaps run through the steps listed here and then let us know how you go.
http://support.apple.com/kb/HT3805
Tony

When using Vault in Aperture, is the storage incremental or is it replacement?

I like the backup feature of Vault, but don't know if i need to keep the external hard drive mounted for incremental backups or if I can dismount and store until I feel another backup is necessary. I like the idea of incrementals, but if it isn't the way it works, I can save wear and tear on the drive as well as electricy, by removing it. Suggestions?

For incremental's on a Mac it is hard to beat Time Machine. TM will backup external drives as well as the internal
There are two concerns with digital images, the originals as they come out of the camera and the work you do to them after they are in Aperture.
While loosing an Aperture library would be painful it can be recreated as long as you have the originals. So the first step is to backup the originals, I backup my originals while importing them into Aperture (there is a setting in the import pane to make this simple)
Then I have two vaults on separate drives for each library and finally I have TM running.
Finally backups are no use if when you need them you find out they weren't doing what you thought so every now and again restore from one of your backups to make sure it is useable. The time to find out it is not useable is not when you really need it.
I move my active library out and restore one of my backups and use that as the new active. This way I know for certain the backup will function as it should,
regards

Using vaults to restore libraries

Hello All,
I've got a question on vaults in Aperture 3. Let's assume my HD fails and I can't do anything to recover data from it. I install everything from scratch and now A3 does not have anything in the library. Can I use the vaults to re-create my pictures library, as it was before the HD died?
Thanks,
Valerio
ps: this is only an hypothetical scenario, fortunately my HD is intact!

Yes, and i guess you know, it must be on a different Drive.
You can also back up a project, or the whole Library manually, if you want to keep a fixed copy at a particular point in time, Go to File>Export Project as Library.
Allan

How can I transfer my photos to an external drive without using vaults?

In light of what is going on with all the uncertainty over Aperture support in the future, I am trying to be proactive and save my masters/versions to an external hard drive without them still being tied to Aperture. I've been at it for hours with no luck. I can create a new vault but I want a system where I can choose which individual projects I want to download to the external and the ability to go back to the external HD to work on files. Vaults seems to be an all or nothing backup and doesnt allow choosing 1 particular file to work on. Same thing with Time Machine? Is this possible or are all the adjustments I made in the past few years forever tied to Aperture?

Yes i understand that. In fact when ever i import new images i do not save them in the Aperture Library. I save them on my server wich is pretty much the same as an EHD in this respect. There must be a clean way to do this....
I have in mind:
1) Export all your Photos from Aperture to EHD without an loss of Information/tags/RAW ...
2) Import them back but instead of choosing In the Aperture Library choose In their current Location. See Screenshot.
This might be an appropriate solution if you want to keep Aperture for some more months. Otherwise of course you can change step 2) easily by importing them right away in your new application (Photos from Apple or Lightroom...) In other words wait with this step until you definitely switch your app;)
jl

Unable to use vault back-up reports error

May not be accurate, but I seem to recall the back-up worked before these updates.
2008-09-25 14:07:45 -0700: Installed "Java For Mac OS X 10.5 Update 2" (1.0)
2008-10-10 09:41:08 -0700: Installed "Security Update 2008-007" (1.0)
2008-10-16 19:16:32 -0700: Installed "Migration and DVD ⁄ CD Sharing Update" (1.1)
Adobe Indesign 5.0.4 update.
When trying to update a vault to an external firewire drive I receive the following error.
Update Vault Error
The following error occurred:
Aperture has detected a problem with the vault “rwsaperturevault”. You need to remove this vault and create a new one.
Having removed and recreated the vault the same error condition was reported.
The directory structure at least part are recreated.
All other file operations outside of aperture works.
The drive does not have file permissions enabled. HFS+ file system.
Anyone else has seen this problem?

yes. same problem. attempting to back up 16k files for the first time. I am getting repeated errors saying the vault needs to be deleted and a new one created, but that does not do anything. Any help is appreciated.

How to delete projects from Vault

Ok, here is the issue.
I work remotely on a laptop and my main library and vault are on my home computer.
I only keep the last couple of projects on the laptop and use the vault to backup those projects. I used managed files.
When I get home from the road, I export/import the projects to the home machine and master library to do further work and use vault on an external for backup.
So, on the laptop, I will delete projects to make more space on the hdd and I dont need them on the laptop any longer (they are already in the master library and vault at home).
However, the problem is that when I delete those projects and then update the vault, it does not seem to delete those projects in the vault. So the vault just keeps growing in size until it fills up and I cant seem to delete those projects from the vault. Again, both the laptop library and the laptop vault are simply for backup while on the road so I'd like to have the vault on the portable be able to stay synced with the library on the laptop. When I delete a project, it does the same in the vault to keep the external space consistent as well.
Is there any way to do this? Shouldnt the vault basically just back up the library and when something is deleted from the library it should be deleted from the vault as well?
As it is, I need to delete the entire vault when it fills the external and create a whole new one after deleting the projects from the library.
Is there an easier way?

I have not contacted AppleCare, but will if this is how its working for others.
Have you tried this and are sure it is working that way? After all, last week after deleting three projects from the laptop and main library and then updating the vault, I had a vault that was over 80 gigs in size while the library was now less than 20 gigs in size.
After deleting the vault and starting a new one, the new vault was approximately the same size as the library, actually slightly smaller like it is with the master vaults at home with the main library.
I have twice now had my external fill up with the vault while I had been constantly deleting old projects on the laptop. So it just seemed to keep adding new stuff to the vault, but not get rid of the old that I was deleting.

Is it possible to exclude thumbnails and previews from a vault?

I think in Aperture 1.5, vaults did not include any preview or thumbnail files, but only the files containing metadata, adjustments etc. (and the masters, unless referenced only)
Somewhere along the way to 3.0 this changed so now previews and thumbnails are backed up each time you update your vault.
This has two BIG drawbacks:
- the vault becomes much larger than necessary (I always generate large previews)
- the update process takes much longer as more files need to be copied.
On the other hand, I do not see any tangible benefit of including the extra files - provided I back up both masters and the adjustments, I should be able to regenerate thumbnails and previews after a restore following, say, a fatal hard drive error.
(If I chose to delete all previews and thumbnails prior to creating a vault, I assume that the vault would be significantly smaller, without losing any information that cannot be recreated by 'generate thumbnail/preview')
Is my understanding correct?
If so, is there a way around it?
If not, can we please have this option in Aperture 3.5 or 4.0?
Thank you!

Hi Matt. You raise an interesting point. What you say makes sense to me.
My general response is: external drives are cheap. Buy what you need and don't spend any time trying to "save" disk space. IME, the administrative overhead is far more costly than the upfront equipment costs.
Here are some specific answers (as I understand how Apeture uses Vaults).
There is no way to exclude Previews from Vaults. Each Vault includes all extant Previews.
Each Vault is a differential back-up. Updating the Vault should update only those files that have been added, changed, or deleted. Unchanged files -- including Previews -- are not backed up anew each time you update a Vault. The amount of time it takes to update a Vault will vary based on the number of changes made, and should have nothing to do with the size of the Library or the number of files in it.
You can test your hypothesis. Delete all your Previews, and create a new Vault. Let us know what you find out.
Suggestions for enhancements should be made directly to Apple via "Aperture→Provide Aperture Feedback". The forum is -- officially -- strictly for user-to-user interaction.

Two computers, one vault

I am fairly new to using Aperture. I have read quite a few of the how-to's about the vault feature. So, I recently got myself an external drive and told Aperture to set up a vault on it. Here are some questions which I am not quite sure about:
1) when I now add some images to aperture (as a "managed master") is that image initially stored a) just on my computer, b) just in the vault or c) both
2) on this computer if I now say "update vault", does that image now get copied to the vault? Is it still kept locally on my computer
I have a laptop which I use for traveling. I am the only one using it as well as the desktop. I would like to be able to work on the same images in either place, so:
3) Can I use vault as a way to view and work on my images on my laptop when I am traveling and then continuing to work on them when I am back to my big computer?
I thought the answer to 3) was "yes". So I installed Aperture on the laptop (it's brand new) and then 'restored the library" from the indicated vault. It warned me that it was going to delete the local library which is Ok as it was a brand new laptop. But now I am not sure I am doing it right.
Thanks for any help on these three questions!!!
Pito

Hi Pito. Let's deal with the Vault first (and then maybe the two-computers set-up questions).
The Vault is a differential back-up of your Aperture Library. You create and administer your Vault(s) from within Aperture. It's primary function is to serve as a back-up. If your Library gets ruined, you can restore from your Vault the last version of the Library that you "Vaulted".
Like any back-up, a secondary function can be to move files from one location to another. Used this way, the Vault provides little value over simply copying your Library. So little, in fact, that I see no reason to use it this way.
Your Library is a Finder "Package". A Package is a special OS X file which contains a group of folders and files. It shows in Finder as a single file, but you can see what is in it by right-clicking the file and making the appropriate selection. (Don't alter anything in a Package file.)
So, again, the Vault is simply a specific way from within Aperture to create a back-up of your Aperture Library. That's all.
Pito wrote:
1) when I now add some images to aperture (as a "managed master") is that image initially stored a) just on my computer, b) just in the vault or c) both
Images are not Masters, "Managed" or otherwise. You import files into Aperture. That tells Aperture: "Create an image for this file, and keep a bunch of information with it". Part of that information is the location of the original file. That file, once it has been imported into Aperture, is referred to as a "Master". Aperture is non-destructive: the Master is never altered.
The image in Aperture is not a Master. The image has a Master. Every image in Aperture has one Master. Some images have the same Master.
The Master can reside anywhere Aperture can access it. Aperture always keeps track of where the Master is stored (it knows its address). If an image's Master is located inside the Aperture Library Package, it is said to be a Managed Master. If the image's Master is located outside the Aperture LIbrary Package, it is said to be a Referenced Master.
When you import a file you specify where the Master should be stored. What you specify determines whether the image in Aperture will have a Managed Master, or a Referenced Master.
In no case is the image or its Master automatically added to a Vault. You must manually update your Vault to include recently added images. The Vault backs up only the Aperture Library. The Library does not include any image's Referenced Masters. Therefore the Vault does not include any Referenced Masters.
There is a warning message that tells you this when you update a Vault if your Library contains images that have Referenced Masters.
Pito wrote:
2) on this computer if I now say "update vault", does that image now get copied to the vault? Is it still kept locally on my computer
You should now be able to answer that.
Pito wrote:
3) Can I use vault as a way to view and work on my images on my laptop when I am traveling and then continuing to work on them when I am back to my big computer?
You can, but it's not a good way (at all) to accomplish what you want. There is a section in the User Manual on exporting and merging LIbraries (which is what you want to do).
Take your time learning. Aperture is huge and powerful -- and has a long but not steep learning curve. It has tools to do what you want -- but it takes some time to get it all set up.
Message was edited by: Kirby Krieger

Library too Large for Vault?

I just bought an iMac 27" with Mavericks. I was on an iMac running Snow Leopard and Aperture 3.2.4. I used Migration Assistant to move everything over and updated to Aperture 3.5.1. My Aperture Library is 550 GB (40,000 images). Now I can't use Vault! Every time I try (to two different external drives), it stalls and when I look I see that Aperture is not responding. I've let it go for hours but eventually have to Force Quit. When I look at the Vault file, it has about 33 GB in it.
The Apple Pro support people suggested that the problem could have to do with the size of my library. Indeed, we created a very small library and it saved to Vault without difficulty. However, I'm not wild about dividing my library and it seems odd to me that I'm having this problem now when I didn't have it with Snow Leopard and Aperture 3.2.4.
Anyone else having this problem? Thoughts?
Thanks!

I have found that Aperture Vaults (at least up to 100 GB) will transfer reasonably quickly to a direct connected drive. The same is not true of transferring Vaults past about 20 GB to a network drive (to be clear - a drive that is not direct connected by wire and which is accessed by Wi-Fi). Transfer to these network drives of vaults over 20 GB can take hours to days (if at all successful) - what is daunting is Aperture reports it is working (Status Bar and activity report in bottom left corner) but Aperture is locked up from any furthur activity and Force Quit Panel reports Aperture as not responding. In this state, I have had files still transfer after lengthy intervals although after a couple of days I usually give up. Force Quit is the only way out. Do this once or twice and you get the message that you need to rebuild your database. I have found that rebuilding the database does help and speed up the transfer to a Network drive so long as you are in the under 50 GB size. It does not seem to have any impact on larger vaults.
I have split up my big vault into smaller vaults by category and this has helped somewhat but you now have all these vaults which can be a pain. I still have some larger vaults and these continue to be problematic for the Network drive.
I have a late model iMac and all my drive and Network Drives are Western Digital with all the latest software and firmware (as of April 2014).

Using Vaults

Similar Messages

Maybe you are looking for