Skip navigation

Why does "update vault" NOT include auto imported photostream images

1513 Views 22 Replies Latest reply: Nov 5, 2012 11:07 AM by léonie RSS
  • léonie Level 8 Level 8 (46,475 points)
    . Is it possible that these were imported in an earlier version of Aperture? It might have worked at one time but got broken in a later release.

     

    I cannot confirm that. Some of the images that got saved to the vault in my first experiment have been imported after the latest update. But all of them are conspicious in a way, that Aperture treats these masters specially - either they have been edited in an external editor or they have a small pixelsize, so no preview is created and the master doubles as preview :

    The list of the sole (Photo Stream) survivors after restoring my main Aperture Library from the vault: with the images manually imported from the PhotoStream their should have been 1313 images.

    importsession.png

     

    Searching all projects for the keyword "Photo Stream"- not only autoimport projects  turned up these additional images in the restored library: a wide range of import session dates:

    backedup2.png

  • Thomas Emmerich Level 4 Level 4 (3,470 points)

    Aperture 3.4.2: In my limited testing of 3.4.2, newly added photo stream photos now get backed up to the vault. But those that were skipped by 3.4.1 still do not unless you create a new vault.

     

    Note this issue is not one of the documented fixes in 3.4.2 so it could be a side effect of other changes made in the code.

  • léonie Level 8 Level 8 (46,475 points)

    Lessons learned is that I will never entirely rely on the mechanisms in Aperture for backup. Once in a while I will just copy the whole library to a backuo storage somewhere, This task could easily be scheduled in e.g. Carbon Copy Cloner, a program that could be useful in many other backup situations.

    Time Machine also works well with Aperture, and you get a version history. But it is a good idea to have several back-ups. I make bootable clones of the system before each software update (Carbon Copy Cloner works well, and also Super Duper is highly recommended).

  • Shuttleworth125 Level 2 Level 2 (415 points)

    I've got a hard drive with two partitions, SuperDuper backs up a bootable clone to them alternating each night. I thought I was paranoid doing this on top of vaults and time machine and offsite backups, but having seen that my wife (who's business this is) hasn't backed up her vault since JULY, I don't think I'm that paranoid after all!!

     

    Isn't there a saying, something about two sorts of people, those that are paranoid about backup and those that lose all their data?? Something like that anyway !!

  • léonie Level 8 Level 8 (46,475 points)

    Two current backups is a minimum.

     

    I once had a power failure (caused by a lighning during a thunderstorm), that struck while I was backing up. It killed both the backup drive and the mac in one go. I was very glad that I still had a month-old clone of my mac and my most impotant files on my iDisk.

  • Aye Es Oh Level 2 Level 2 (330 points)

    If you're using Time Machine, or any other backup program, make sure and quit Aperture before your scheduled backup occurs. Since Aperture is, at heart, a database program, it should have its database in a stable state when it's backed up. The only way to ensure that this happens is to quit Aperture to ensure that no information is being updated in the library, otherwise, the backup could be saved in a transitional state, which could be difficult to recover from.

  • léonie Level 8 Level 8 (46,475 points)

    Aye,

    Time Machine and Aperture 3 work well together. You can rely on database transactions being completed, before the backup will be written. This used to be a problem with older MacOS and earlier versions of Aperture.  The problem may still be with restoring an Aperture library while Aperture is running, but not with backing up.

     

    See for example:

    Aperture: Using Time Machine to backup a library

    http://support.apple.com/kb/HT1878

     

    Also, it used to be necessary to quit Aperture when backing up, to be able to make an incremental backup, but this also has been fixed, see:  

    Mac OS X v10.5, 10.5.1, 10.5.2: Time Machine may back up the entire Aperture Library each time

     

     

    Regards

    Léonie

1 2 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

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