Aperture 3 Libraries - Backup options

[RichHobson]

So is my thinking on this correct?

I currently export final jpg's from aperture for clients then save these as a backup. I also backup the complete Aperture library. In essence I'm backing up the same thing twice.

My thinking now is that as a project in Aperture can be exported as a new library I don't need to save the exported jpg's, simply export the project as a new library (do the usual off site, multiple backups etc)

Having the library should mean I can open it any time in the future and re-export any files I need. All the formatting etc should be in the library with the files.

This should keep my main aperture library spick and span as well as meaning I onlly need to archive a library rather than lots of different elements of a project.

Am I on the right track here?

 

[Jim.R]

Is there any reason you're not using Vaults? You can create multiple vaults on seperate harddisks, Aperture prompts you when they're getting out of date, and it maintains a complete backup of your library.

This is a two action solution: plug in the external drive, click update. Job done.
This generally means it gets done more often as it's simple and quick. Having to find time to export projects, check the contents, copy the folder onto multiple disks etc... is a bit of a ballache and likely to get skipped if time is short.

And yes, backing up the exported JPEGs is a waste of disk space since they can be re-created at will from the masters

EDIT - I also believe that TimeMachine will backup only the changes made to an Aperture library, rather then the whole library every time, meaning that is another automatic backup solution available to you.

 

[RichHobson]

Thanks for confirming a couple of things for me.

With regards to vaults I've been a bit wary because of lack of understanding of how they work I guess. I'll have to look into them more. I wasn't aware I could move items to a vault and not have them in the main library. That would make life quite easy.

Process would be

1. Move to vault on connected HDD
2. Backup (copy) vault drive to another HDD
3. Move backup of vault drive offsite.

Leaves Aperture library free and clear.

If I need anything on the vault drive I can simply open it and restore it?

Am i correct in this assumption.

 

[Jim.R]

I wasn't aware I could move items to a vault and not have them in the main library. That would make life quite easy.

Ah, I'm not sure you can do that. AFAIK, a vault is a copy of your whole library and it's not possible to exclude items.

Leaves Aperture library free and clear.

What's your aim in exporting projects from the library and leaving it "free and clear"?
It's fairly easy to keep things organised, projects can be moved into folders, sub-folder etc... once you're done with them.
If you're aiming to make things easy to find (eg. one library per assignment or client) then searching can be done much more easily by effective keywording of images. This is really quick to do with either import presets or the lift/stamp tool.

If I need anything on the vault drive I can simply open it and restore it?

A vault is a backup of an existing library. If you lose your library, you create a new one and restore the contents of the Vault into it. Although, I suppose there's no reason you can't delete the library once it's been backed up to a vault.

 

[RichHobson]

Ah, I get it.

The reason for removing from the main library is that at the current rate of growth it soon exceed 1TB. Finding stuff is easy but keeping it trim should help with performance. Archiving old projects - say over 6 months old should keep it manageable.