Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

10.5.3 and new Time Machine error

I had this issue and the solution for me was to rebuild the backup by reformatting the Time Machine disk and then letting Time Machine create a new backup. All that mattered to me was to have one latest backup.
 
mreg376 said:
Thanks, but that's not really a satisfactory solution to an Apple-induced bug. Apple will have to do better.
Click to expand...

Agreed. That's not even close to acceptable. Since when do you have to reinstall the entire OS to fix a BACKUP SOLUTION?!?

Apple needs to figured this stuff out.

Reinstalling or wiping the entire backups should not be an option!

-Kevin
 
OK I think this is a new one.....

iMac backs up fine with Time Machine connected via ethernet to my timecapsule.

Mac Air (since 10.5.3) goes into Preparing Back UP and then just stays there - doesn't actually start the back up.

I've tried switching TM off, changing disk, rebooting Time Capsule but nothing :mad:
 
time machine error

another forum put me onthe right track to solve this for me. remove intego virus software and dont forget to also remove netupdate as well as the preferences. backups ok now:rolleyes::rolleyes:
 
ebel3003 said:
I had this issue and the solution for me was to rebuild the backup by reformatting the Time Machine disk and then letting Time Machine create a new backup. All that mattered to me was to have one latest backup.
Click to expand...

Did this. It worked for a few days, now it's happening again.
 
Same problem

I am having the same problem (error -43, then error 11) using an *internal* WD drive - the one shipped/installed in my Mac Pro.

Nothing has changed except updating to 10.5.3 so I, like others in the thread, suspect it's an issue with the latest version.
 
Sorry, I can't add anything more helpful here than another point on the graph: I've had this error about five times since upgrading to 10.5.3. 10.5.4 hasn't made things any better or any worse. Never saw it once before 10.5.3.

Thanks for posting, everyone, at least I know I'm not alone. I really don't like getting mysterious error messages from my backups!
 
I had the same problems on my macbook. Every time TM went to do a back up, it failed and said it was unable to copy.

I started a backup manually, and when the backup drive mounted, I went in and deleted the last couple backups, and the file that was the current backup in progress. Turned TM off then back on, and started another backup, and it works fine now.
 
davidwarren said:
I had the same problems on my macbook. Every time TM went to do a back up, it failed and said it was unable to copy.

I started a backup manually, and when the backup drive mounted, I went in and deleted the last couple backups, and the file that was the current backup in progress. Turned TM off then back on, and started another backup, and it works fine now.
Click to expand...

Don't worry -- it'll happen again.
 
I came across this recently, there's now a dialog box on my screen in the morning reporting that Time machine backup failed. In scanning the console log files I found that the error most often occurs when TM is backing up a file that is being synchronised with another system--in my case my firefox book marks file using foxmarks or my keychain file using mobileme sync.

8/19/08 8:14:02 PM /System/Library/CoreServices/backupd[14498] Error: (-43) copying /Users/XXXXl/Library/Keychains/.fl4E0F697A to /Volumes/Time Machine/Backups.backupdb/XXXZ’s MBP17/2008-08-19-201359.inProgress/2483E244-A53C-4EF3-A13A-9C85AACDE6FC/Macintosh HD/Users/XXXX/Library/Keychains.

the log file shows that subsequent backups ran fine however. This seems like TM is inelegantly handling locked files--the specific problem with errant file should be dumped to a log and the whole backup should not fail....
 
Just chiming in with more info. It is happening to me with a brand new HD, three days old. Running 10.5.4 and it happened at least once a week with the previous HD as well. At some point in the past it was NOT happening, but I did not note the exact time it started. Seems to be the same problem everyone else is having.

With persistent problems like this one, I'm not exactly thrilled with my Mac since "switching", but I think the overall experience is probably better than Windows. I wish I could be more positive and say "I love it", but with this, the Mobile Me disaster, and other problems I just can't say that yet :(
 
todd2000 said:
Meh! I consider this a minor problem. So you miss one hourly backup a week, or even a day, not a huge deal. As long as the subsequent backups work Im not too concerned.
Click to expand...

For the most part, Time Machine has been reliable. The issue for me is that a backup is supposed to be a form of fault tolerance. When your employed solution to fault tolerance is failing, that isn't exactly reassuring. I've been seeing this error less and less often, though.
 
Same Problem, but I Fixed It

I don't know if anybody is still looking at this thread, but I had the same problem that so many people have been describing. However, I was able to solve it rather easily. I turned off Time Machine, mounted the backup sparse bundle, deleted the .inProgress file, ejected the bundle, turned Time Machine back on, and forced an update. Don't be surprised if it takes a long time for the file to delete. Granted, I haven't tested this in the long run, but it seems to have done away with my issue.
 
Same problem - solved it

carbonizer said:
I don't know if anybody is still looking at this thread, but I had the same problem that so many people have been describing. However, I was able to solve it rather easily. I turned off Time Machine, mounted the backup sparse bundle, deleted the .inProgress file, ejected the bundle, turned Time Machine back on, and forced an update. Don't be surprised if it takes a long time for the file to delete. Granted, I haven't tested this in the long run, but it seems to have done away with my issue.
Click to expand...

I had the same trouble. Checking the local hdd, removing the 'corrupted files'. Detaching and attaching the backup volume. It took me hours.

In the end this was my solution:
1. on the backup volume, backups.backupd, "your computer name" I deleted "In Progress" or "Latest"
2. In terminal type: sudo grep backupd /var/log/system.log to find the file(s)creating the error. For me it was iMovie.app
3. delete all files in TM giving errors in the log (http://www.tech-recipes.com/rx/2655/leopard_time_machine_delete_files_folders_from_backup/)

good luck
 
I'm still having this problem in 10.6.1... I really think this is unacceptable from such a high quality company like Apple... I fixed it by removing my entire backup...
 
vikking said:
I'm still having this problem in 10.6.1... I really think this is unacceptable from such a high quality company like Apple... I fixed it by removing my entire backup...
Click to expand...

Did you try Repair Disk?

You'll likely get better help on the Apple forums. There's a Time Machine forum in both the Leopard and Snow Leopard sections. And there are two User Tips at the top of each with many answers and fixes.
 
Beetlebinkie said:
In the end this was my solution:
1. on the backup volume, backups.backupd, "your computer name" I deleted "In Progress" or "Latest"
2. In terminal type: sudo grep backupd /var/log/system.log to find the file(s)creating the error. For me it was iMovie.app
3. delete all files in TM giving errors in the log (http://www.tech-recipes.com/rx/2655/leopard_time_machine_delete_files_folders_from_backup/)
Click to expand...

Okay, so I did this, but deleted both today’s InProgress and Latest. Turned TM off, let it completely wind down, then turned it on, and started a backup.

That was two hours ago. It’s still in “Prepping” mode, according to TM prefs. Is that normal, or did I just screw something up?

This isn’t my first TM/TC problem, so forgive me if my nerves appear a bit thin.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back