It was working last night. Now it says backup failed everytime
whats going on?
ive tried permisions, ejecting, restart, etc
any ideas?
whats going on?
ive tried permisions, ejecting, restart, etc
any ideas?
This has happened to me too. It has happened when I installed Microsoft Office 2008, and when I updated Java. I think what happens is the installer messes up permissions or something, and Time Machine encounters something it can't copy. Either way, the way to fix it is to basically exclude the files that are giving you problems from being backed up.
After getting a Time Machine backup error, use Terminal and type in
cat /var/log/system.log
and you should see stuff like "Error 32 : /folder/file.blah could not be backed up", then just exclude that folder.
This is just a "cover up" fix, obviously, if someone could really fix this that would be great.
Time machine can be very temperamental. I have had a problem every time I take my MBP out of range and the scheduled backup starts and fails. Every time it tries to back up after that, I will get an error.
Solution (for me, and hopefully for you too): Go into Time Machine Preferences, select Change Disk, reselect the volume that is used for your backups. There have been times that I had to just go through the whole Set Up Time Capsule procedure, but not nearly as frequently.
Hope this helps.
Wow, hopefully someone around here will be able to help you.thanks, sadly it doesnt
Wow, hopefully someone around here will be able to help you.
Dumb question... have you googled it? (WWW, not MR)
TM is probably picky about the configuration and doesn't like it when it expects 3 and gets 2. I'm sure I'm over-simplifying things here, and um, I haven't a clue what I'm talking about. Good luck.yea i have or tried to lol
i did notice this though
i took a hdd out (have 3 in my tower) and when i take a hdd out, that is when it no longer will backup to time machine
when i put it back in, it backs up. any idea?
the hdd i remove is not the primarty or time machine drive
Again, not to over simplify things but you aren't taking out the drive that has the time machine files on it are you?
Repair your hard drive. I had this happen to me more and more as my HDD was beginning to fail.
I'm not trying to scare you, just saying what I went through. And the drive never actually failed, I just got so tired of some weird crap going on that I went and had the thing replaced.
nope my drives are
1: 500 gig primary
2: 1.5TB time machine drive
3: 80 gig laptop drive
I have tm backing 1 up to 2. the drive I took out is 3 and once i took it out, TM fails backup. when i put it back in, TM works again
Ill try it though the TM drive is like a month old
Usually when a drive fails, it will fail early. To me that doesn't sound like the issue though. Can you confirm the 80GB drive was not being backed up to the 1.5TB drive?
Ill try it though the TM drive is like a month old
If you have this issue, there is a fix for it. I found it with a quick Google search, as I was having this issue myself. What you need to do is delete the .inProgress file created by Time Machine on your backup drive. Initiate a backup manually, and it should start working again.
Very big of you to post the resolution. Good for you!
but I cancelled it because I could see this in the logStarting standard backup
Backing up to: /Volumes/My Book/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 298.2 GB excluded items size: 252 KB for volume Macintosh HD
No pre-backup thinning needed: 358.53 GB requested (including padding), 929.83 GB available
CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
Copied 6196 files (2.5 GB) from volume Macintosh HD.
Backup canceled.
For the record all this seemed to come about after Safari update last week to v4.0.2 Coincidence ?? Maybe but.....Event store UUIDs don't match for volume: Macintosh HD
I could go get Super duper but that doesn't address the current problem which is underlying. Up to now I have had Safari 4.0.2 hang which freezes the computer, dock won't pop up nothing else will open, even force quit is sluggish until Safari has relinquished grip. Activity monitor doesn't show anything grabbing too much processor use.RE:
"Does anyone have a solution to this?"
Yes.
1. Turn OFF Time Machine.
2. Get ahold of SuperDuper
3. Use SuperDuper to erase your backup drive and create a new clone of your internal drive on the backup.
4. Do a daily "incremental backup" to the external (again, with SuperDuper)
Your backup problems will be solved. AND, you will have something that Time Machine cannot give you - a fully bootable backup of your internal drive. You can now boot from the backup and run maintenence or recovery on the internal if the need arises. You CAN'T do that with a TM "backup".
In 22 years of Mac'ing, one truth I've discovered: one needs a fully-bootable SECOND drive in addition to one's primary drive. It makes EVERYthing easier.
Apple would have done much better by buying SuperDuper outright, and including it with every Mac sold, rather than Time Machine. As of late, I seem to be reading an increasing number of postings stating that either:
1. They can't restore from a TM backup, or,
2. TM seems to be corrupting the drives it uses, or other problems simply maintaining a TM backup drive.
Time Machine is clunky at best, and an unreliable backup solution at worst.
SuperDuper _works_.
- John
After getting a Time Machine backup error, use Terminal and type in
cat /var/log/system.log
and you should see stuff like "Error 32 : /folder/file.blah could not be backed up", then just exclude that folder.
This is just a "cover up" fix, obviously, if someone could really fix this that would be great.