“Time Machine may back up the entire Aperture Library on each run”. No, really?

by moose

According to this tech note from Apple’s KB,

Time Machine may back up the entire Aperture Library on each run:
This can happen if the Aperture library is included in Time Machine backups and a backup occurs while Aperture is running. In this situtation, Time Machine excludes the Aperture library from a backup while the application is running, but backs up the entire library 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 released Mac OS X 10.5.0, the only “fix” they offer for this is to

Avoid performing backups or restores while Aperture is running.

Wow, thanks Apple, that’s waaaaay better than before when it was advised to

set Time Machine to exclude the Aperture Library from automatic backups

C’mon on Apple, you control the hardware, the OS and the software, and you can’t bloody make them work together? Or is everybody at Cupertino too afraid to explain the whole cluster-fuck to teh Steve?

Share this: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Reddit

 

One Response to ““Time Machine may back up the entire Aperture Library on each run”. No, really?”

  1. HardMac’s Blog » Blog Archive » MacOSX 10.5.3 update fixes Time Machine backup of Aperture’s Library Says:

    [...] a complete copy of your Aperture Library. yes, the WHOLE Library, not just the changed files… like I explained in this post (and as Apple explained in a KBase [...]

Leave a Reply