Time Machine will only do proper backups if Aperture is not running
by moose
So, according to this tech note on Apple’s knowledgebase, you can now safely use Time Machine to back up your Aperture Library (before the OSX 10.5.2 update, it was recommended to exclude the Library from the Time Machine backups for fear of giant asteroids destroying your house or something.
I just upgraded my laptop to Leopard (better late than never), so I let Time Machine do its thing and everything went well. Then I noticed something funny: the backups were constatnly deffered, and actually almost never happened. Hmmm. Then I noticed that I had Aperture open in a separate Space and had completely forgotten about it. I quit Aperture and, voilà, next time the backup went fine. I relaunched Aperture, asked for a backup and nothing happened, well, actually, something did happen, but it is weird. The console log was showing this:
27/02/08 13:16:41 /System/Library/CoreServices/backupd[4062] No pre-backup thinning needed: 1.04 GB requested (including padding), 12.78 GB available
So TM was supposed to backup 1.04GB, but the Time Machine menulet was showing that only 133.7MB were to be backed up. It seems that the Aperture Library is not backed up if Aperture is running.
Conclusion: if you want Time Machine to work correctly, it’s better to quit Aperture before doing a backup. Jeez, can’t Apple fix their own software? I thought the whole thing was about tight integration blah blah blah…




March 15th, 2008 at 15:44 CET
[...] once Aperture quits, rather than just the changes since the previous backup. As I pointed out in a previous post, this is a real pain in the lens. At least Apple is acknowledging the problem, but as when they [...]