#!/bin/blog

February 16, 2008

MacOS 10.5.2 kills Time Machine

Filed under: Software — Tags: , , — martin @ 9:09 am

I strongly advise everyone who has upgraded to “Leopard” 10.5.2 to make really sure that Time Machine is still working. My log is full of weird backupd messages after an entire night with the TM drive connected. Also, the Time Machine control panel still shows the last backup as having been done on Feb. 10, which was the last time when I had my laptop connected to the external drive before I came home again yesterday:

# grep backupd /var/log/system.log
Feb 15 23:31:29 macbook /System/Library/CoreServices/backupd[2061]: Backup requested by user
Feb 15 23:31:29 macbook /System/Library/CoreServices/backupd[2061]: Starting standard backup
Feb 15 23:31:29 macbook /System/Library/CoreServices/backupd[2061]: Backing up to: /Volumes/WD MyBook/Backups.backupdb
Feb 15 23:31:29 macbook /System/Library/CoreServices/backupd[2061]: Event store UUIDs don't match for volume: Mac HD
Feb 15 23:31:29 macbook /System/Library/CoreServices/backupd[2061]: Forcing deep traversal on source: "Mac HD" (mount: '/' fsUUID: ********-****-****-****-************ eventDBUUID: ********-****-****-****-************), {1, 1, 0, 1}
Feb 15 23:31:29 macbook /System/Library/CoreServices/backupd[2061]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonForceDeepBackup|
Feb 16 00:00:59 macbook /System/Library/CoreServices/backupd[2061]: No pre-backup thinning needed: 2.24 GB requested (including padding), 20.02 GB available
Feb 16 00:00:59 macbook /System/Library/CoreServices/backupd[2061]: Waiting for index to be ready (915 > 0)
Feb 16 00:01:29 macbook /System/Library/CoreServices/backupd[2061]: Waiting for index to be ready (915 > 0)
(Last message repeated for hours until I disable Time Machine.)

This is NOT nice, Apple. My previous backup solution, SuperDuper!, had to take a lot of criticism from users while it took the vendor more than three months to come up with a version that was thoroughly tested on Leopard. On the other hand, you ship a patch-level release of your very own backup software that goes into some sort of endless loop without noticing and without displaying a warning about it.

The issue is starting to pop up on the support forums as well:

My friend K. used to say that Apple has invented backups for the masses with Time Machine and I agreed. I would like to extend this statement today and add that they have in fact invented unusable backups for the masses.

I don’t care what the reasons are. I don’t want to know how to fix it. I don’t care if it’s free or not. Things like this must not happen. The Time Machine experiment has failed for me. My trust in Time Machine has been wiped out.

I’m back to manual runs of SuperDuper!, which won’t give me point-in-time restores, but a working and bootable single backup generation. Which is just about everything I really need.

Advertisements

Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: