Skip navigation

New vault is smaller than old vault. Am I missing data?

332 Views 6 Replies Latest reply: Sep 29, 2011 5:03 PM by SierraDragon RSS
David Strait Level 2 Level 2 (175 points)
Currently Being Moderated
Sep 29, 2011 10:10 AM

I have three vaults (on three HDs) backing up one Aperture library (two onsite and one for offsite backup). Two of the vaults simultaneously became corrupted and I could no longer back up to them. I deleted these two vaults and created two news vaults on the same HDs where the original vaults were created. I was surprised that both of these vaults were much smaller than the other vault that was not corrupted (320 GB vs 360). Does this make sense? Shouldn't the new vaults be the same size as the old vault?


I am somewhat paranoid about this because I believe my library was recently corrupted and I have lost at least some of my master files from at least one project. I detailed this in the following thread, but have had no responses to my question:

Missing (most, but not all) masters from managed project


Anyway, now I am concerned that I may have lost 40 GB of  files throughout my entire library. The masters that I know I have lost would only be a few hundred MB at most. I have not gone through my entire library to check if there are other projects that have some missing masters. Is there a logical reason why my recently created vaults would be much smaller than my older vault?




PowerMac, Mac OS X (10.6.7), 2009 2.66 GHz 8 Core, 16 GB RAM
  • SierraDragon Level 4 Level 4 (2,665 points)



    I would expect rebuilding might make a new Vault smaller. However 40 GB seems too much to just be consolidation efficiencies.


    My response to your earlier post is reiterated verbatim below:



    Sorry I cannot answer the where-are-my-pix question, except to suggest Spotlight searches on file names,  and a careful review of the Trash folder.


    As a database person IMO a really large DB populated with (relatively) large unchanging individual field contents should be avoided in favor of a smaller DB referencing the large unchanging individual fields. In Aperture that means I recommend using a Referenced-Masters Library.


    Large files like a 300+ GB Library simply become unwieldy, and unwieldy leads to errors. Whether or not the errors are human PEBKAC or computer-generated does not matter. IMO Aperture should open with a warning message suggesting how to switch the DB to externally referenced Masters once a Managed-Masters Library reaches a certain size (say, 50 GB).


    Whether using a Managed-Masters Library or a Referenced-Masters Library, backing up originals on external drives prior to import into Aperture or any other images app is the best way to provide real images security.


    Good luck!


    -Allen Wicks

  • Frank Caggiano Level 7 Level 7 (22,805 points)

    If you look in the Library tab of the Inspector is there a project called Recovered files (or something like that). In a complicated library structure it can be easy to miss especially if you're not looking for it. You can use the search box  at the top of the Library Pane to try and locate it.


    When the Aperture repairs run any orphaned files are place in this Aperture created project.

  • Kirby Krieger Level 6 Level 6 (11,570 points)

    What I've seen is a Folder called "Recovered Folder" and within it a Project called "Recovered Project".  Searching the Library tab of the Inspector for "Recovered" should turn up everything.


    The one time it turned up I could not figure out why it was there, or why the Images in it were there (they were from a few Projects, and none of them had been missing).  Of course it was weeks later that I even saw the Folder.

  • SierraDragon Level 4 Level 4 (2,665 points)

    That approach sounds fine.


    My workflow is a bit different. Perhaps because of having come from a background of shooting film in remote and/or difficult locations, I am absolutely paranoid about losing/corrupting original images. And hundreds of stories like yours on this forum reinforce my paranoia.


    Original images never change, so I prefer to manually copy them to two locations asap after capture: one location is the MBP SSD and the other is an external backup HD that itself gets backed up off site regularly. That assures me that "the pic is in the can." Until two digital files exist on different media I do not consider the pic in the can.


    Then I reformat the card in-camera.


    The Masters then get imported into Aperture from the SSD by reference (i.e. "Storing Files: in their current location" on the SSD). After editing is complete (may take weeks or months), from within Aperture I relocate the referenced Masters to an external hard drive for long-term storage.


    I do use Time Machine routinely on the MBP, but for the daily-volatile activities going of the MBP. I prefer not to have TM be my backup-of-originals protocol. Instead TM backs up the SSD on the TM schedule and I back up original images asap based on my shooting schedule. Also the TM drive is a different drive than the drives used for long-term original image files archiving.


    TM does back up my Library because the Library lives on the SSD but I do not assume that TM works for Library backup. I back the Library up to Vaults (on the same drives I put archives of Masters on) independent of TM.


    As an aside, I have no fear regarding losing Versions, because unlike Masters edits can be redone. And after losing hundreds of hours of Photoshop editing over the years (the joys of Adobe's destructive workflow) I learned that the re-editing goes much faster...






More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.