I use ChronoSync to back up my iPhoto library (along with the rest of my home directory) to an external hard drive. I also use ChronoSync to sync my iPhoto library between my PowerMac and my MacBook Pro. It's been a great solution and I've been totally happy with it until yesterday.
The new iPhoto '08 changed the way the photo library is stored on disk. Instead of a simple "iPhoto Library" folder in the Pictures folder, in iLife '08 Apple has decided to change it to an "iPhoto Library" package. Similar to the way an application package work, I suppose. It's still a directory in reality -- you can grope around in it with Terminal and you can "Show Package Contents" from the right-click menu. However, ChronoSync now sees it as a single file instead of a directory containing individual files. This means that the sync process now has to re-send the entire library blob (mine is 17GB, I'm sure others have even larger libraries) instead of just sending the new and changed image files. This makes syncing take much longer, and actually broke syncing entirely to my laptop because I don't have 17GB free for the temporary file to be stored while the transfer is in process.
I haven't tested with using rsync from Terminal, which might dodge the problem, but even if that works it would be a real shame to have to stop using ChronoSync. Hopefully Apple changes this back to the old behavior or perhaps the ChronoSync folks can come up with a way for ChronoSync to more elegantly handle the fake OS X package "files" when Syncing.
Anyone else have a good solution to this one?
The new iPhoto '08 changed the way the photo library is stored on disk. Instead of a simple "iPhoto Library" folder in the Pictures folder, in iLife '08 Apple has decided to change it to an "iPhoto Library" package. Similar to the way an application package work, I suppose. It's still a directory in reality -- you can grope around in it with Terminal and you can "Show Package Contents" from the right-click menu. However, ChronoSync now sees it as a single file instead of a directory containing individual files. This means that the sync process now has to re-send the entire library blob (mine is 17GB, I'm sure others have even larger libraries) instead of just sending the new and changed image files. This makes syncing take much longer, and actually broke syncing entirely to my laptop because I don't have 17GB free for the temporary file to be stored while the transfer is in process.
I haven't tested with using rsync from Terminal, which might dodge the problem, but even if that works it would be a real shame to have to stop using ChronoSync. Hopefully Apple changes this back to the old behavior or perhaps the ChronoSync folks can come up with a way for ChronoSync to more elegantly handle the fake OS X package "files" when Syncing.
Anyone else have a good solution to this one?