You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
After installing Lion Time Machine backup (not initial one which is long by default) takes about 40 minutes vs. about 5 minutes in Snow Leopard. Very annoying because it slows down my entire system for such a long time. Any help, please?
Mac mini, Mac OS X (10.7)
Although using Mac OS 10.6, I have done updates that will allow my machine to cross over to Lion (a.ka., Mac OS X 10.7). I too am having this same issue. I didn't know if the Time Machine.app was timing-out because of slow USB2 speeds or some other I/O bus bottleneck. My Macintosh HD does fine. The problem really is apparent with my second internal drive. While the drive is 500 GB, there was only 110 GB of file size being used.
Backup.app has come through for me. I let Time Machine.app do hourly back-ups of my boot Macintosh HD while Backup.app does end of day back-ups of my second drive.
Hi! I've had similar problems to many on this topic, and I have tried most of the solutions. But I do find that the problems come back after a few (2-4) days. I've also observed what I think are two separate problems (but, no doubt related):
But sadly, I have no solution. I'm a power user, but not deeply technical, so I share the above observations. I was OK with this happening the first time since I upgraded, but it has now happened at least three times. I'm typing this with my MacBook fan blowing as mdworker32 and mds suck up the processer. I at first thought it could be to do with problems with locked drives, shutting down (or sleeping) during a backup, etc. But when it came back yesterday, I had put my MB to sleep the night before and carefully checked first that no backup was running and that all recent backups in the log looked good. But yesterday morning, Time Machine started with the Indexing routine... and then Spotlight decided to have a go as well.
I'm quite frustrated. I'm assuming that Apple in their inimitable quiet style are reading forums, getting feedback, and a fix will come.
I'm quite tempted now to create a new backup (and more to the point, tempted to reinstall a clean Lion - I'm currently running a three-year old MacBook which has been upgraded to Snow Leopard and Lion).
But other than Time Machine I'm actually very happy with Lion!
If anyone has any comments or can throw any additional light as to why is problem suddenly decides to reoccur, I'd be interested!
Thanks, Nic.
After upgrading to Lion, I have exactly the same symptoms with an iMac of 2010.
Hi,
has someone tested this solution:
http://maurodelrio.com/2011/07/24/fix-lion-slow-timemachine-backups/
I am asking because we need several results to understand if this is really working.
Thanks
Yes.
I stopped the backup. Removed spotlight indices from both drives, and ran Disk Utility on the TM sparsebundle.
Disk Utility announced that it could find no errors with the TM disk.
Spotlight started indexing---and estimated 5 hours to do the job on the main disk. (I don't know if it took that long, I went to bed before it finished with 2 hours estimated to go).
I started up TM again.
16/08/11 7:44:11.774 AM com.apple.backupd: Starting standard backup
16/08/11 7:44:11.776 AM com.apple.backupd: Attempting to mount network destination URL: afp://x@y._afpovertcp._tcp.local/Wells-3
16/08/11 7:44:12.460 AM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Wells-3-1 using URL: afp://x@y._afpovertcp._tcp.local/Wells-3
16/08/11 7:44:33.978 AM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
16/08/11 7:44:37.349 AM com.apple.backupd: Disk image /Volumes/Wells-3-1/xxx.sparsebundle mounted at: /Volumes/Time Machine Backups
16/08/11 7:44:37.366 AM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
16/08/11 7:44:40.365 AM com.apple.backupd: 88.76 GB required (including padding), 423.38 GB available
16/08/11 7:44:40.425 AM com.apple.backupd: Waiting for index to be ready (100)
16/08/11 7:49:18.608 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 131, length 7, native = no)
16/08/11 7:49:22.503 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 131, length 7, native = no)
16/08/11 7:49:41.002 AM com.apple.backupd: Copied 16120 files (0 bytes) from volume H.
16/08/11 7:49:41.002 AM com.apple.backupd: Event store UUIDs don't match for volume: H
16/08/11 8:44:40.487 AM com.apple.backupd: Copied 101.5 MB of 74.0 GB, 541750 of 3687840 items
16/08/11 9:44:40.784 AM com.apple.backupd: Copied 263.7 MB of 74.0 GB, 913868 of 3687840 items
16/08/11 10:43:13.359 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 131, length 7, native = no)
16/08/11 10:43:13.359 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 132, length 7, native = no)
16/08/11 10:44:43.289 AM com.apple.backupd: Copied 274.4 MB of 74.0 GB, 1179865 of 3687840 items
16/08/11 11:36:48.297 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 11:36:49.345 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 133, length 7, native = no)
16/08/11 11:36:50.845 AM mdworker: iCal.mdimporter: could not find component keys: /Users/michaeln/Documents/Calendar Backup/Calendar.ics
16/08/11 11:36:51.125 AM mdworker: iCal.mdimporter: could not find component keys: /Users/michaeln/Documents/Calendar Backup/Library Loans.ics
16/08/11 11:37:13.675 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 11:37:59.078 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 132, length 7, native = no)
16/08/11 11:37:59.179 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 11:38:00.688 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 11:38:00.689 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
16/08/11 11:38:00.970 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
16/08/11 11:38:01.345 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
16/08/11 11:38:50.344 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
16/08/11 11:38:53.402 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 131, length 7, native = no)
16/08/11 11:39:01.823 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 11:39:02.206 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 11:44:43.320 AM com.apple.backupd: Copied 382.9 MB of 74.0 GB, 1362117 of 3687840 items
16/08/11 12:44:44.153 PM com.apple.backupd: Copied 497.5 MB of 74.0 GB, 1523970 of 3687840 items
16/08/11 12:59:41.330 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 12:59:53.541 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 131, length 7, native = no)
16/08/11 1:00:00.529 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 131, length 7, native = no)
16/08/11 1:28:51.989 PM com.apple.backupd: Copied 1679760 files (716.8 MB) from volume C.
16/08/11 1:28:51.990 PM com.apple.backupd: Event store UUIDs don't match for volume: C
16/08/11 1:28:52.002 PM com.apple.backupd: Waiting for index to be ready (100)
[snip 60 lines]
16/08/11 2:48:05.251 PM com.apple.backupd: Waiting for index to be ready (100)
16/08/11 2:48:47.151 PM com.apple.backupd: Copied 716.8 MB of 74.0 GB, 1679760 of 3687840 items
16/08/11 3:48:49.712 PM com.apple.backupd: Copied 821.0 MB of 74.0 GB, 2204398 of 3687840 items
16/08/11 4:51:37.955 PM com.apple.backupd: Copied 821.0 MB of 74.0 GB, 2449918 of 3687840 items
16/08/11 5:51:38.857 PM com.apple.backupd: Copied 821.6 MB of 74.0 GB, 2550272 of 3687840 items
16/08/11 7:53:08.202 PM com.apple.backupd: Copied 821.7 MB of 74.0 GB, 2616564 of 3687840 items
16/08/11 9:19:47.726 PM com.apple.backupd: Copied 821.7 MB of 74.0 GB, 2741313 of 3687840 items
16/08/11 10:23:22.682 PM com.apple.backupd: Copied 821.7 MB of 74.0 GB, 2755541 of 3687840 items
16/08/11 10:35:35.644 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 10:35:37.166 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 133, length 7, native = no)
16/08/11 10:35:37.666 PM mdworker: iCal.mdimporter: could not find component keys: /Volumes/B/Users/michaeln/Documents/Calendar Backup/Calendar.ics
16/08/11 10:35:38.412 PM mdworker: iCal.mdimporter: could not find component keys: /Volumes/B/Users/michaeln/Documents/Calendar Backup/Library Loans.ics
16/08/11 10:35:55.223 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 10:38:05.508 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 132, length 7, native = no)
16/08/11 10:38:05.752 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 10:38:06.963 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 10:38:06.963 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
16/08/11 10:38:07.488 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
16/08/11 10:38:08.200 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
16/08/11 10:39:01.155 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
16/08/11 10:39:07.542 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 131, length 7, native = no)
16/08/11 10:39:11.270 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 10:39:11.880 PM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
16/08/11 11:23:23.059 PM com.apple.backupd: Copied 821.7 MB of 74.0 GB, 2879773 of 3687840 items
17/08/11 12:06:02.717 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
17/08/11 12:06:32.642 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 131, length 7, native = no)
17/08/11 12:08:13.527 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 131, length 7, native = no)
17/08/11 12:23:23.466 AM com.apple.backupd: Copied 821.7 MB of 74.0 GB, 3013165 of 3687840 items
17/08/11 12:36:20.110 AM com.apple.backupd: Copied 3047162 files (903.9 MB) from volume B.
17/08/11 12:36:21.083 AM com.apple.backupd: Event store UUIDs don't match for volume: B
17/08/11 1:23:24.259 AM com.apple.backupd: Copied 2.4 GB of 74.0 GB, 3205007 of 3687840 items
17/08/11 2:25:03.373 AM com.apple.backupd: Copied 8.8 GB of 74.0 GB, 3400703 of 3687840 items
17/08/11 3:25:03.921 AM com.apple.backupd: Copied 10.9 GB of 74.0 GB, 3418528 of 3687840 items
17/08/11 4:25:54.486 AM com.apple.backupd: Copied 13.0 GB of 74.0 GB, 3456877 of 3687840 items
17/08/11 4:48:17.957 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
17/08/11 4:53:41.988 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
17/08/11 4:54:15.109 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
17/08/11 4:54:15.882 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
17/08/11 4:54:21.488 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
17/08/11 4:54:27.574 AM com.apple.backupd: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no)
17/08/11 4:56:07.472 AM com.apple.backupd: Copied 3489710 files (30.5 GB) from volume E.
17/08/11 4:58:49.440 AM com.apple.backupd: Waiting for index to be ready (100)
[snip 840 lines]
17/08/11 7:34:40.606 PM com.apple.backupd: Waiting for index to be ready (100)
So, no, that didn't work in any meaningful way at all.
I've stopped it again. Then I'll install the latest Lion upgrade, in a clutching-at-straws hope that it fixes something.
Version 10.7.1 did not solve the issue.
The solution of Mauro del Rio did not work for me either: "No such file or folder".
I wander whether it is an Airport disk problem only or do Time Capsules have a similar problem.
I remember when we went over to Leopard and an Airport firmware update, the Airport disk had a problem with (dis)mounting Airport disks used for Time Machine. It looked like Apple wanted you to go to Time Capsules.
It was not solved until going to Snow Leopard, when it was wise enough to patch the Airport with the long available firmware again.
In the meantime, I wish Apple came with a solution.
P.S.: After having Spotlight run for 20 minutes and the TM Backup after that, the Airport disk was dismounted???!!!
I wander whether it is an Airport disk problem only or do Time Capsules have a similar problem.
I don't think it has anything to do with the hardware. I'm having the issues with 3rd party disks on a MacMini running Snow Leopard. That is, genuine Apple software on an Apple machine, but with 3rd party disks. As mentioned, since these are RAIDZ disks I really don't beleive there are any hardware issues---and assorted disk utility checks and speed tests seem to back this up.
And 10.7.1 made no difference.
What seems to be happening is that it is going through every file on the source disk and checking to see if it needs to copy it. Since this is a subsequent attempt to do an initial copy, a lot of files are there already, so almost no copying occurs. However, this checking is extraordinarily slow. Now (having been left overnight) it's up to the 'indexing backup..." stage, and it predicts 19 days left, while Console shows the usual "com.apple.backupd: Waiting for index to be ready (100)". I'll see how far it has progressed when I come back to it this evening.
Not sure if this will be of much help, but just in case:
The problem: extremely long Wi-Fi Time Capsule backup process after installing Lion, and the backup never completed.
After installing Lion over 10.6.8, I had problems backing up a MBP to an older Time Capsule via Wi-Fi. Took all night, even with the MBP next to the Time Capsule for highest Wi-Fi speed. The backup seemed to work, but the Time Machine pane in System Preferences said that the backup never happened. I tried this several times over about a week period but it never completed a backup.
Come to think of it, backups had been getting slower and slower even before the Lion update. Even when just a few KB or MB were backed up. I've had the MBP and Time Capsule (both refurbs) for 2 years with no reformatting or resetting of any kind, knock on wood. The MBP would get hot to the touch from all the backup-related activity, but the backups did eventually complete. After the Lion install the backups didn't complete.
The solution: I ran the big post-Lion-install backup over ethernet.
I connected the MBP to the Time Capsule via ethernet, turned off Wi-Fi, plugged in the MBP, set Computer Sleep: to "Never" in the Power Adapter tab of the Energy Saver pane of System Preferences, and chose the Backup Now item from the Time Machine menu in the menu bar. I let the backup run overnight (121+ GB) and this time it completed. Suspiciously, it finished just a few minutes after I logged back into the "sleeping" display.
The Time Machine Preferences pane said that the latest backup had just completed. Subsequent backups, even over Wi-Fi, take only minutes for KB or MB of data, just like the good old days.
Apologies for the long-windedness, but I wanted to be precise. Hope this helped.
I've got the same problem.
Brand new 16gb ram 3.4ghz i7 iMac that came with Lion installed a couple of days ago. It take about half an hour to backup 30kb!!!!
KB!!!!
My macbook pro with snow leopard is way faster.
APPLE, if you are listening PLEASE INVESTIGATE.
Thank you
What does Console report (search for backup)
For me, it seems that 10.7.1 solved the issue. Do you have the same experience?
I spoke too soon. It's back again! Pre and post.
I spoke too soon. It's back again! Pre and post.
And also for me. It's now been running a couple of days, and informs me that it has 19 days to go!
19/08/11 10:42:48.164 PM com.apple.backupd: Waiting for index to be ready (100)
for hundreds of lines.
Sigh
The first backup finally finished. It took over three days!
It's done some hourly backups since then, although they are still relatively slow, taking 45min to back up jut a few MB. This seems to be caused by it spending a huge amount of time deciding what to back up.
Just a thought: is this caused by big disks? The new disk is a 3rd party 2TB. Are other people getting good TM speed out of Lion with large boot disks?
I don't think it has much at all to do with large disks. I have been closely monitoring Time Machine whilst it's been running a backup and seen a number of undesirable pieces of behaviour:
(1) Any modification of data seems to cause Time Machine to re-run the backup process - i.e. it loops.
(2) During the most recent backup, a loop occurred and it took 1hr 20 minutes to write a total of 600Mb of data. During this time many Gigabytes of data were transferred (both read and written) - I could understand the reading, I really cannot see any justification for all the writes which brings me to this:
(3) Having taken an hour to perform (2) above, "Finishing Backup" takes a further 20 minutes during which an additional couple of Gig was written and at least that much read.
There are no errors in the logs, I've run repair on all volumes including Time Machine regardless the amount of data being shunted around seems completely out of proportion with the small amount of data being backed up.
Time Machine backup very slow in Lion
