8 comments

I’ve been getting that message lately with my time machine back up, but I haven’t had time to even think about it. I guess I should be worried. I’ll try the fixes. Thanks.

julianne Fishell, on June 25th, 2008 at 5:14 pm

I get that on my G5 iMac. Going to TM’s console and choosing backup now seems to solve the immediate issue but it would be nice not to have to do this manually from time to time.

Dave, on June 26th, 2008 at 12:02 am

The most common error message I get is that some random .DS_Store file can’t be found. Was I under the misapprehension that .DS_Store files should stay put once they’re created? Fortunately these errors clear up next time Time Machine runs.

I also get more serious meltdown-class errors when my TM disk is close to full. I have been solving these by deleting blocks of my backup where incremental data in unimportant to me, thus freeing up disk space until the next meltdown.

Chris Schram, on June 26th, 2008 at 2:01 am

I have been getting errors like this one, even though I go on with a hard core backup strategy, meaning copying all files and checking the total number of items and sizes via info manually. Only this way I have the chance to dig through to find those files, which cannot be copied due to non ANSI encoded name or ill permissions. By the way, I had experienced no problems with this strategy in the days of Tiger. So I rather assume that the “bug in the OS X 10.5.3″ is related to file copying mechanism rather than the fancy Time Machine backing-up.

Bora Okumusoglu, on June 26th, 2008 at 5:51 am

I get this regularly on my brand new 3GHz iMac that’s had Time Machine running since it came out of the box. So no excuses that I can think of. Today I needed a file that got messed up since yesterday lunchtime, but there were no successful backups between 9am and 3pm, even though the Mac was running constantly and should have been backed up every hour. Time Machine is fantastic, but this needs fixing…

Adam Banks, on June 26th, 2008 at 9:42 am

The article tells how to monitor Time Machine using the Console application. As an alternative to that method I’ve created a Unix alias that runs the following command in an xterm.

tail -F /private/var/log/system.log | grep backupd

This command does nothing special that Console doesn’t do. It’s just my preferred way on monitoring Time Machine.

Chris Schram, on June 26th, 2008 at 1:18 pm

[...] looks like there are quite a few other Mac users experiencing this error, [...]

Can we trust Time Machine? -- Reality Distortion: Macs, Mac OS X, and Apple stuff, on July 8th, 2008 at 12:56 am

The long thread about time machine backup failing on apple.com has been pulled. or someone got a link that work?

Yan, on July 15th, 2008 at 8:47 am