Restoring Aperture Library from Vault

Question

Level 1

0 points

Restoring Aperture Library from Vault

Hi all,

I hope someone can help. I recently had my 'Drobo' die on me as two discs failed at the same time. I also have a copy of my Aperture Library backed up in a Vault. I have carried out a 'Restore from Vault' and my new external HD shows 1.5TB of data (same as my original library). When I open Aperture, I can see all my folders and projects, but each project has no photos in it. I have tried repairing the database and rebuilding the database using the option key on start up, but I repeatedly get to approx 83-89% complete and my system hangs and I get a message that I have run out of applications memory. I then get the Spinning wheel and eventually have to reboot the iMac.

1. How can I recover my data?

2. Is there anything else I can/should do? Am I doing anything wrong?

3. Is there anyway of recvering the files seperately of the external hard drive with other data recovery software?

I am running Aperture the most uptodate version of Aperture 3.4.x, on OS X Mavericks, on a 3.4GHz i7 iMac with 12GB ram.

One point I may need to add, I was backing up to Vault when my 'Drobo' unit failed, although based on the size of the vault, I think it had finished backing up, although can not be certain.

Any help/assistance or advice would be greatfully received as I have lost my library, its parity due to two failed drives simultaneously and possibly a corrupt vault(?).

Thank you in advance for your help.

Paul W

Aperture 3, OS X Mavericks (10.9.1)

Posted on Jan 28, 2014 9:51 PM

Reply

Answer 1

Best reply

Frank Caggiano

Level 7

25,969 points

Jan 29, 2014 5:31 AM in response to Snurge

Your post raises a number of questions:

First are the originals stored as managed files or as referenced files? Second if the vault was on the Drobo and the Drobo failied where did you get the vault from that you are recovering from?

You can look in the restored library in the Masters folder to see if the originals are there. Locate the library in the Finder, right click and choose Show package contents then navigate to the Masters folder, are the originals there?

You can do the same thing with the vault, the procedure is the same.

regards

Reply

Answer 2

Jan 29, 2014 11:39 AM in response to Snurge

First, I would suggest updating to Aperture 3.5.1.

Be sure you have plenty of disk space when running the Repair. Did you check the make sure the projects do not have a search criteria set or the images possible in the trash or Rejected? If you still do not have a resolution and you've confirmed the Masters are actually in the Aperture Package, try a Rebuild of the Library.

Reply

Answer 3

Snurge Author

Level 1

0 points

Jan 29, 2014 1:16 PM in response to Frank Caggiano

Thanks Frank. Much appreciated.

To answer your queries:

1. The files are managed.

2. The vault was on a seperate hard drive to the Drobo unit; I am trying to restore the library to a new external hard drive. (i.e. No Drobo)

3. Thank you for the 'Show Package' information - I was unaware of this. Brilliant advice. I have found all of the original files in the Masters folder so that is good news. Thank you. What I have yet to locate are the files which I exported to Photoshop to work on, which are then saved back into the laibrary as Tiff files. Will these be in the Masters folder? Or another folder

Thank you so much for your advice/tips/help. You are a star.

Kind regards

Paul W

Reply

Answer 4

Snurge Author

Level 1

0 points

Jan 29, 2014 1:27 PM in response to firstlaunch

Thank you for responding Firstlaunch.

Sorry, miss information. The version I am using is 3.5.1. My mistake. At the time of writing the post Aperture was hanging and I could not check the version, I have now been able to do this.

The disk space point is a good one that I hadnt considered. The library is approx 1.5TB, the new library is on a 2TB drive. Hopefully this is sufficient? (I accept actual disk is less than this).

As an update, I returned to the Mac this morning to find Aperture open, all folders and files listed, plus the edition of 4 'Recovered' folders with files in - Images I had deleted from the original library months ago. The 'Repair database' had finished without crashing. Aperture was 'Processing' some files so I have left it to 'Do it's thing' whilst I am at work today. Will try a rebuild if still no joy.

As stated above in my reply to Frank. I can access the original files, so at least I have access to my original RAW files, I just have not gained access to my processed files yet (both processed in Aperture, and externally in Photoshop).

Fingers crossed. Will update the status later. Thank you so much for your advice and assistance. Much appreciated.

Kind regards

Paul W

Reply

Answer 5

léonie

Level 10

194,871 points

Jan 29, 2014 1:55 PM in response to Snurge

Aperture was 'Processing' some files so I have left it to 'Do it's thing' whilst I am at work today.

Paul,

it is great thatthe repair succeeded.

Check, what Aperture is processing in the Activity window. (WIndow > Show Activity). If it appears to be hanging processing a certain image or video, try to delete this item from your Aperture library. It might be corrupted.

As an update, I returned to the Mac this morning to find Aperture open, all folders and files listed, plus the edition of 4 'Recovered' folders with files in - Images I had deleted from the original library months ago. T

These folders collect "lost & found" original image files, that are in your Aperture library, but not connected to versions. If a version has lost the connection to the original, the file can show up in the "recovered" project, if the Trash cannot be emptied properly, or if an external editor saves files into the aperture library with wrong filenames. Check these folders carefully, before deleting the images.

-- Léonie

Reply

Answer 6

Jan 29, 2014 2:37 PM in response to léonie

In addition, with a library that large, the Activity Monitor might show as Aperture not reponding even though it is still working in the background. You'll have to be patient when repairing and especially rebuilding the library. The rebuild might take over a day to complete being that large. I suggest you not force quit during the Rebuild, as this might cause more issues.

Reply

Answer 7

Snurge Author

Level 1

0 points

Jan 29, 2014 8:54 PM in response to léonie

Thank you Leonie and Firstlaunch.

I have returned home this evening to find the thumbnails are loading in the 'Recovered' project. The project contains all 14K+ images; originals and images processed externally in Photoshop. What seems to be missing are all of the 'version' images processed in Aperture.

Will rebuilding the library place the images into their correct projects/folders?

Will rebuilding return the images to their edited version state?

Hesitant to carry out a rebuild if there is a chance I could lose the files completely.

If I do carry out a rebuild, shall I wait until all the images have been processed to produce the thumbnails?

Once again, thank you all for your invaluable assistance.

Kind regards

Paul W

Reply

Answer 8

léonie

Level 10

194,871 points

Jan 30, 2014 2:31 AM in response to Snurge

Will rebuilding the library place the images into their correct projects/folders?

Will rebuilding return the images to their edited version state?

This library is the restored library from your vault, correct?

What seems to be missing are all of the 'version' images processed in Aperture.

In what way "missing"? Are all your projects empty or are you seeing broken thumbnails of the missing images in the projects?

I am afraid, rebuilding will not be able to reconnect the "recovered" originals to the versions. The images are in the "Recovered" project, because Aperture does not know the link to the version.

If your missing versions are still showing thumbnails, however correpted, you could use the lift&stamp tool to transfer the adjustments from the unusuable versions to the recovered versions.

But that would be a bit daunting for 14000 recovered originals.

I'd try something different - quick and dirty emergency measure: Try to open your vault directly on the drive where it is now without restoring it.

Keep the restored library you are now having save and don't delete it.
Change the filename extension of your vault to ".aplibrary", this will turn the vault into an Aperture library and try to open it directly in Aperture by double clicking it. This needs to be done in-place, on the Drobo-attached drive where you originally created the vault. Do not move it.
Aperture will now try to open the vault as the current Aperture library and upgrade it. There is a slim chance, that the links between originals and versions will remain intact, if the vault is not restored to a different volume but repaired in-place on the original volume.

Frank, what do you think? Should Snurge first try to repair the permissions on the drive?

-- Léonie

Reply

Answer 9

Snurge Author

Level 1

0 points

Jan 30, 2014 3:09 AM in response to léonie

Hi Leonie,

Thanks for the reply.

Hope the following information helps clarify the situation.

1. Yes the library is restored from a vault (Managed Library)

2. The original, RAW files are from the library are located in one project titled 'Recovered'. The folder/project structure is detailed on the left hand side under the library tab, but all projects and folders are empty.

3. I have all the 'RAW' (NEF) files and all TIFF files imported from Photoshop during my editing stage. What I am missing are the 'versions' i.e. the RAW files with the aperture adjustments attached. So any files that I have edited in Aperture only, such as adjustments to contrast, crop, exposure - RAW adjustments have not been appended to the masters; essentially I have all my RAW/NEF masters in one big project with no adjustments applied. I have no adjustments to Lift & Stamp from.

I am happy to try your suggested 'Vault to Library' change, but should this fail, can it easily be returned to the vault file?

Once again, Thank you for your assistance.

Kind regards

Paul W

Reply

Answer 10

léonie

Level 10

194,871 points

Jan 30, 2014 3:36 AM in response to Snurge

I am happy to try your suggested 'Vault to Library' change, but should this fail, can it easily be returned to the vault file?

You can turn it back to a vault by changing the extensio back to .apvault, but trying to open it as a library can currupt it further. If you want to keep the vault like it is, copy it to a different drive for safekeeping, but the fix I suggested will only work if tried in place.

2. The original, RAW files are from the library are located in one project titled 'Recovered'. The folder/project structure is detailed on the left hand side under the library tab, but all projects and folders are empty.

Have you checked, if you have any filters set? Is the search field cleared in the Browser?

If the search filed is cleared and you still do not see any versions in the projects, ctrl-click your repaired Aperture library, use "Show PAckage Contents" from the contextual menu, and check, if the folder "Database" iside contains any versions at all:

If there are no versions, rebuilding cannot help. Then check, if your vault is containing versions.
If there are versions in your restored library, you could try rebuilding the restored library, but I have little hope, that this can restore the connection to the originals.

Reply

Answer 11

Jan 30, 2014 6:14 AM in response to Snurge

Having been away from this for a time I see a lot has happened. I've try going back all the previous posts to get up to speed but I'm afraid I'm a bit lost.

If the vault you are restoring from was not on a drive with problems and is formatted OS Extended and the drive you restored to is also without problems and formatted OS Extended then if there are problems restoring the vault the only conclusion is that the vault was never correct to begin with.

When was the vault you are restoring from last updated? Is this the only backup of the library that was on the Drobo? How was the Drobo formatted?

One point I may need to add, I was backing up to Vault when my 'Drobo' unit failed, although based on the size of the vault, I think it had finished backing up, although can not be certain.

I'm afraid this might be the kicker.

What indication did you get that the Drobo failed? When the Drobo failed what happened to Aperture? Did it just hang, did you get any messages? How did you proceed?

As the failure occurred during the Vault update it is probable that the vault was also corrupted.

Making a copy of the vault should be your first step now as whatever can be done will depend on the vault and the troubleshooting and recovery steps could make matters worst.

Once that is done doing Léonie's suggestion of changing the vault to a library and attempting to open it with Aperture is probably your best bet at this point.

regards

Reply

Answer 12

Snurge Author

Level 1

0 points

Jan 30, 2014 11:46 AM in response to léonie

Hi Leonie,

OK. So I have tried the vault to library attempt as suggested and unfortunately, no joy. I just get a blank library. This confirms my initial suspicions/fears that the vault was corrupted during the back up process.

The versions are contained within the database folder as you suggested; it appears that my library is complete, its just that the 'connections' to the files are missing. Logic may suggest a rebuild will fix this, but I am concerned about losing what I have. Is there a way of reassigning them to the masters?

Going forward, here are my thoughts; does this seem reasonable to you? Anything I have missed?

If I clone my 'new library' with all of the files, all be it in the recovered folder and keep my current library safe to one side. I then use the clone to attempt a rebuild. If successful, job done, back up and continue. If not, manually move the files into their respective projects and 'take the hit' on the images where I have carried out adjustments in Aperture; I can always re-edit if required. (Most of my images have had some work in Photoshop, therefore these are now TIFF files and are stored in the recovered Masters folder). This would return my library back to 90-95% of its original state.

Thank you once again for your help; a 90% recovery is way better than a 0% recovery and I am sure there are many people out there that have had to deal with that situation.

Kind regards

Paul W

Reply

Answer 13

Snurge Author

Level 1

0 points

Jan 30, 2014 12:04 PM in response to Frank Caggiano

Hi Frank,

Thank you for returning to my post and providing some helpful assistance.

As I stated to Leonie, my concerns were with a corrupt vault too, as I was carrying out a backup when the Drobo failed (or rather one of the internal drives failed). Running an Aperture library on the Drobo had become a painful process; very, very slow to open the library and read/write to it too. I accepted this as I could comfort myself with the fact that my library was 'safe' (Ohh the irony). Looking back, I am sure that however the Drobo system arranged its data, it was possibly not really suitable for large files and/or Aperture libraries. I was backing up to Vault because my gut told me something was not right.

Obviously I do not want to turn this discussion into a negative feedback item on Drobo. Separately to the recovery through Vault, I am also liaising with Drobo to try and recover the original library from the device itself; although this is turning out to be a slow, expensive process with a low risk of total recovery; thus this discussion/recovery route.

What I am concerned about is that the internal drives in the Drobo were less than 18months; of the three installed one failed completely and another is about to fail according to the Drobo diagnostics report. It appears that the Drobo may 'eat' drives.

I have posted my thoughts on going forward in the post above; if you have any further comments, these would be gratefully received, if not, thank you so much for taking the time to assist me with this issue. I am extremely grateful to you and all who have helped.

Kind regards

Paul W

Reply

Answer 14

edwaant

Level 1

0 points

Jan 30, 2014 2:08 PM in response to léonie

Hello léonie,

I've noticed your expertise with Aperture. Here's hoping that you can help me. Aperture 3.5.1 runs quite sluggishly on both my iMAC 27" i7 8GB (late 2009) and MBA 13" i7 4GB (mid 2011). I have an ad hoc setup with the *.aplibrary (650GB) completely on an external hd. I've tried to connect this external hd to an Apple Airport Extreme, but that has proved unsuccessful (although I am eyeing the WD MyCloud 3TB if you have any reviews of its ability to host .aplibrary packages). So instead I have copied the .aplibrary file to two more external hds which I attach to each machine.

I noticed advice that you've given about maintaining a library on the Mac while moving a reference library to the external hd. If I understand this correctly, I would have an active library that opens on my Mac which lives on my Mac hd. I would also have a library on the external hd that would be the original photos. Right now, I don't think I have a .aplibrary on my Mac's hd, only on the external hd.

How do I create a library on my Mac's hd (especially on the mba ssd) that will access all the photos (650GB) but keep the photos on the external HD?

Thanks so much. I apologize in advance if I am describing this inadequately. I'll provide more detail if needed.

ED

Reply

Answer 15

léonie

Level 10

194,871 points

Jan 30, 2014 2:19 PM in response to edwaant

How do I create a library on my Mac's hd (especially on the mba ssd) that will access all the photos (650GB) but keep the photos on the external HD?

ED, what you need to to is making the original image files referenced.

Read this page in the User Manual: Aperture 3 User Manual: Working with Referenced Images

That will explain the basics of using a referenced library, and then please post a new question in a separate thread. We like to keep the discussions restricted to one topic. That makes it easier to read the thread.

Switching between unrelated questions can be very confusing.

Reply