4 Replies Latest reply: Jan 12, 2014 1:50 AM by Najinsky
Mandi B Level 1 (0 points)



I'd be really grateful if someone out there could give me some reassurance.  I'm dealing with a lot of photos from a long overseas trip, and have just finished making a photobook using the photos from five projects.  My library is getting a bit cluttered, so I would like to delete the projects from the library.  The masters are all stored elsewhere (apart from a few iPhone images that I don't really care about anyway) and are referenced in the library, but I've put quite a lot of work into editing them, which I wouldn't like to lose in case I want to come back to these photos at some later stage for some other reason.  I have just updated my Vault, and have been trying to look inside to see what's there, without really much success - I have to trust the software and assume everything's backed up okay.


So finally, here's my question: can I safely just delete the relevant projects from my library, knowing that I can restore them from the vault at some later stage if I need them?  On a restore, can one choose which projects to restore, or do you just get the whole lot back like drinking from a firehose?


Thanks in advance...

Aperture 3
  • Najinsky Level 3 (670 points)



    If you delete them from Aperture then the next time you update the vault, they will be removed from the vault too.


    The way I archive older/unwanted stuff is to CTRL+Click the project and use "Export->Project as New Library" (if you are happy keeping your images with the referenced images, don't check the box to copy the originals - so you are just saving your projects metadata and edits). This creates a new small library for just that project.


    Once you have a copy you can delete the project from Aperture (and it will be removed from the vault during the next update).


    Note 1, one copy of something is not a backup. One copy means it's the only copy so these projects should also be backed up somewhere like the rest of your data.


    Note 2, referenced image files are not backed up in the vault, so you need to be backing up your images seperately.



  • Mandi B Level 1 (0 points)

    Thanks Andy, for a very complete response.  And yes, thanks, I am aware that I need to back up my referenced files - I'm really just looking for a way of backing up the edits.


    What I don't altogether understand, though, is what the purpose of the vault is, if everything is deleted from it if you delete from the library. Why not just do as you suggest, and make a copy of the library on another disk in order to create backups?

  • léonie Level 10 (91,099 points)
    What I don't altogether understand, though, is what the purpose of the vault is, if everything is deleted from it if you delete from the library. Why not just do as you suggest, and make a copy of the library on another disk in order to create backups?


    Mandy, vaults are incremental backups. Copying a large Aperture library for backup may take a very long time. The vault will save time by updating your current vault and only writing the changes to it. This is much faster.


    If you want an archival backup - to save a snapshot of your current library, then don't update your vault after changing the library, but keep the old vault and start a new vault. You could create a new vault after each major change to your library. You may have as many vaults as you like, to backup the history of your vault.


    But frankly, I prefer to simply backup the original image files, directly before importing them to Aperture, and then backing up the Aperture library with Time Machine and to keep two additional copies of the Aperture library on separate drive. But I never delete projects from the Aperture library that I want to keep. My Aperture library has all my photos - I try to save space by rigorously deleting single photos that are technically bad, boring, or redundant.

  • Najinsky Level 3 (670 points)

    The ability to export as Libraries only came in in version 3, back in version 2 they were exported as projects which wasn't quite as useful. Also iPhoto now reading Aperture libraries adds a bit more convenience.


    I've not used vaults for a while, since way back in early version 2. I can't confirm it still does this now, but at the time it didn't store thumbnails and previews for secondary and multiple versions in the vault, only the master version. So if you used a lot of versions it meant the vault could be much smaller than the library.


    So back then vaults seemed a good idea, but in one Aperture version it started taking ages to process the vault updates so I gave up on them.


    I use referenced masters and am very selective about which images get previews so my library is very small, which with USB 3 means it's easy and quick to make ad-hoc backups, and I also let time machine back it up over wifi.


    For my referenced images, I backup using software called SyncTwoFolders which also lets me keep deleted images around for a while and do a few other tricks. For example, periodically I verify the integrity of my backup by using locate referenced files and pointing it at my backup drive and forcing a reconnect to the backup instead of the main. When it's done, I can then check for missing files in Aperture to see if my backup has any gaps. I also like to move things around from time to time, just to give me confidence I know where everything is and I haven't created too many strays.


    It's much easier and quicker than vaults and at this time, I can't think of a single advantage of vaults (for me). But obviously a vault is a million times better than no backup!!