Got a tip for us? Share it...

Time Machine + Aperture Bug

Aperture users that have upgraded to Mac OS 10.5 Leopard should beware when using Time Machine. According to an Apple support document, having Time Machine run a backup while an Aperture session is in progress could result in inconsistencies in the Aperture database.

Apple recommends that Aperture users set Time Machine to perform manual backups. Apple also says that they will be updating the support document as more information becomes available, perhaps indicating that they are working on a resolution to the issue.

Top Rated Comments

(View all)

56 months ago
why do they have to push the OS out before its ready

I would much prefer 2 more weeks of bug killing then to have it 2 weeks early and struggle with the os being buggy

what makes this worse is thats its a problem between two apple products..
Rating: 0 Positives / 0 Negatives
56 months ago
Not so clever Apple..........
Rating: 0 Positives / 0 Negatives
56 months ago
I keep getting this feeling too. I mean, all up it's a pretty good effort considering exactly how much work has to go into an OS, but I can't help but think that a little more foresight should have gone into compatibility. Maybe putting the betas into certain user's hands and not just developers who may only use them to test their own apps??
Rating: 0 Positives / 0 Negatives
56 months ago

why do they have to push the OS out before its ready

I would much prefer 2 more weeks of bug killing then to have it 2 weeks early and struggle with the os being buggy

what makes this worse is thats its a problem between two apple products..


I agree the problem is pretty stupid considering its an apple product-product issue. However even if they delayed it two more weeks there would still be calls for it to have been delayed a further two weeks - they have to ship it sometime! Lets be glad apple make regular, useful updates to OSX.
Rating: 0 Positives / 0 Negatives
56 months ago
It's too bad that this glitch wasn't caught in time.

The support document does not make clear whether the "inconsistencies in the Aperture database" would be in the original copy or only in the backup copies. I assume that it's only in the backup copies. If that's the case, it seems to me that it would not be necessary to limit Time Machine to manual backups as long as you never use Time Machine to restore the Aperture database. More importantly, the distinction makes a big difference to users for whom 'inconsistencies" have already occurred.
Rating: 0 Positives / 0 Negatives
56 months ago
I have been patient with Leopard and understanding but this just pissed me the **** off. This is ********. :mad:
Rating: 0 Positives / 0 Negatives
56 months ago

If that's the case, it seems to me that it would not be necessary to limit Time Machine to manual backups as long as you never use Time Machine to restore the Aperture database.


Not looked into TM much yet, but I assume you could exclude the Aperture DB from TM backups.

Anyone here able to knock up an automator script that switches backup off, starts Aperture then waits for Aperture to exit before re-enabling TM? (Ive never figured out Automator :o )
Rating: 0 Positives / 0 Negatives
56 months ago
Come on Apple... How old is the issue of open files & databases while a backup is running....? :rolleyes:
Rating: 0 Positives / 0 Negatives
56 months ago
has anyone actually had an issue occur because of this?
Rating: 0 Positives / 0 Negatives
56 months ago
Hopefully there are some pretty specific conditions that have to exist for there to be a problem. I'm pretty sure I've already been using Aperture while a TM backup ran, so it'd be nice to know what the actual symptoms are. Hopefully there some way to check the consistency of the Aperture database.

It seems like the easier workaround for the moment is to turn off TM when you're going to use Aperture instead of making TM totally manual. I guess it's just a matter of remembering you need to do it.
Rating: 0 Positives / 0 Negatives

[ Read All Comments ]