Aperture 3.2.1: vault questions

Core Duo Processor; OS 10.6.8
I have Time Machine backing things up on my HD, but the Aperture Vault is on an external HD.
Like many of you, I had to revert to version 3.1.3 when version 3.2 kept crashing. One problem I saw while I was still attempting to use version 3.2, in addition to the crashes, was that I could no longer access the vault because the photos there were created by an earlier version of Aperture - version 3.1.3.
Can anyone answer one - or all - of these questions:
1. Will the content of the vault automatically be upgraded if I try version 3.2.1?
2. If not, can I use the 'update vault' function in Aperture to upgrade the photos in the vault? or
3. Would I have to delete the current library on the vault, create a new one, and rename it?

Update:
Since a few people had read the post but no one had an answer, I decided to bite the bullet and try the new upgrade.
I am happy to report that all is well with version 3.2.1. All I had to do after the download and installation finished was to open Aperture and update the vault from the HUD.
To be on the safe side, I repaired permissions and verifed the disk on the partition dedicated to Aperture vault on the external HD, then restarted.
Aperture is behaving as it should.

Similar Messages

Why are my masters offline in aperture after restore from vault (not referenced)

I really hope someone can help as I am at my whits end!
I recently had to do a clean install of lion and so dutifly backed up my Aperture 3 library to a vault. 100% of my library was managed and I have never referenced files and always avoided it.
I then restored the aperture library from the vault.
When the new library opens all the files and project organisation is there, but quite a few images are showing as offline.
I have noticed that the number of offline images is going up by the minute. Something is changing the state of the images.
I have checked inside the vault and all the masters are there, but for some reason aperture things they are missing. When selecting the "offline" images and then consolidate masters it gives me the alert that there are no referenced files!
I have tried repairing and then rebuilding the database but this has no effect.
Does anyone know whats going on or how I can recover the situation?
I really do look forward to some help from you guys.
Many Thanks.
Brad

It seems so Puzzling Shutter.
I have the Aperture Library and the Vault both on the internal hard drive.
I prepared the vault yesterday and according to aperture it was up to date (updated it several times to make sure)
My vault was on an external hard drive and I copied it to the mac before restoring.
Once I restored. The library is the same size as the vault.
When I use the meta search bar in aperture and select show offline images it shows 144 but each time i come out of the all photos view and go back in this number creeps up!
When I then go and check the vault (on the mac) and the library, the file arent there either but the size of the library and vault hasnt gone down.
Do you think it could be because I copied the vault to the mac before restoring from it. Do you think I should try restoring from the vault as it is on the hard drive?
I really appreciate any advice.
Thanks,
Brad

Vault size vs APerture library size and related questions

My aperture library is 50GB for some 65,000 referenced pictures...how does this compare with others? To me, it seems a bit big.
Also odd. The vault backup of my libarary is 9.1GB ONLY! How come?
I think that all of my pictures are referenced.....is there an easy way to check?
If I make a new fresh library and restore from the vault, what will I loose, if anything? Will I need to reconnect pictures or anything?

that seems about right to me. what's taking up space are previews and thumbnails. afaik, the vault doesn't hold any of those, only the database, albums, projects and configuration files.
if you restore from a vault, all the previews and thumbnails have to be rebuilt. you can save a little space that way, because the thumbnail files don't shrink when you erase photos or move them to another project, but personally i don't think it's worth the time and effort.
j

Aperture Vault Question

Okay, so I am looking to simplify my photo storage process, as I recently got Photoshop and am going to be doing more and more editing and what not.
I also have Aperture that I back up using its vault feature on my external hard drive, creating two locations for all my pictures - within Aperture and the vault on my external hard drive. Is it necessary (aka, would it be a good idea) to keep the original pictures in my home folder/pictures folder? I am hoping to free up space if not necessary.
Also, I would probably end up burning the master images to a DVD from Aperture for a third back up. I may sound paranoid about this, but I don't want to lose anything.
I'm just looking for an easy back-up process for my photos.
Thanks!
Josh

Also, I would probably end up burning the master images to a DVD from Aperture for a third back up. I may sound paranoid about this, but I don't want to lose anything. I'm just looking for an easy back-up process for my photos.
You do not sound paranoid, just prudent. The essence of competent digital photography is multiple redundant backup.
Your Managed-Masters-Library and Vault workflow is fine now but only in the short term because hard drives slow as they fill and using a Managed-Masters Library image files will sooner or later overfill the internal hard drive unless completed Projects with Masters are constantly purged from Aperture but that is inappropriate workflow for most photogs, and the benefits of using a Managed-Masters workflow are minimal.
I recommend to Manage by Reference with Master image files stored on external hard drives. Especially important for iMacs and laptops with a single internal drive. The workflow as described below uses a Referenced-Masters Library.
I feel pretty strongly that card-to-Aperture or even camera-to-Aperture handling of original images puts originals at unnecessary risk. I suggest this workflow, first using the Finder (not Aperture) to copy images from CF card to computer hard drive:
• Remove the memory card from the camera and insert it into a memory card reader. Faster readers and faster cards are preferable.
• Finder-copy images from memory card to a labeled folder on the intended permanent Masters location hard drive.
• Eject memory card.
• Burn backup hard drive or DVD copies of the original images (optional recommended backup step).
• Eject backup hard drive(s) or DVDs.
• From within Aperture, import images from the hard drive folder into Aperture selecting "Store files in their current location." This is called "referenced images." During import is the best time to also add keywords, but that is another discussion.
• Review pix for completeness (e.g. a 500-pic shoot has 500 valid images showing in Aperture).
• Reformat memory card in camera, and archive originals off site on hard drives and/or on DVDs.
Note that the "eject" steps above are important in order to avoid mistakenly working on removable media/backups.
Also note with a Referenced-Masters Library that use of the "Vault" backup routine backs up the Library only, not the Masters. Masters should be separately backed up, IMO a good thing from a workflow and data security standpoint.
External drives that are not eSATA (or at least FW800) decrease speed, so your Aperture Library should stay on the internal drive.
When using Referenced Masters the Library does not actually hold the large Master images themselves. That way even a laptop drive can hold an Aperture Library of 100,000 images by referencing Master images that live on external drives. To store Master images by "Reference," in Aperture when you go to Import on the right hand side of the import window you must select "Store files in their current location."
Note that by sizing Previews carefully (I suggest creating Previews manually and only during down time, and sizing to the pixel dimensions of the laptop display) all images can always be viewed on the laptop even when the Masters are off-line.
Good luck!
-Allen Wicks

Yet another Time Capsule /Time Machine / Aperture / Vault Question

OK - It is recommended that the Aperture Library be excluded from the Time Machine backups, and to create vaults instead. Fine.
Has anyone tried including the vaults instead of the library in their TM backups? Any issues? Does TM backup only the changes to the vault, or does it see the vault file as one file, and backup the whole thing after the vault has been updated?

I haven't experienced it personally. That's because I have my Aperture library excluded -- I'm using SuperDuper to clone the entire library once a week (Aperture isn't open when this happens), and I also use vaults.
There were numerous threads here about it, though. Or, I should say, they were in this forum, or they were in the Leopard/Time Machine forum. There was a fair bit of complaining about it... so I take it that some people have been affected.
I doubt there's any danger of data loss, given TM won't back up the Aperture library when it's open -- which is when the database is in use and there could be open journal files. But... if you try it, and you notice that TM is taking 2-3 hours of crunching on your drive to back up the whole library, don't come yelling to me. I'll just say "known issue" and point to the Kbase article.
Deal?

Will Aperture backup to a vault with daisy chained external hard drives

I am moving my Aperture library to a 6TB external drive. I want to back that up to a disaster drive consisting of 2 g-drives daisy chained, one 2TB and the other 4TB.
Will Aperture recognize the daisy chained drives as a single drive and backup the Aperture library to these drives as a single vault?

Caveat: answering your question requires one to make lots of assumptions, any one of which might change the answer. I do not know if Aperture would do so or not but personally I would not recommend it.
Note that daisy-chaining is simply a method of connecting drives; the drives themselves each remain fully independent. One needs to build a RAID array to combine independent volumes, and that is usually best done with fairly identical drives rather than with a 4TB and a 2TB.
I strongly believe that unless one is a true mass-storage expert very large Managed-Originals Libraries should be avoided. IMO far preferable is to instead use Refererenced-Originals Libraries.
Databases invariably perform better in numerous ways when smaller.
-Allen

Aperture library copy vs vault

Hi,
sorry if this is redundant, but I couldn't locate the clear answer to this seemingly basic question:
if using a referenced library, what is the major difference/advantage of creating a vault versus a simple drag & drop copy of the aperture library onto an external HD?
Thanks,
Mike

The Finder is the strongest Mac app. It has been being tested by every Mac user and has had resources allocated to improving its stability since Mac day one. And, all of us use the Finder constantly so we are very conversant with appropriate usage. IMO if one has the discipline to go to the desktop and manually multiple backup using the Finder that is the surest kind of backup.
Personally I prefer manual non-incremental backups. It can be done with forethought after one is comfortable that everything is well with whatever it is that is being backing up.
I keep old iterations of the backup in the event that there is a critical flaw in what is being backed up. E.g. I built a Filemaker images database for an antique store. The db user was given admin control of the db against my recommendation, changed the password at some point, and then left town. Old db copies allowed me to go back to the last backup made before the password change and start over with a new user.
Drag-and-drop is good for Referenced-Masters folks in particular because Masters are not backed up by the Vault process when using a Referenced-Masters Library, so the users need to separately be backing up Masters anyway.
Most important however is to get the backup done however one does it. Other techniques like Vaults, Time Machine, etc. may assist folks who have difficulty maintaining the discipline to properly drag-and-drop.
-Allen Wicks

Vault question

Perhaps this is dumb question, but I don't use Vault nor I have the need, my Aperture library is on a second internal HD, which is automatically backed up to an external by backup software. My question is that on the splash screen Aperture says "Items not yet stored in Vault, x images", I have never set any Vault up, why am I getting this message? how do I get rid of it? To me, an indication that you're doing something wrong, I already have by back up plan , can I disable Vault completely or the message on the splash screen?

Hi, as far as I am aware you can not get rid of that message. It is just Aperture's reminder that you are not using the recommended/built-in backup solution. Then again it's not such a big deal, it only shows up for a second or two

Time Machine and File Vault question

I just completed a clean install of OS x mavericks and then used my time machine back up to restore the mac.
The whole process was confusing for many reasons and I just want to get some clarification/verification on my next actions.
When I enter time machine preferences and click select disk. It gives me two choices. One in the group Back Up Disks and One in available disks. The confusing I have is that it is the same external hd. So which should I pick if I want to keep my original time machine backups?
The other question I have is, this whole journey started with me wanting to turn on file vault. I am using a late 2012 Mac Mini updated to Mavericks came with Mountain Lion.
Should I be able to use both an encrypted time machine (external hd) and file vault?
Thanks for the help.

The difference is that do yo want to combine the backus you made before with the previous backups (group Back Up Disks) or start a whole new backup (available disks). Either option will retain the previous backups unless you overtly delete them. I would select that later to start a new set of backups.
See the following for using FileaFault with Time Machine
http://apple.stackexchange.com/questions/46833/with-file-vault-on-are-time-machi ne-backups-encrypted
http://kb.mit.edu/confluence/display/istcontrib/Enable+FileVault+(whole+disk+enc ryption)+on+Time+Machine+backup+drives+on+OS+X+10.9

Aperture 3 library file organization question

I tried searching for an answer to this question but I had no luck. Perhaps I was searching on the wrong keywords.
In the older version of Aperture, you could look in the "guts" of the library and see individual projects, but as far as I can tell with Aperture 3 you can only see files by date (i.e. by year, month etc).
My problem is that I don't currently have access to the entire library via Aperture, but I have access to all the files via the cloud (I am using Crash Plan). I need to find individual files but searching chronologically makes no sense and neither does downloading the (terabyte plus) library to use in a local copy of Aperture is not feasible.
Is there a way that I can identify specific projects within the Aperture3Lib file? Any help would be deeply appreciated.
Attached is a couple of screenshots of what Crashplan shows.

No sorry in Aperture 3 all that got turned into entries in database files. And even if you could find them it would do you no good because the only place an actual image file is located is in the Masters folder, where the files imported are kept and the Previews folder, where the previews are kept.
Also bear in mind that the Masters folder is organized by import date and time not image date and time.
As a side note you need to be very careful using an online backup service for Aperture (and iPhoto) libraries. Because of the way the # libraries there have been reports of some of the services causing libraries problems when restored.
regards

Database Vault Question on a Test Server

I have a question about database vault. Say I have Database Vault protecting the DBA from viewing table XYZ in producion. If the DBA takes a backup of the production database and clones it onto another test server is table XYZ still protected on that test server? Or because Database Vault is not running against this test server does that mean that the table is wide open now for the DBA to see? Thanks for any help on this.
Edited by: jeff81 on Nov 18, 2010 12:25 PM

findhorn wrote:
> I wondered if the mysql_query function needed a
reference to
> the database?
No, mysql_query() just needs the query. Your problem lies
with quotes in
the query itself. A couple of the values are not in quotes.
There should
also not be a comma before WHERE.
$query_updateAvailability = "UPDATE tbl_availability
SET
satStatus='".mysql_real_escape_string($_POST['satStatus'])."',
sunStatus='".mysql_real_escape_string($_POST['sunStatus'])."'
WHERE
availabilityId='".mysql_real_escape_string($_POST['availabilityId'])."'";
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of
ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Aperture library restored from vault different size to original?

Hi, I tried to share an Aperture library between two user accounts and it's messed up the permissions such that I can't use it in either account.
Shortly before trying to do this I updated the Aperture vault I keep on an external USB drive.
I've been unable to restore the permissions on the original library so I put it in another folder and asked Aperture to restore from my up to date vault.
After some time Aperture restored it's library from the vault I keep on the external drive but it's about 4GB smaller. The original aperture lib with incorrect permissions is 100.54GB and the new lib is 96.5GB.
As far as I can tell the library that has been created from the vault is up to date, so why has it shrunk by 4GB? Has the process of rewriting it in one go saved it to the disk more efficiently?
Regards,
Dave.

The vault is smaller as it doesn't store thumbnails or previews, both of which take up a noticeable amount of space.
When you use the restored library, I'd expect the thumbnails will get automatically rebuilt. The previews may as well, so eventually it will fluff back up.

Aperture 2.1.2 vault update error

ever since i have updated to this most recent release i can no longer update my vaults /___sbsstatic___/migration-images/migration-img-not-avail.png i have reformatted my drives just to make sure they have not been corrupted. i was able to get 1 clean vault update but that is it. just as some other aperture users experienced i too am getting on the splash screen, when A. is first launched a notice i have not yet backed up some files. well dah how can i if i get errors upon errors
i have searched through this forum and specific topic and have not found an answer yet. so perhaps an Aperture support person could take some time out of their busy day and help us all out in this most vexing and annoying matter.
thanks

Ha ha you are also as much a support person as any of us.
I posted it originally hslfway down page 2 of.
http://supportforums.blackberry.com/t5/BlackBerry-PlayBook/playbook-os-2-1-0-840/td-p/1888743/page/2

Aperture 2.1.1 Vault problem with external usb disk

I have just updated to 2.1.1 and now Aperture freezes every time I connect my usb external disk and try to create or update a vault. I have to force quit Aperture and remove the disk before I can use Aperture again. The only way I can create a vault is to create it on my internal disk then manually copy to the external usb. Another topic here suggested the problem is with network disks but I have a very similar problem with a local usb disk. I have tried two different disks with the same results. All my software and os is up to date.
Does anyone else have this problem?

I have a similar problem, and have a not totally satisfactory fix for my issue.
I have my photos stored on an external FW drive.
Originally I also stored my vault on the same drive.
When I started Aperture with this config then Aperture would not pass the loading screen. I would have to kill the process to quit.
If I started Aperture with the FW drive disconnected then it would launch, but I would then attach eth FW drive and have to Manage referenced files.
What has worked for me:
I have removed the vault from the FW drive and Aperture now boots quickly as 2.1 did.
I have to create the vault on the internal HD and copy to the external.

Aperture freezes when restoring vault

It's aperture 351 running on a macbook air 1.7 GHz Intel core i7 8GB 1600 MHz DDR3 Intel HD graphics 5000 and OS X 10.9.3.
Aperture library was in crashed external HD.
Aperture freezes when trying to restore library in vault.
What can I do?
Thanks.
Humberto

When I try to restore library from the original vault file I know it freezes because I can see in the "force quit" window that Aperture is "not responding".
The "not responding" does not necessarily mean that Aperture is hanging. It may be just too busy to respond.
It is hard to estimate the time it will take for the restore to complete. I have waited for about an hour to rebuild a library of 300 GB.
Where are you trying to restore the vault to? Do you have enough free disk space on the drive?
I've done that. It just doesn't work! Actually it seems to be trying to read something for hours. Don't low how long it takes to open a 320 GB library.
That is a pity. How is the drive formatted, where your vault is located? Is it formatted MacOS Extended (Journaled)? Otherwise you may have problems with pathnames and files not found.
Also, have you set the "Ignore ownership on this volume" flag for the drive with this library?
You can do this from the File > Get Info" panel for the drive.
If the file system is o.k., and also the "Ignore ownership" flag, try the library first Aid Tools on your vault with the the changed filename extension. Try to repair the permissions, the database, and to rebuild the library, in this order:
Make a copy of the vault, if you do not have a backup.
Hold down the key combination alt/option ⌥ and command ⌘ at the same time, while launching Aperture by double-clicking the vault. Keep holding down the keys firmly, until you see the First Aid panel.
Select "Repair database" from the panel. This may take a long time for a large library. Don't interrupt it.
If Repair does not suffice, do a Rebuil as well.

Aperture 3.2.1: vault questions

Similar Messages

Maybe you are looking for