Time machine error failed

The backup disk image could not be mounted.
Got my time capsule and configured to work wirelessly. Then tried to backup my hard drive. the problems begin. Stalled. I changed the sleep settings to never. Hoped that would help. IT took 2 days to get to 391.6 GB of 463.8 GB available then it failed. Mac won't recognize any data nothing shows in the oldest backup and latest backup area. Can you erase the data already entered and start over or am i minus the disk space. Should I do the initial backup with ethernet cable. I''m lost as my main reason for getting the time capsule was for mindless backup. Please help.

Can you erase the data already entered and start over or am i minus the disk space. Should I do the initial backup with ethernet cable.
Yes and Yes. (Turn off TM and erase sparsebundle image, then start over)

Similar Messages

Time machine backup fails; error creating folder. Western Digital drive requires password which is perhaps/likely the issue. I can't eliminate the password/encryption.

Time Machine backup fails on new WD external drive (My Passport Studio); error creating folder (after several hours of Time Machine apparently working).
Background: I purchased a Western Digital drive from an Apple Store to use for Time Machine backup. I followed the Western Digital instructions that came with the drive for Mac. I didn't get the Time Machine prompt which the instructions indicated I would receive--namely to select whether I want to encrypt my Time Macine backups. (I already have a Time Machine backup I use at another location, which is perhaps why I didn't receive a prompt.)
I decided to install the Western Digital utilities and security software that comes on the disk--with a view to potentially encrypting the disk (since I still wanted to have an encrypted backup since I was mobile). I forgot that (from experience 2-years previous) that I shouldn't install Western Digital software because it just makes life really complicated.
I tried several times to do a Time Machine backup with failures each time (error creating the backup folder). I tried to get help from WD but I don't think the technicians were following what my issue was. Potentially I was not helpful in explaining it. I deleted the WD applications from my system after the first contact with WD. However the problem persisted--I still had an encrypted hard drive. After three phone sessions with three different WD techs I still could not get a solution. (By the second call I was not at all interested in having an encrypted drive--I just wanted to format and restore the drive to an unencrypted state so that I could have SOME kind of Time Machine backup.)
I still don't have a solution--either to get Time Machine working with the WD encryption/password on the drive, or to remove the encryption so I can backup. Right now my options are to return the drive to the Apple Store -- or get a return authorization from WD. Seems crazy since the drive is fine and I have the working password.

Never install "helpful software" provided by WD and Seagate (or any HD mfg.)
All such stuff is fluff and nonsense that interferes with normal HD operation.
Always when you buy a new HD, format it for Mac and then use it to TM backup or clone a HD, or archive data.
Less is more on HD new out of box. A "blank brick", no fluff and cotton candy software

First Time Capsule Backup Failed - Time Machine Error

I bought my Time Capsule yesterday because I needed to backup my MacBook (which I bought 6 months ago). My plan was to backup the MacBook to the TC and then do an Erase and Install of my MacBook because of problems I'm having with the MacBook (it constantly hangs for a minute or more - sometimes up to 20 times a day). I thought an erase and install might fix the problem.
After setting up the Time Capsule and connecting it to the MacBook with a Cat 6 ethernet cable for the first backup I went to bed. I noticed that, when the backup started, it was taking approximately 5 minutes to backup the first Gb of data. As TC noted there was 80GB to backup I assumed this would take 6 or 7 hours to complete.
This morning when I checked the MacBook I discovered a message on the screen of my MacBook as follows -
Time Machine Error
Unable to complete bacup. An error occurred while copying files to the backup volume.
Nothing else! When I check the Time Machine in Finder, under Data there is the following -
Patricia Henwood’s MacBook_002332b6d076.sparsebundle and this is 50.82GB.
Can anyone suggest what I should do?
I bought the TC yesterday because all my other backup drives are Firewire and, of course, the MacBook doesn't have a Firewire port.
Should I just 'give up'? The MacBook is covered by Apple Care (and anyhow, even if it weren't it's only 6 months old so, presumably, it's still covered by Apple warranty). I understand from the salesman where I bought my TC that it, too, is covered by my Apple Care for the MacBook because I bought it to use with the MacBook.
Would the simplest solution be to make an appointment to take the MacBook and the TC to the genius bar and see if they can help?

Hi dealbata, happy to hear that yours is now up and running. My fourth TC backup attempt last night failed yet again (at 50.8GB) - I read in a previous thread (which I can no longer find but which was more than 5 pages long and went back to 2007) about many people who have had the message
Time Machine Error
Unable to complete backup. An error occurred while copying files to the backup volume.
From that thread, 'famouswolf' posted a solution which involved checking the system.log using Console.app (Utilities folder). In his case (and in mine) the problem was caused by corrupted files in iPhoto. The solution was to actually delete the files (all those that had an ERROR (-36) message next to them in the system.log. To delete them you have to locate them in your iPhoto Library file and delete them in the Finder. As you can imagine, this is a long and tedious process (I have over 8000 images in my iPhoto library) - frankly, I've already wasted two days on this - and the TC was bought so I could back up my MacBook and then discover what the REAL problem is with my MacBook (it hangs and/or crashes between 10 and 20 times a day :-((
So, I've bitten the bullet and re-partitioned my MacBook's hard drive and done a fresh install of OS X and the applications that came on the install DVD. I've then run Software Updater until everything is up to date and I am now in the course of doing a backup of the MacBook to the TC of the 'bare bones' of my system - it's only 14.3GB so I hoping it will work. Then I'll copy across what I need from my iMac and hope that tonight TC will backup everything.
Here's hoping!
Cheers
Tricia

Time Machine Backup Fails With Error 36 on Music Folder?

Hi. I've been having backup errors since a clean install of Leopard (and immediate upgrade to 10.5.2). I keep getting a pop up that says time machine has failed. I started isolating my user folders (Pictures, Downloads, Music), and turns out its my iTunes Music folder that has files that are causing Time Machine to fail. If I exclude Music, the backup works perfectly. If I include it, it recognizes that it has 19 GB more to backup, but then I get the following errors (this is just a subsection):
Feb 24 01:38:50 jordan-martons-imac /usr/sbin/ocspd[592]: starting
Feb 24 01:40:22 jordan-martons-imac kernel[0]: disk0s2: 0xe0030005 (UNDEFINED).
Feb 24 01:40:22 jordan-martons-imac kernel[0]:
Feb 24 01:40:22: --- last message repeated 1 time ---
Feb 24 01:40:22 jordan-martons-imac /System/Library/CoreServices/backupd[204]: Error: (-36) copying /Users/jordanmarton/Music/iTunes/iTunes Music/Maroon 5/Songs About Jane/12 Sweetest Goodbye.mp3 to (null)
Feb 24 01:40:42 jordan-martons-imac kernel[0]: disk0s2: 0xe0030005 (UNDEFINED).
Feb 24 01:40:42 jordan-martons-imac kernel[0]:
Feb 24 01:40:54: --- last message repeated 1 time ---
Feb 24 01:40:44 jordan-martons-imac /System/Library/CoreServices/backupd[204]: Error: (-36) copying /Users/jordanmarton/Music/iTunes/iTunes Music/Martin Page/In the House of Stone & Light/01 In the House of Stone and Light.mp3 to (null)
Any idea what is going on?

Hi. I've been having backup errors since a clean install of Leopard (and immediate upgrade to 10.5.2). I keep getting a pop up that says time machine has failed. I started isolating my user folders (Pictures, Downloads, Music), and turns out its my iTunes Music folder that has files that are causing Time Machine to fail. If I exclude Music, the backup works perfectly. If I include it, it recognizes that it has 19 GB more to backup, but then I get the following errors (this is just a subsection):
Feb 24 01:38:50 jordan-martons-imac /usr/sbin/ocspd[592]: starting
Feb 24 01:40:22 jordan-martons-imac kernel[0]: disk0s2: 0xe0030005 (UNDEFINED).
Feb 24 01:40:22 jordan-martons-imac kernel[0]:
Feb 24 01:40:22: --- last message repeated 1 time ---
Feb 24 01:40:22 jordan-martons-imac /System/Library/CoreServices/backupd[204]: Error: (-36) copying /Users/jordanmarton/Music/iTunes/iTunes Music/Maroon 5/Songs About Jane/12 Sweetest Goodbye.mp3 to (null)
Feb 24 01:40:42 jordan-martons-imac kernel[0]: disk0s2: 0xe0030005 (UNDEFINED).
Feb 24 01:40:42 jordan-martons-imac kernel[0]:
Feb 24 01:40:54: --- last message repeated 1 time ---
Feb 24 01:40:44 jordan-martons-imac /System/Library/CoreServices/backupd[204]: Error: (-36) copying /Users/jordanmarton/Music/iTunes/iTunes Music/Martin Page/In the House of Stone & Light/01 In the House of Stone and Light.mp3 to (null)
Any idea what is going on?

Time Machine Backup Failed - Copy stage failed with error:11

My TM backups started to fail on a Mac Book Pro running 10.5.8 a few weeks ago with the 'Copy stage failed with error:11' message. It seemed to happen after coming out of hibernation from clamshelling the laptop.
This happened a few times before when I had initially set TM up so to 'fix' it I just blew away the TM backups and started fresh. I would rather not do that this time as I have accumulated 3 months worth of backups.
My TM is on a samba share, I've searched a bit and followed a guide:
http://blog.robberthamburg.nl/mac-osx-leopard-repair-a-time-machine-error-11-pro blem
to try and fix the problem by deleting a .inProgress backup but this has not helped. unfortunately this has did not fix it. I had also read that there are sometimes problems with TM and Spotlight indexing so I have turned spotlight off completely. Still no luck.
Here is a log dump of my latest backup attempt:
Sep 12 01:31:59 lysithea /System/Library/CoreServices/backupd[763]: Backup requested by user
Sep 12 01:31:59 lysithea /System/Library/CoreServices/backupd[763]: Starting standard backup
Sep 12 01:32:04 lysithea /System/Library/CoreServices/backupd[763]: Mounted network destination using URL: smb://mdaemon@io:139/timemachine_lysithea
Sep 12 01:32:04 lysithea /System/Library/CoreServices/backupd[763]: Backup destination mounted at path: /Volumes/timemachine_lysithea
Sep 12 01:32:06 lysithea /System/Library/CoreServices/backupd[763]: Disk image /Volumes/timemachinelysithea/lysithea0025bcdeabda.sparsebundle mounted at: /Volumes/lysithea Time Machine
Sep 12 01:32:06 lysithea /System/Library/CoreServices/backupd[763]: Backing up to: /Volumes/lysithea Time Machine/Backups.backupdb
Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: No pre-backup thinning needed: 7.61 GB requested (including padding), 89.80 GB available
Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
Sep 12 01:40:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 01:45:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 01:50:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 01:55:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:00:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:05:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:10:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:15:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:20:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:25:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:30:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:32:05 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:32:37 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:33:09 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:33:42 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:35:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:38:38 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:39:08 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:39:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:40:27 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:42:12 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:42:43 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Stopping backup.
Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Error: (-43) SrcErr:NO Copying /Users/mdaemon/Library/Preferences/com.apple.DirectoryUtility.plist to /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/466ADDEF-7D04-45 15-B024-C02ADF152EA7/Macintosh HD/Users/mdaemon/Library/Preferences
Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Copied 16247 files (5.9 GB) from volume Macintosh HD.
Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Copy stage failed with error:11
Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backup failed with error: 11
Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Restarting backup after linking failure.
Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Starting standard backup
Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backup destination alias resolved to path: /Volumes/timemachine_lysithea
Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Disk image /Volumes/timemachinelysithea/lysithea0025bcdeabda.sparsebundle mounted at: /Volumes/lysithea Time Machine
Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backing up to: /Volumes/lysithea Time Machine/Backups.backupdb
Sep 12 02:43:42 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
Sep 12 02:51:03 lysithea /System/Library/CoreServices/backupd[763]: No pre-backup thinning needed: 509.8 MB requested (including padding), 83.21 GB available
Sep 12 02:51:03 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Indexing a file failed. Returned -12 for: /.DS_Store, /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/AB3F09D7-61EB-4D 9F-B0EF-AC4C1E0712EA/Macintosh HD/.DS_Store
Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Aborting backup because indexing a file failed.
Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Stopping backup.
Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Copied 0 files (0 bytes) from volume Macintosh HD.
Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Copy stage failed with error:11
Sep 12 02:51:14 lysithea /System/Library/CoreServices/backupd[763]: Backup failed with error: 11
Sep 12 02:51:15 lysithea /System/Library/CoreServices/backupd[763]: Ejected Time Machine disk image.
Sep 12 02:51:18 lysithea /System/Library/CoreServices/backupd[763]: Ejected Time Machine network volume.
Any help would be greatly appreciated

mattdaemon wrote:
My TM is on a samba share
First problem: this is *not supported by Apple:* http://support.apple.com/kb/HT1733
to try and fix the problem by deleting a .inProgress backup but this has not helped.
Second problem: deleting (or changing or moving) things in TM backups via the Finder can hopelessly corrupt them.
Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
Sep 12 01:40:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
These can usually be stopped by excluding the backups from any anti-virus scanning, and Spotlight indexing, at least on supported volumes. Unless you're sure you have Spotlight off entirely, try excluding your backups via System Preferences > Spotlight > Privacy.
Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Error: (-43) SrcErr:NO Copying /Users/mdaemon/Library/Preferences/com.apple.DirectoryUtility.plist to /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/466ADDEF-7D04-45 15-B024-C02ADF152EA7/Macintosh HD/Users/mdaemon/Library/Preferences
Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Indexing a file failed. Returned -12 for: /.DS_Store, /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/AB3F09D7-61EB-4D 9F-B0EF-AC4C1E0712EA/Macintosh HD/.DS_Store
Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Aborting backup because indexing a file failed.
Both of these appear to indicate problems on your backup drive, perhaps directory problems. For a supported one, a +*Repair Disk+* (not permissions) will often fix it. If there's a way to run that on your backups, it's worth a try.
It's also possible there's a problem on your internal HD, so it's worth doing a +*Verify Disk+* (not permissions) on it, too, via Disk Utility. If that shows errors, you'll have to boot from your Install disc and use it's copy of DU to repair them.

Time machine error - backup fails due to sparsebundle already in use

Since upgrading, Time machine reports backup error:
TIme Machine Error
The backup disk image ...sparsebundle is already in use.
Any thoughts?

Thanks russ. After the initial upgrade to Mt Lion, no backups have been made. Every attempt reports the sparsebundle error. I recently updated to 10.8.1 and a whole new set of problems have shown up which is having me question the wisdom of continuing to invest in Apple product.
I have decided to pack it in with regard to the timecapsule product, as it is just too unreliable, and certainly not worth the continued time and effort it has been taking to try and get it to work. I have instead gone with an online backup service, Crashplan. I have the backup service I am seeing and I am no longer frittering away valuable time on something that ought to just work.
Problem solved.

Time Machine Backup Failed - on three Macs. Used to work fine.

"*+Time Machine Error*+
+Unable to complete backup. An error occurred while copying files to the backup volume.+"
Last week all three machines were running fine. The Time Machine disk is hooked up to an Airport Extreme running 7.3.2 firmware. I updated it today to 7.4.1 in hopes of fixing the problem. All Macs are on 10.5.6 and have been for a month or more.
When "Backup now" is selected all machines stick on Preparing backup" for a few minutes and then fail.
I'm bummed that this is happening now. I used to use SilverKeeper (free from LaCie). It's faster and more comprehensive, but somehow I got sucked in by Apple's futuristic (historic?) interface. Now, in order to use SilverKeeper I need to erase the Time Machine drive - all 1.2TB.
I don't feel TM is ready for storage of important data. A commercial product would never make it to market if it continually had issues like this. Nearly 10,000 topics in this forum, and a good portion have just plain bad things to say.
I'm sure a lot of people have run into this on their own setups. Has anyone solved the issue? Please help.

Yes, perhaps we're missing something. But I'd rather stick with what works. Here's a software review that pretty much echo's my feelings:
*+I've tried to love Time Machine. I really have. It was one of the reasons I was in an all-fire hurry to upgrade to 10.5. I spent the cash, installed the OS, and immediately set up TM. Or at least I tried to. My new Airport Extreme wasn't allowed to access the USB disk for this purpose.+*
*+But I found a hack and things were good. For about a day. "To **** with it" I thought and went back to Carbon Copy Cloner. An excellent and free app that got me thru years of work with no loss of data. But wait! Now that I upgraded to 10.5 CCC no longer works.+*
*+So I played with it for a few weeks and eventually, I got it to work.... Until Apple released the official software upgrade that allowed Airport Extreme disks to work with TM and it broke again. Another 4 days of playing and reinstalling, and reformatting, and shuffling data. Still nothing.+*
*+****, you should have seen the look on their eyes when I showed up to the Apple store toting my G5 PowerMac Dual, AirPort Extreme, MacBook Pro, wife's MacBook, and two USB drives. AND my Apple ProCare card.+*
*+I took up half the Genius Bar for about 2 hours and still left with a backup scheme that would only partially work. Then, upon arriving home, the IP addresses had changed so I had to repeat half of the steps I barely remembered (and the Genius made up on the fly).+*
*+Finally all was good in the world. Until last week. My wife asked me to send her a picture I took of her with our new puppy at our new house about 6 months ago. I pulled up iPhoto and couldn't locate the picture. "No problem, I've got Time Machine" I thought.+*
*+The story is getting long and you can see where it's going. Not only was the picture missing, but 4 months of pictures were missing. 4 months starting when I stopped using CCC and, even though TM was running, it deleted the oldest files without any warning, any notification, or any reason. In fact the TM drive still had over 400GB free.+*
*+Yes, I had to replace a drive in that 4 month window and yes, I made sure I pulled the data off of Time Machine. HUGE pain in the @ss - it took nearly 4 days to copy the data from TM to the new drive, and apparently a big chunk was lost.+*
*+Finally, the end of my little story. I'm back using CCC. v3 is out and it works with 10.5 and reportedly, 10.6. Four years of using CCC and I've never lost so much as an email (much to the chagrin of my old landlord that emailed me that dogs were perfectly fine, only to try to sue me later).+*
*+For all of those who trust Time Machine, go ahead and try to find a file from a few months ago. It's not as easy as the interface makes it look, and it may not be there at all.+*
*+Time Machine - go sparse yourself. And thanks Bombich software for a superior product in Carbon Copy Cloner.+*

Time Machine Error "Unable to complete backup"

I have not backed up my hard drive for about 30 days. When I plug my external hard drive in, Time Machine "prepares backup" for a while, then gives me the following message:
*Time Machine Error*
Unable to complete backup. An error occurred while copying files to the backup volume.
I tried unplugging and re-plugging, rebooting my computer, trashing the ".inprogress" backup file and restarting. It did not help. While it time machine is preparing the backup, my computer runs crazy slow, with the rainbow pinwheel spinning for about 5-10 seconds just about every time I click the mouse, in any program.
Per someone's suggestion, I put "sudo grep backupd /var/log/system.log" into terminal, and this is what came up:
"No pre-backup thinning needed: 4.98 GB requested (including padding), 70.16 GB available
Waiting for index to be ready (906 > 0)
Unable to rebuild path cache for source item. Partial source path:
Indexing a file failed. Returned -12 for: /Applications/iChat.app, /Volumes/Time Machine Backups 1/Backups.backupdb/My Computer (2)/2011-01-13-113417.inProgress/CB0D491E-EF04-48A0-9AE9-32AE43E9209C/Macintosh HD/Applications/iChat.app
Aborting backup because indexing a file failed.
Stopping backup."
This time, it was apparently iChat, but in each of the three times I've tried to backup and gotten this error message, a different file has been the culprit for the indexing error.
Any suggestions?

orchestr wrote:
Indexing a file failed. Returned -12
see [this_|http://web.me.com/pondini/TimeMachine/C3.html] user tip by Pondini.
JGG

Time Machine Error: The backup was not performed because an error occurred

G'day (from Queensland, Australia)
Not for the first time Time Machine has broken down - originally in September 08 (I just can't recall how I fixed it!!).
Now it has failed after 14 months of faultless performance.
There seems to be little help available, but searching for solutions finds plenty of problems.
I get the message "The backup was not performed because an error occurred while copying to the backup disk.
The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair you backup disk."
(I have a Time Capsule as my backup disk)
Disk Utility runs and finds-
Verifying volume “Backup of xxxxxx’s iMac”
2010-01-25 12:16:09 +1000: Starting verification tool:
2010-01-25 12:49:21 +1000: The volume Backup of xxxxxx’s iMac appears to be OK.
2010-01-25 12:49:21 +1000: Repair tool completed:
So I search and find "Fix for broken Time Machine backups under Snow Leopard"
(http://www.andrewgrant.org/2009/09/22/fix-for-broken-time-machine-backups-under- snow-leopard.html) - downgrading to 7.4.1 of the Airport Extreme / Time Capsule firmware.
But still have the same Time Machine error!
On to http://forums.macosxhints.com/showthread.php?t=103919&highlight=TimeMachineError
and try-
"... suggesting would be something like renaming the existing TimeMachine file on your backup disk - e.g. add a date to the end of it.
And then go onto Time Machine preferences and set it up as if it were the first time you used it. (Renaming the file on the backup disk should make Time Machine think that you are starting fresh.)"
So, using Finder, I opened my Time Capsule and renamed "xxxxxx’s iMac_00224135e6fb.sparsebundle" as "091222xxxxxx’s iMac_00224135e6fb.sparsebundle091222"
And finally, this worked - I have my backups to 22 December and a complete backup as at today and hopefully for at least another 14 months!

pjh42 wrote:
G'day (from Queensland, Australia)
Not for the first time Time Machine has broken down - originally in September 08 (I just can't recall how I fixed it!!).
Now it has failed after 14 months of faultless performance.
There seems to be little help available, but searching for solutions finds plenty of problems.
On the contrary. At the top of this forum are four *User Contributed Tips,* including one on Troubleshooting that would have saved you a great deal of time.

Time Machine Error. Unable to complete backup. An error occurred while copy

I purchased my iMac 24" in February.
After I had set up the machine I configured an IceCube Firewire 300 GB (Seagate) Hard Drive as a backup volume and flicked the switch in Time Machine. All went as expected. I even restored my whole hard drive from the Time Machine volume about a month ago after I repartitioned the boot volume to set up Boot Camp. No problems.
About a week ago I purchased a 500GB WD HDD and set it up inside the IceCube enclosure (I remembered to make it the "Master" disk too!!). I partitioned it with Disk Utility with a GUID Mac OS X (Journaled) partition for my Leopard boot partition, and as MS-DOS FAT32 for my Boot Camp external partition. I used Carbon Copy Cloner to copy all the Windows files across from Boot Camp to the new FAT32 partition and set up Time Machine to make a backup of the Leopard boot partition.
After several hours Time Machine stopped with the error message above. ("Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup").
I have spent days formatting the new WD drive, repairing permissions on the boot drive, excluding large files and cache files from the backup in Time Machine to no avail. Every time I get the same message. I even set up another 200GB firewire drive to see if it was anything to do with the enclosure of WD HDD. Same result!!
I have searched these forums for any ideas, and have done wide searches with Google but nothing has worked.
I can not understand why my Mac worked perfectly with Time Machine before I installed the new Western Digital Hard Drive.
What have I missed?

I keep getting the Time Machine backup error too, like many others. Was fine until just the other day, now, nothing. Although my husband's backs up just fine. I assume it's the 10.5.3 bug everyone else has. I've tried reselecting the drive, running the disk utility, shutting everything on and off... help!
Here's the console log- anyone know what this means?
Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Starting standard backup
Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Network mountpoint /Volumes/Library not owned by backupd... remounting
Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Network volume mounted at: /Volumes/Library-1
Jun 10 08:37:43 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Disk image /Volumes/Library-1/Tiffany Danko’s Computer (2)_001b63baf698.sparsebundle mounted at: /Volumes/Backup of Tiffany Danko’s Computer (2)
Jun 10 08:37:43 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Backing up to: /Volumes/Backup of Tiffany Danko’s Computer (2)/Backups.backupdb
Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Failed to create progress log file at path:/Volumes/Backup of Tiffany Danko’s Computer (2)/Backups.backupdb/Tiffany Danko's computer (2)/2008-06-09-065427.inProgress/.Backup.234797868.792920.log.
Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Event store UUIDs don't match for volume: Macintosh HD
Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Error: (-36) Creating directory 77B4FA27-3E65-4B81-897C-610DEE7BB187
Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Failed to make snapshot.
Jun 10 08:37:53 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Backup failed with error: 2
Jun 10 08:37:58 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Ejected Time Machine disk image.
Jun 10 08:37:59 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Ejected Time Machine network volume.

Is there a solution for Time Machine error?

I got an error in Time Machine saying backup had failed, a couple of days ago. Spent the next day or two trawling the web and found thousands of postings from people with the same error, but no solution.
(At least, some people had a solution - they were using PC-formatted hard drives.)
I've been using Time Machine for a few weeks, and it has only now taken a dislike to my external hard drive, which is connected by FireWire.
Is there a solution to this problem, or should I revert to using SuperDuper, which I was using successfully before?
I haven't put in lots of information about the apps I'm running, because this is a general query rather than a specific one. If there's a solution, I'll use it; otherwise I'll wipe the drive and go back to using SuperDuper.

OisinOg wrote:
Pondini - Thank you for your slightly hostile reply.
On the contrary. The statement was: +"found thousands of postings from people with the same error, but no solution."+ I don't know where you found thousands of posts -- there are many here, but certainly not thousands. If you're talking about, say, a Google search, if you actually look at them, many are duplicates, unrelated to your problem, or unrelated to Macs at all -- and there are a number of solutions that seem to have fixed many of the real ones.
The error message was the standard one: "Time Machine Error - Unable to complete backup. An error occurred while creating the backup directory."
There's most likely another, better message in your logs. Thus the suggestion about Time Machine Buddy. You can also use the Console app (in your Applications/Utilities folder). Click on Show Log List, then navigate in the sidebar to your system.log (or system.log.0.bz2, etc. for previous ones). You can filter for backupd to get the same TM messages as the widget, but I prefer to view the full log at the date/time in question, as messages from other concurrent processes may have a clue.
I've gone through the suggestions in some of the helpful replies to those thousands of postings, by wiping my drive, erasing it and reformatting it, first in two partitions using the GUID method in Disk Utility, then in a single partition. But Time Machine still doesn't want to back up to it.
Sounds a bit like a problem communicating with the drive. The logs may clarify that.
The hard drive of my computer is 250GB; the external drive is 300GB. Both are SATA drives; the external is connected by FireWire.
How full are they?
Thanks for your suggestion of downloading the Time Machine Buddy widget; I'll give it a last try tonight.
What is the difference between a SuperDuper clone and a Time Machine backup?
The initial backup of both copies almost everything on your HD, excluding only some caches, temp files, etc., although you can exclude other things. This takes quite a while, of course. Thereafter, only the items that changed are backed-up.
SuperDuper (and CarbonCopyCloner, which I use, and other, similar apps) are most often used to make bootable "clones" identical copies of your HD -- if your HD fails, you can boot and run from them immediately. With TM, once your HD is repaired/replaced, you restore your system to it from your TM backup.
Score one for the clones, but TM has it's advantages, too (which is why many of us run both).
First is, CCC and SD look at every file and folder on your HD to see what changed. This is quite time-consuming and CPU-intensive, so most of us run it once a day (or less often), usually automatically at, say, 3 am. TM, however, runs hourly, but uses an internal File System Event Log of changes, so it is far quicker and less intrusive. There are exceptions, but most users rarely even notice the backups unless they see the icon revolving. On my small system, for example, TM rarely runs over 30 seconds; CCC is at least 15 minutes.
Second, not only does TM keep previous versions of changed files, but it manages the space and backups for you. It keeps those hourly backups for 24 hours; except the first of the day becomes a daily backup which is kept for a month; one per week becomes a weekly backup that is kept for as long as there's space (it will fill the drive/partition). But it's smart enough, as it deletes the old weeklies, that it won't delete it's copy of anything that still exists on your HD.
There isn't room to have two 250GB sections on a 300GB drive. I suppose I could get another 250GB drive - I have an IDE enclosure somewhere - but I don't fancy the expense right now.
Your CCC or SD partition only needs to be as large as your HD, although in a pinch it only needs to be somewhat larger than what's actually used on your HD. If you don't have room for both on the one drive, an even better solution might be to get a pair of smaller portable HDs for CCC/SD. Use one daily for, say, a week, then take it to your safe deposit box, workplace, relative's house, etc. and start with the other. Now you're also protected against fire, flood, theft, direct lightning strike on your power lines, etc.

HT3275 Time Machine error. Unable to complete backup. An error occurred while copying files to the backup volume. Tried restarting, remounting external WD drive. Still cannot backup.

Time Machine quit backing up files. Bought a new WD external drive. Worked for awhile, then quit backing up. Tried restarting computer, remounting drive. Message: Time Machine Error. Unable to complete backup. An error occurred when copying files. Suggestions?

Thanks so very much for your help!! I'm boggled by it and now just about ready to dump the whole idea of Time Machine and backup using a cloning program. Maybe TM is only guaranteed to work well with Time Capsule these days?
Today there again was no backup. I did as you suggested, looked into Console. It showed many lines of "(Error) DiskStore: No block in wakeup" and also repeatedly "(Warning) DiskStore: Ignored bogus fetch...".
So I created a marker and attempted to initiate a backup, keeping Console open and refreshed. Here's what I got:
8/19/13 5:18:40.385 PM Console: Marker - Aug 19, 2013 5:18:40 PM
8/19/13 5:19:48.844 PM com.apple.backupd: Starting standard backup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.508 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:38ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.510 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:40ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:20.000 PM kernel: USBF:          58091.976          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:20:51.000 PM kernel: USBF:          58122.985          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:22.000 PM kernel: USBF:          58153.992          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:53.000 PM kernel: USBF:          58185. 2          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:24.000 PM kernel: USBF:          58216. 14          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:55.000 PM kernel: USBF:          58247. 25          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:26.000 PM kernel: USBF:          58278. 41          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:57.000 PM kernel: USBF:          58309. 51          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:28.000 PM kernel: USBF:          58340. 59          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:59.000 PM kernel: USBF:          58371. 68          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:25:30.275 PM xpchelper: for uid: 501 -- timeout while waiting on FSEvents flush; clearing cache.
8/19/13 5:25:30.000 PM kernel: USBF:          58402. 82          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:01.000 PM kernel: USBF:          58433. 96          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:32.027 PM com.apple.backupd: Backing up to: /Volumes/TMBackups/Backups.backupdb
8/19/13 5:26:32.000 PM kernel: USBF:          58464.112          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:02.653 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David‚Äôs iMac size:37
8/19/13 5:27:02.657 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David‚Äôs iMac size:37
8/19/13 5:27:03.000 PM kernel: USBF:          58495.121          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:12.668 PM com.apple.backupd: Backup failed with error: 2
During this 9-minute timeframe Finder also was inoperative - according to Activity Monitor: "Not Responding".
I'm thinking it's the standalone Buffalo backup drive not waking up, and so everything comes to a screeching halt. Do you also think I should abandon TM and just do manual backups every day using a clone program?

I recently upgraded to Mavericks and the time machine is failing to backup. Time Machine began only backing up twice a day and now has stopped.

I recently upgraded to Mavericks and the time machine is failing to backup. Time Machine began only backing up twice a day and now has stopped.

This is the error message I got:
2014-03-18 17:02:30 -0400 com.apple.backupd[4971]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TOSHIBA EXT/Backups.backupdb/Quincy‚Äö√Ñ√¥s iMac size:37
2014-03-18 17:02:30 -0400 com.apple.backupd[4971]: Backup failed with error 2: 2

Time Machine Error: An error occurred while creating the backup directory

Time Machine Error: Unable to complete backup. An error occured while creating the backup directory.
I back up to wirelessly to a Time Capsule. I get these errors often. I'll go for a few days with everything working and then encounter these errors. I've even completely erased the Time Capsule drive and started over. It'll work fine for a few days and then start the errors over again. Interestingly, when the errors occur, the Time Capsule drive can not be unmounted even if clicking the eject button. I am on 10.5.8 but it happened in 10.5.7 as well. I have another Mac that doesn't seem to have any issues with the same Time Capsule.
Here's a log - they all seem to fail with similar errors:
Starting standard backup
Backup destination alias resolved to path: /Volumes/AirPort Disk
Disk image /Volumes/AirPort Disk/Brittney’s Computer_0019e33d4fde.sparsebundle mounted at: /Volumes/Backup of Brittney’s Computer
Backing up to: /Volumes/Backup of Brittney’s Computer/Backups.backupdb
2009-08-27 13:52:48.465 FindSystemFiles[2955:713] Querying receipt database for system packages
2009-08-27 13:52:48.693 FindSystemFiles[2955:713] Using system path cache.
Failed to create progress log file at path:/Volumes/Backup of Brittney’s Computer/Backups.backupdb/Brittney’s Computer/2009-08-26-212437.inProgress/.Backup.273091970.250248.log.
Error: (-50) Creating directory 7CCE60DD-ADCC-4004-A0D9-3EC83D892372
Failed to make snapshot.
Backup failed with error: 2
Failed to eject volume /Volumes/Backup of Brittney’s Computer (FSVolumeRefNum: -114; status: -47; dissenting pid: 0)

Nancy H wrote:
I used it as it came, supposedly formatted for a mac.
It may or may not be right.
I'd be inclined to start over, per #5 in the Frequently Asked Questions *User Tip* at the top of this forum.
If that doesn't help, go on to #C10, etc., in the Troubleshooting Tip, as in the previous post.

Time Machine Error, backup disk couldn't be mount

I have a USB drive plug to my Airport Extreme and I use it for Time Machine. Today I had a message saying: "Latest Backup:Failed"
Time Machine Error
The Backup disk image could not be mounted.
The hard disk is there, I can drag, drop, copy, delete files on that disk. There's is a big file call Serge'siMac_001ec205f583.sparsebundle, the file does not seem corrupted, I could probably drag it to the Desktop. How can I mount the backup disk.
Serge

I had the same problem and found out how to fix it
You can check the whole process here in a post I wrote for the Hardmac blog (it's rather long...):
How I saved my corrupted Time Machine sparsebundle image…

Time machine error failed

Similar Messages

Maybe you are looking for