Time machine running slow

Not sure why my wireless setting are set up high connections.What happens if I put something into the wan port?

Ok, so I have had another play this morning. I have plugged the Mac into the router connecting at 100Mbps. I then added a file around 4GB to the Mac. I first transferred this to the WD drive which transferred at 95Mbps average continuously until the file was transferred. This tells me there is not issue with my network and equipment.
Secondly I started a time machine backup and it picked up this file as needing backing up. The transfer started quite quickly which was good compared to yesterday. It was a little choppy on the through put but was reaching peaks of 95Mbps. Great. I am just putting the choppy down to time machine copying and sorting or something of that sort.
Oh dear. 1GB transfered and the backup suddenly goes slow again without warning again. Then later on, a lot later, it speeds up again. I am seriously looking at my router as the problem here but require to swap it out to test it. It just seems so strange that it is up and down like this. Oh, and right now (while writing this) it is back at 72Kbps peak. This makes no sense that Time Machine itself would keep changing the transfer rates so dramatically.
Regards,
Adam.

Similar Messages

Time machine running slow and slowing network access

I have had and continue to have issues with wifi on my MBP. Those are pretty well summarized in https://discussions.apple.com/thread/5535320?start=30&tstart=0. I've been able to make mt system usable with some of the less dodgy workarounds in that thread ( like keeping a ping on my router running )
That thread really doesn't mention the issues I've been having with time machine though, so I thought I'd bring this up here. Whenever time machine starts up, Safari and mail become unresponsive. It's worst when TM is "preparing" of "cleaningup", though barely usable during the actual backup. Mostly, I can work around that too, but occationally, TM will find GB of data to be backed up and lock up my mac for a day. Here's a recent example:
2/16/14 12:30:27.952 PM com.apple.backupd[11557]: Starting automatic backup
2/16/14 12:30:28.466 PM com.apple.backupd[11557]: Attempting to mount network destination URL: afp://;AUTH=No%20User%20Authent@MyBookLive._afpovertcp._tcp.local/TimeMachine
2/16/14 12:30:33.866 PM com.apple.backupd[11557]: Mounted network destination at mount point: /Volumes/TimeMachine using URL: afp://;AUTH=No%20User%20Authent@MyBookLive._afpovertcp._tcp.local/TimeMachine
2/16/14 12:31:44.678 PM com.apple.backupd[11557]: Disk image /Volumes/TimeMachine/sparky.sparsebundle mounted at: /Volumes/Time Machine Backups
2/16/14 12:31:46.613 PM com.apple.backupd[11557]: Backing up to /dev/disk2s2: /Volumes/Time Machine Backups/Backups.backupdb
2/16/14 12:34:07.904 PM com.apple.backupd[11557]: Will copy (1.66 GB) from Macintosh HD
2/16/14 12:34:08.004 PM com.apple.backupd[11557]: Found 83487 files (1.66 GB) needing backup
2/16/14 12:34:08.738 PM com.apple.backupd[11557]: 4.16 GB required (including padding), 445.21 GB available
2/16/14 1:32:33.579 PM com.apple.backupd[11557]: Copied 534.6 MB of 1.66 GB, 28317 of 83487 items
2/16/14 2:40:02.513 PM com.apple.backupd[11557]: Copied 564.1 MB of 1.66 GB, 30225 of 83487 items
2/16/14 3:46:20.853 PM com.apple.backupd[11557]: Copied 593.2 MB of 1.66 GB, 31631 of 83487 items
2/16/14 4:48:19.461 PM com.apple.backupd[11557]: Copied 621.8 MB of 1.66 GB, 33182 of 83487 items
2/16/14 5:00:31.968 PM com.apple.backupd[11557]: Bulk setting Spotlight attributes failed.
2/16/14 5:54:51.036 PM com.apple.backupd[11557]: Copied 658 MB of 1.66 GB, 34773 of 83487 items
2/16/14 6:17:20.839 PM com.apple.backupd[11557]: Bulk setting Spotlight attributes failed.
2/16/14 6:56:27.566 PM com.apple.backupd[11557]: Copied 688.2 MB of 1.66 GB, 36246 of 83487 items
2/16/14 7:57:07.076 PM com.apple.backupd[11557]: Copied 704.8 MB of 1.66 GB, 37267 of 83487 items
2/16/14 8:58:52.469 PM com.apple.backupd[11557]: Copied 730.7 MB of 1.66 GB, 38724 of 83487 items
2/16/14 10:09:42.807 PM com.apple.backupd[11557]: Copied 760.5 MB of 1.66 GB, 40291 of 83487 items
2/16/14 11:21:25.825 PM com.apple.backupd[11557]: Copied 803.8 MB of 1.66 GB, 42462 of 83487 items
2/17/14 12:30:58.322 AM com.apple.backupd[11557]: Copied 834.1 MB of 1.66 GB, 43513 of 83487 items
2/17/14 1:45:28.495 AM com.apple.backupd[11557]: Copied 846.1 MB of 1.66 GB, 44160 of 83487 items
2/17/14 2:45:36.010 AM com.apple.backupd[11557]: Copied 868.6 MB of 1.66 GB, 45485 of 83487 items
2/17/14 3:57:29.939 AM com.apple.backupd[11557]: Copied 890.6 MB of 1.66 GB, 46729 of 83487 items
2/17/14 5:07:30.971 AM com.apple.backupd[11557]: Copied 926.7 MB of 1.66 GB, 48695 of 83487 items
2/17/14 6:15:49.283 AM com.apple.backupd[11557]: Copied 963.7 MB of 1.66 GB, 50583 of 83487 items
This is on an AC router. My peak throughput shows 19 Mb/s on menu meters, so, not great, but not this slow. Mostly, the network activity is nothing with short bursts of higher throughput.
I'm hoping this will be addressed in 10.9.2. In the mean time, are there any workarounds to get past this issue short of turning off TM?
Thanks,
Horst

These instructions were taken from Mac OS X Hints at:
http://hints.macworld.com/article.php?story=20050302225659382
The Unix program dd is a disk copying util that you can use at the command line in order to make a disk image. It makes a bit-by-bit copy of the drive it's copying, caring nothing about filesystem type, files, or anything else. It's a great way to workaround the need for Norton Ghost.
Normally, in order to make a disk image, the disk you're copying from has to be able to spin up and talk -- in other words, it's OK to make a copy if the disk is healthy. But what happens when your disk is becoming a doorstop? As long as it continues to spin, even with physical damage on the drive, dd and Mac OS X will get you out of the fire.
We had a situation recently where a friend sent a disk to us that had hard physical errors on it. It would boot in Windows, but then it would hit one of these scratch marks and just die. We fired up dd, and it started OK, but stopped at the same physical error location -- complaining about a Hard Error.
So the workaround was to designate the dd mode as noerror -- which just slides over the hard stops, and to add the mode sync, which fills the image with nulls at that point. We did it on BSD Unix, but as long as you can get the hard drive attached to your Mac, the command is the same:
dd bs=512 if=/dev/rXX# of=/some_dir/foo.dmg conv=noerror,sync
The bs=512 designates block size, and the if=/dev/rXX# is the UNIX path to the actual disk device. Make sure that the chosen directory (some_dir) has enough room to take the entire disk image -- which will be equal to the size of the drive. Since dd doesn't care about the contents of the drive, it copies every bit on the thing, so you get an image equal to the disk's capacity. A really big file. One workaround is to put it on a RAID array.
Once you've established the disk image (in this example, foo.dmg), you're almost home. Here's where your Mac OS X box is far and away the best thing to have. In this example, the dd output file is foo.dmg. You have to realize that this is an exact copy of a busted drive, but the "holes" are filled with nulls. As long as the damage isn't to the boot sector, though, when you double-click on it, Mac OS X mounts it without breathing hard ... who cares if it's FAT32, NTFS, whatever.
Due to the size of the image that we were copying, we put it on a RAID array, and had to access the image over the network -- it still mounted fine. In straight UNIX, if you try to mount a disk image, it complains that there is "no block device" and fails. Once your image is mounted, it appears in your Finder, and then it's easy work to retrieve the critical files from the image -- usually things like .doc files and .xls files and the lot.
Finally, since your disk is actually dying, once you have your image, you can drop it to tape or something and you've not only recovered your files, you've made a viable backup as well. Once again, that which destroys a Windows box becomes a play thing to a Mac OS X box.

Why does ext HDD / time machine run slow?

Apologies if this is answered else where, but I can't find any answers.
I have a MBP running OSX 10.6.8. Connected to it as a Time Machine is a Freecom 400GB 28147 uk, external hardrive connected over USB 2.0. I also have a Mac Mini running 10.6.8.
When connected to my MBP, I have found that it is extremely slow to read files. I gave up using it for Time Machine a while ago as I thought there was a problem Time Machine software causing it to run slow. I have also tried to read the time machine backups through finder and they are still slow to read.
Today (don't know why i didn't do it before now) I plugged it in to my Mac Mini with USB 2.0 and found that I can read all the time machine files at lightning speed, far quicker than my MBP which can take 2-3 mins to open a folder. I have noticed that the hard drive doesn't make its usual whurring noise when im trying to open a folder using the MBP, right up until the last minute before the folder opens.
Does any one have any idea about what might be causing the problem when the the ext HDD is connected to my MBP?
Any thoughts or suggestions greatly appreciated.

larryfromjackson wrote:
I'm backing up to a Drobo with four 2-Gig drives.
How are you connected to it? Network problems could explain at least some of what you're seeing.
More often then not I don't know how long the backups take because when it becomes to annoying I stop the backup.
That guarantees that Time Machine will have to do a "deep scan" the next time, comparing everything on your system to the backups. That does take a while, but if there are no other problems shouldn't have a major impact on performance.
All of that said, I can't say for certain that there isn't something else going on. Generally the way I notice the slowdown is when my keyboard inputs come out screwy -- ingB instead of Bring, pplAication for Applicaton for example. When I know that this is happening I can work "around" it by typing the first letter, pausing for a second or two, then typing the remander. Does any of this ring an bells?
I've not heard of that specifically, but if you're connected to the Drobo wirelessly, and using a Bluetooth keyboard, there are reports of interference between the two. Try a wired keyboard temporarily, and/or different WIFI channels.

Why is time machine running slow?

I am suddendly experiencing problems with Time Machine. Time Machine seems to run very slow lately. Is there any reason for this? The disk I use is fine.

I am suddendly experiencing problems with Time Machine. Time Machine seems to run very slow lately. Is there any reason for this? The disk I use is fine.

HT1277 Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Ok; I'm not sure what you're doing. 36 hours is rather long. Seems like a new migration. Not what I intended.
Here's what I intended: from the newly-migrated and apparently-corrupt environment, create a new user, not related to any existing user, nor any migration-created user, or any other user for that matter. That is, use  > System Preferences > Users and Groups, authenticate yourself by clicking on the padlock, and then click the + and create a wholly new user. Then log in under that user and establish the mail access.
36 hours? I'm wondering if there's an error or an exceedingly slow network here? Or a really, really slow disk? Or a sick backup? (WiFi isn't the path I'd usually choose, either.)
Failing the attempted second migration, I'd try a different tactic. Does your existing (old) system work? If so, I'd bypass the backup and connect an external (scratch) USB disk drive to the (old) sstem and then boot and use Disk Utility booted from the installer DVD disk or boot and use Disk Utility from the recovery partition or booted from a recovery partition created on some other external storage (details here vary by the OS X version and what hardware you have), and perform a full-disk backup of your original internal disk to (scratch) external storage. (Make sure you get the source and target disks chosen correctly here; copying the wrong way — from the scratch disk to your existing disk — will clobber your data!) In esssence, this will clone your existing boot disk. Then dismount the (formerly-scratch) external disk, transfer it over to the new system, and use it as the source of the migration, by performing a fresh OS X installation on the new system.
Target Disk Mode is also sometimes an option for accessing the disk for a migration, but that requires the right cable, and requires systems that have the same external connection; newer MacBook Pro systems use Thunderbolt for this, and older systems tend to use FireWire. And I'm guessing you don't have compatible hardware.
The details here can and do vary by your OS X versions and your particular Mac systems — if you'll identify the specific models and hardware, somebody might be able to better tailor the above (fairly generic) sequence to your particular configuration.

Trouble with Time Machine (runs constantly). Erase and install?

Trouble with Time Machine (runs constantly). Tried re-installation (equivalent of archive install) of Snow Leopard. Time Machine still unable to complete a back-up. Erase and install recommended at Genius Bar. Have backed up data to external HD using Super Duper. Should be a bootable backup. Last successful backup through Time Machine was 6/1/11. Not sure if I can access this back-up if I erase and re-install.
Computer shipped with Tiger (7/2007). Have original disks. Now running Snow Leopard. So: erase HD, install Tiger, then update to Snow Leopard? Start-up from Tiger disks does not appear to work (starting up holding "C" key). Suggestions? Want very much to transfer data to new iMac, but do not want to carry bugs forward. Very nervous about erasing HD. And have the questions above about reinstalling system software.
Advice desired! Thanks.

Well if you can hold option and boot off the Superdupes clone and it works fine then you should be set to do what you need to do to the original boot drive.
Disconnect all drives and c boot off the Snow Leopard install disk, use Disk Utility to Erase > format HFS+ journaled your internal boot drive.
Quit and reinstall OS X Snow Leopard, setup (do not use Setup/Migration Assitant!) and update to 10.6.8
When you setup the new install, use the same hard drive name and user name as you did before.
Now the free iLife that came on the Tiger disks you won't get naturally, but you can pick them off the disk with the shareware program called Pacifist.
install your programs from fresh sources, this way you don't get the "crap" from the older setup.
Once your machine is up and going. Hook up the clone and transfer your user folders over manually. With iTunes just replace the whole folder. Because you kept the same user and boot drive name as before, the playlists should be fine.
Once your all peachy, take the opportunity to clone this new setup to a external drive, label and disconnect.
Make another clone for day to day, or week to week clone updates and your just a hold option boot away for recovery.
You know Superdupes and Carbon Copy Cloner both have auto-scedualing/updating ability, so you can leave them plugged in and it will perform a update so your clone stays fresh and recent.
But you should keep a clone timed back about a couple of weeks back just in case you install something bad and don't learn about it right away.

Time Machine Runs All Night...Every Night.

Ove the past month or so I've noticed Time Machine seems to be running (especially at night) any time I'm not actively using my MacBook. (When I'm using the MB it seemed to operate normally backing up every hour or so.)
I initally thought that after a year's worth of accumulated back ups, the Time Machine file was getting too large to efficiently manage. So, not needing all those backups I wiped the hard disk that contained the back ups and started from scratch. (I back up to a hard drive, via wifi, through an Airport Extreme.)
I also Verified/Repaired the disk through Disk Utility.
This seemed to help for a coupe of days, but eventually it was back to the same, Time Machine chugging along seemingly all night. And now, the MB was getting warm when it really should be mostly idle.
So, I did some more research and found this webpage below that suggested if all else fails do a "Full Reset of Time Machine". The proceedure involves deleting the Time Machine ".plist" file and resetting your preferences. Your back up files will stay intact.
http://pondini.org/TM/A4.html
Wow! This really did the trick! Time Machine no longer runs all night long, and even the hourly backups during the day seem to process much quicker. So, if your Time Machine seems to just constantly chug along when you think it should be idle - give this a try.
Thanks to Pondin for putting the info out there that really helped me......
As an aside.....
I'm fairly new to the world of "Mac". I've had this MacBook a little over a year. In that time I've had 3 issues with: IPhoto, Mail, and Time Machine. (The programs just started acting "wonky".)
All these issues were fixed by deleting a ".plist" file (or a group of ".plist" files).
What are these ".plist" files and why are they always getting corrupted? Is this common? Am I doing something wrong? Is there anything I can do to make the files a little more roubust and keep them from getting corrupted?
Seems like one goes bad every 4-months and takes the app down with it.
Q.

Noelle Buscher wrote:
I dont recall this problem a month ago when I first got the Time Capsule. I do remember seeing the Time Machine running quite a bit, but it didnt affect my performance (at least not to the degree that I was going up and turning it off all the time)
Opening a webpage...takes about 10-15 seconds. Of course, I look up at the Time Machine and it is running. Opening a file takes forever...ESPECIALLY a Photoshop or other large file. Time Machine is running.
I will STOP the back-up so I can get something accomplishes...but ultimately have to go up and just turn it off completely, as it starts running again shortly.
Is there a setting for only running a backup once a day? I cant find it.
No, as Time Machine is designed to run hourly, and ordinarily works best that way.
You've clearly got something else going on here. I'd recommend starting by doing a +*Repair Disk+* on the sparse bundle. See #A5 in the Time Machine - Troubleshooting *User Tip,* also at the top of the +Time Machine+ forum.
If that doesn't help, try all the things in #D2 there.
Once you get it doing regular backups, see if the size makes sense considering the amount of changes you think you've made. If the backups seem too large, see #D4 in the Troubleshooting Tip. You may have an app that's causing extra-large (and therefore lengthy) backups.

Time Machine WIFI slows down and Fine after I unplug it?

My Time Machine WIFI slows down to an absolute crawl and then after I unplug it and plug it back in, it's back to normal. Can someone help me?

My Time Machine WIFI slows down to an absolute crawl and then after I unplug it and plug it back in, it's back to normal.
This is a classic case of the effects of wireless interference from other networks around you. See the link at the bottom for more information about this.
It might first help to understand why things improve when you unplug the Time Capsule and then power it back up. When you do this, the Time Capsule will scan to find the best available wireless channels to use at the time.
Unfortunately, other wireless routers are doing the same thing all the time, so after a few hours or a day or two, the channel(s) that the Time Capsule was using become overcrowded and the wireless slows down to a crawl. Cordless phones can also create interference issues for a wireless network as well as any number of other electronic devices.
Unless you can convince other users around you to turn off their wireless routers, there is not much that you are going to be able to do to come up with a permanent fix. For now, locate the Time Capsule as far away from any outside walls in your home as possible and use the 5 GHz band for as many connections as you can.
A friend of mine who recently moved into a new apartment complex has the same problem. He has to restart his wireless router at least twice a day, sometimes more on the weekends. Too many wireless networks.....not enough channels.
Wi-Fi and Bluetooth: Potential sources of wireless interference - Apple Support

Time machine works slow

After updating to Mavericks the finder started working really slowly, bugging and I also hava problems with time machine - the sistem starts to make a backup copy it goes too slow... for a night it can copy only 1-2mb of 500gb?
any ideas how to solve that problem?

Hello stoyanvassev,
Thanks for using Apple Support Communities.
For more information on this, take a look at:
OS X Mavericks: If Time Machine is slow
http://support.apple.com/kb/PH14169
Best of luck,
Mario

Time machine extreme slow

since i updated to maverics, the timemachine and the finder are extremly slowly, i mean realy much slowlier than "microsoft-speed". But i checked it again, i closed my MBP an found the white apple on it´s top..... its an apple. In different forums i read, that its a problem with spotlight. The backup with 4.87 GB is now, after 3 hours an 44 minutes at 3.84 GB.
Even Microsoft is faster.
can anyone help me?

Hello Bastlbeda,
Thank you for using Apple Support Communities.
For more information, take a look at:
OS X Mavericks: If Time Machine is slow
http://support.apple.com/kb/PH14169?viewlocale=en_US
Have a nice day,
Mario

Do I need to have "Time Machine" running in the background all the time or can I turn it off and on say once a week?

Do I need to have "Time Machine" running in the background all the time or can I turn it off and on say, once a week?

Robert Kempner wrote:
Do I need to have "Time Machine" running in the background all the time ...
It is how it is designed to be used. How Time Machine Works its Magic
Robert Kempner wrote:
... can I turn it off and on say, once a week?
Why..?
Perhaps TM is not for you... See Time Machine vs. Clones and Archives
More Info here > http://www.reedcorner.net/guides/backups/ch2.php

Time Machine Running Very Slow After Repairing Permission under "get info"

Hi,
I have a timemachine backup external hard drive which had permissions problem (perhaps this is because I crossed over from 10.5 to 10.6 at some point?) When I enter timemachine some files had that red minus sign beside it and told me "you don't have permission to access its content", and this problem was not with all files but with some of files and folders scattered all over my backed up 500GB data.
This created a problem and i wasn't gonna go in and open "get info" for each folder and go under sharing & permissions to manually fix it to read & write (and I believe some files didn't even allow me to do this)
Now here is the real concern. What I did without thinking is I right clicked on the external hard drive in the finder and opened the "get info" window and went down to the sharing and permissions. At first I fixed all privileges to "read & write" by unlocking the lock, but this still didn't fix all restrictions on accessing files and folders.
So instead I clicked on the icon which appears to be a "gear" and selected the "apply to enclosed items" and ran this operation on my whole 2TB hard drive. This of course took over 12 hours as far as I can remember. And I think in some forum it said this can create a problem? (Granting permissions to some system related files which can cause critical problems perhaps)
I also think this action I took has caused the time machine external hard drive to run slow in almost every way. My question I guess is, is there a way to revert my action of clicking on the gear and running the "apply to enclosed items"? Or perhaps another fix?
I have no idea on how to go onwards from here and worried that if I continue using this all-permissions-altered 2TB hard drive that it will create a huge problem in the future.
Any advise from senior members and/or members who encountered such situations would be greatly appreciated.
Thanks in advance,
Norio

Do not attempt to change the permissions on your backups.
And the problem you are having, on Lion, is far different from these old Leopard threads.
Please browse and/or search for similar threads in the Lion forum: https://discussions.apple.com/community/mac_os/mac_os_x_v10.7_lion?view=discussi ons#/

Time Machine Running VERY SLOW

I am using a 2 TB G-Drive for Time Machine.
I've been getting "disk full" messages for some time and the drive is is currently showing 47 GB free.
Today (at least that's the first I noticed it,) Time Machine is running VERY SLOW.
Looking at the drive the light with flash bright about once every 3 or 4 seconds.
Looking at the Time Machine status, it has been trying to backup 30 GB for several hours and has only backed up less than 10 GB.
My question is could this be caused by the drive being full or could it be the drive is about to go out.
In either case, if I get a new (larger) drive, will I be able to retrieve older files from this drive if necessary?
Thanks in advance.
Chuck

I finally re-booted at about 4:20 PM which seemed to clear up the issue, so this may be moot.
Here is the log:
12/19/12 2:40:32.786 PM WindowServer[78]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04273580 device: 0x100d29320 isBackBuffered: 1 numComp: 3 numDisp: 3
12/19/12 2:40:32.800 PM WindowServer[78]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x1b563241 device: 0x100d29d30 isBackBuffered: 1 numComp: 3 numDisp: 3
12/19/12 2:40:41.887 PM lsboxd[626]: @AE relay 4755524c:4755524c
12/19/12 2:43:24.256 PM Bento[93709]: Warning: Already had a model for IP9_RKAlbum with uuid: recoveredPhotosAlbum in cache.
12/19/12 2:45:15.805 PM mDNSResponder[46]: Double NAT (external NAT gateway address 192.168.1.88 is also a private RFC 1918 address)
12/19/12 2:54:14.856 PM com.apple.backupd[92721]: Copied 9.45 GB of 27.59 GB, 2762 of 2762 items
12/19/12 3:00:15.823 PM mDNSResponder[46]: Double NAT (external NAT gateway address 192.168.1.88 is also a private RFC 1918 address)
12/19/12 3:07:23.000 PM kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
12/19/12 3:07:23.657 PM com.apple.SecurityServer[15]: Killing auth hosts
12/19/12 3:07:23.657 PM com.apple.SecurityServer[15]: Session 100639 destroyed
12/19/12 3:07:23.000 PM kernel[0]: macx_swapon SUCCESS
12/19/12 3:07:23.718 PM com.apple.SecurityServer[15]: Session 100649 created
12/19/12 3:07:25.704 PM Notes[93810]: [IMAP] Expected untagged initial response from mail.brennaman-photo.com
12/19/12 3:07:25.795 PM Notes[93810]: [IMAP] Expected untagged initial response from pop.att.yahoo.com
12/19/12 3:07:25.843 PM Notes[93810]: [IMAP] Expected untagged initial response from pop.att.yahoo.com
12/19/12 3:07:41.000 PM kernel[0]: Sandbox: sandboxd(93819) deny mach-lookup com.apple.coresymbolicationd
12/19/12 3:07:47.266 PM sandboxd[93819]: ([93817]) mdworker(93817) deny file-write-owner /Users/Chuck/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.stor edata-wal (import fstype:hfs fsflag:480D000 flags:240000005F diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 2479915)
12/19/12 3:07:47.670 PM sandboxd[93819]: ([93817]) mdworker(93817) deny file-write-owner /Users/Chuck/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.stor edata-shm (import fstype:hfs fsflag:480D000 flags:240000005F diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 2479915)
12/19/12 3:08:26.326 PM Notes[93810]: [<_LibSasl2SASLClient: 0x7f92d2e022c0> mechanism: PLAIN security layer: no] Failed a step of SASL authentication
SASL(-1): generic failure:
12/19/12 3:08:51.955 PM com.apple.ShareKitHelper[40510]: --warning: [ShareKit-XPC] Received XPC_ERROR_CONNECTION_INVALID
12/19/12 3:08:51.956 PM com.apple.ShareKitHelper[40510]: --warning: [ShareKit-XPC] connectionWithClientInterrupted
12/19/12 3:08:51.956 PM com.apple.ShareKitHelper[40510]: --warning: [ShareKit] Cancel UI for running services with Client PID: 93810
12/19/12 3:10:00.000 PM kernel[0]: Sandbox: sandboxd(93833) deny mach-lookup com.apple.coresymbolicationd
12/19/12 3:10:00.768 PM sandboxd[93833]: ([93832]) mdworker(93832) deny file-write-owner /Users/Chuck/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.stor edata-wal (import fstype:hfs fsflag:480D000 flags:240000005F diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 2480117)
12/19/12 3:10:01.376 PM sandboxd[93833]: ([93832]) mdworker(93832) deny file-write-owner /Users/Chuck/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.stor edata-shm (import fstype:hfs fsflag:480D000 flags:240000005F diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 2480117)
12/19/12 3:10:20.970 PM mdworker[93701]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
12/19/12 3:11:23.000 PM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=93847[GoogleSoftwareUp] clearing CS_VALID
12/19/12 3:15:15.841 PM mDNSResponder[46]: Double NAT (external NAT gateway address 192.168.1.88 is also a private RFC 1918 address)
12/19/12 3:30:15.858 PM mDNSResponder[46]: Double NAT (external NAT gateway address 192.168.1.88 is also a private RFC 1918 address)
12/19/12 3:43:48.462 PM WindowServer[78]: CGXDeferSurfaces : Invalid source window 6476
12/19/12 3:43:48.462 PM WindowServer[78]: CGXDeferSurfaces : Invalid source window 6475
12/19/12 3:43:48.462 PM WindowServer[78]: CGXDeferSurfaces : Invalid source window 6474
12/19/12 3:43:48.462 PM WindowServer[78]: CGXDeferSurfaces : Invalid source window 6473
12/19/12 3:45:15.876 PM mDNSResponder[46]: Double NAT (external NAT gateway address 192.168.1.88 is also a private RFC 1918 address)
12/19/12 3:48:34.247 PM WindowServer[78]: CGXDeferSurfaces : Invalid source window 6506
12/19/12 3:48:48.000 PM kernel[0]: firefox (map: 0xffffff8035a0d4d8) triggered DYLD shared region unnest for map: 0xffffff8035a0d4d8, region 0x7fff90a00000->0x7fff90c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
12/19/12 3:48:55.833 PM lsboxd[626]: @AE relay 4755524c:4755524c
12/19/12 3:53:18.000 PM kernel[0]: firefox (map: 0xffffff8035a0d4d8) triggered DYLD shared region unnest for map: 0xffffff8035a0d4d8, region 0x7fff90a00000->0x7fff90c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
12/19/12 3:53:26.182 PM System Preferences[94039]: Cannot setMachineString without first being authenticated
12/19/12 3:53:26.237 PM System Preferences[94039]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
12/19/12 3:53:26.238 PM System Preferences[94039]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
12/19/12 3:53:26.256 PM System Preferences[94039]: *** WARNING: -[NSImage compositeToPoint:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
12/19/12 3:53:26.257 PM System Preferences[94039]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
12/19/12 3:53:39.518 PM System Preferences[94039]: Could not connect the action warnCullingPressed: to target of class TMOptionsSheetController
12/19/12 3:53:39.519 PM System Preferences[94039]: Could not connect the action backUpOnBatteryPowerPressed: to target of class TMOptionsSheetController
12/19/12 3:54:17.868 PM com.apple.backupd[92721]: Copied 11.33 GB of 27.59 GB, 2762 of 2762 items
12/19/12 3:55:33.000 PM kernel[0]: VirtualBoxVM (map: 0xffffff8032d07960) triggered DYLD shared region unnest for map: 0xffffff8032d07960, region 0x7fff90a00000->0x7fff90c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
12/19/12 3:56:10.000 PM kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.
12/19/12 3:56:15.000 PM kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.
12/19/12 3:56:23.831 PM VirtualBoxVM[94051]: -_continuousScroll is deprecated for NSScrollWheel. Please use -hasPreciseScrollingDeltas.
12/19/12 3:56:23.832 PM VirtualBoxVM[94051]: -deviceDeltaX is deprecated for NSScrollWheel. Please use -scrollingDeltaX.
12/19/12 3:56:23.832 PM VirtualBoxVM[94051]: -deviceDeltaY is deprecated for NSScrollWheel. Please use -scrollingDeltaY.
12/19/12 3:57:50.000 PM kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.
12/19/12 4:00:15.894 PM mDNSResponder[46]: Double NAT (external NAT gateway address 192.168.1.88 is also a private RFC 1918 address)
12/19/12 4:01:04.000 PM kernel[0]: Sandbox: sandboxd(94070) deny mach-lookup com.apple.coresymbolicationd
12/19/12 4:01:09.123 PM sandboxd[94070]: ([94063]) mdworker(94063) deny file-read-xattr /Users/Chuck/Library/Caches/Firefox/Profiles/ac442cpf.default/safebrowsing-to_d elete (pre-plugin fstype:hfs fsflag:480D000 flags:250000004C diag:0 uti:public.folder plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 2481004)
12/19/12 4:10:06.000 PM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=94128[GoogleSoftwareUp] clearing CS_VALID
12/19/12 4:10:39.938 PM com.apple.usbmuxd[67841]: _handle_timer heartbeat detected detach for device 0x78-10.0.0.15:0!
12/19/12 4:15:15.911 PM mDNSResponder[46]: Double NAT (external NAT gateway address 192.168.1.88 is also a private RFC 1918 address)
12/19/12 4:18:52.000 PM kernel[0]: firefox (map: 0xffffff8032d060e8) triggered DYLD shared region unnest for map: 0xffffff8032d060e8, region 0x7fff90a00000->0x7fff90c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
12/19/12 4:18:54.297 PM WindowServer[78]: CGXDeferSurfaces : Invalid source window 6463
12/19/12 4:18:54.297 PM WindowServer[78]: CGXDeferSurfaces : Invalid source window 6306
12/19/12 4:18:54.297 PM WindowServer[78]: CGXDeferSurfaces : Invalid source window 6191
12/19/12 4:19:01.256 PM com.apple.backupd[92721]: Copied 2762 files (12.21 GB) from volume Macintosh HD.
12/19/12 4:19:12.920 PM com.apple.launchd.peruser.501[265]: (com.apple.PackageKit.InstallStatus) Throttling respawn: Will start in 7 seconds
12/19/12 4:19:14.886 PM WindowServer[78]: dict count after removing entry for window 0x33 is 0
12/19/12 4:19:14.968 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:14.968 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:14.969 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:14.969 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:14.969 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:14.974 PM com.apple.launchd.peruser.501[265]: ([0x0-0x5987982].com.apple.MassStorageCamera[75489]) Exited: Killed: 9
12/19/12 4:19:14.990 PM mds[45]: (Error) Server: ==== XPC handleXPCMessage XPC_ERROR_CONNECTION_INVALID
12/19/12 4:19:15.082 PM coreservicesd[79]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=159
12/19/12 4:19:15.085 PM coreservicesd[79]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=174
12/19/12 4:19:15.086 PM coreservicesd[79]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=174
12/19/12 4:19:15.087 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.087 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.088 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.088 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.088 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.089 PM coreservicesd[79]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=113
12/19/12 4:19:15.089 PM coreservicesd[79]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=44890
12/19/12 4:19:15.122 PM coreservicesd[79]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=61322
12/19/12 4:19:15.123 PM com.apple.launchd[1]: (com.apple.ShareKitHelper[40510]) Exited: Killed: 9
12/19/12 4:19:15.343 PM coreservicesd[79]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=140
12/19/12 4:19:15.344 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.344 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.344 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.344 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.344 PM WindowServer[78]: CGXGetConnectionProperty: Invalid connection 36611
12/19/12 4:19:15.591 PM loginwindow[49]: sendQuitEventToApp (Image Capture Extension): AESendMessage returned error -1712
12/19/12 4:19:15.592 PM com.apple.launchd.peruser.501[265]: ([0x0-0x27027].com.apple.AppleSpell[630]) Exited: Terminated: 15
12/19/12 4:19:15.593 PM com.apple.launchd.peruser.501[265]: ([0x0-0xc5d55c9].com.apple.iTunesHelper[67878]) Exited with code: 1
12/19/12 4:19:15.593 PM com.apple.launchd.peruser.501[265]: (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[94152]) Exited: Killed: 9
12/19/12 4:19:15.702 PM com.apple.launchd.peruser.501[265]: ([0x0-0x1a01a].com.apple.ImageCaptureExtension2[365]) Exited: Terminated: 15
12/19/12 4:19:15.807 PM com.apple.launchd.peruser.501[265]: (com.apple.storeagent[48126]) Exited: Killed: 9
12/19/12 4:19:17.162 PM loginwindow[49]: DEAD_PROCESS: 49 console
12/19/12 4:19:17.499 PM com.apple.backupd[92721]: Stopping backup to allow backup destination disk to be unmounted or ejected.
12/19/12 4:20:21.000 PM bootlog[0]: BOOT_TIME 1355955621 0

Why is my Time Machine running so slow?

I am curious why my Time Machine backup is running so slow. I am trying to backup 52.85 GB. I am currently at 17.65 GB and it has taken about 6 hours. The Time Machine "meter" that shows how long it is going to take to finish the backup is telling me it estimates about 14 hours. Thirty minutes it was telling me it was going to take about 12 hours. Now 14? What's the deal? It seems to me the backup is taking way too long. What is puzzling was that the first 15 GBs or so were prett fast. You could actually see the download happening. Now it seems like the meter is stuck and not moving. Inerimittently, the meter will change the number of files yet to be backed up. Can anyone shed some light as to what might be happening.
Thanks!
Edward

I've followed many of the suggestions on this thread (except upgrading to Mountain Lion). My Time Machine and computer has been going for eight days straight backing up 580 gigs and last night there were 30 gigs to go! Something happened and in the middle of the night the computer crashed. I restarted the computer and external harddrive that I use for my Time Machine this morning and continued the backing up of 35.24 gigs. Except now the status window tells me it will take 9,624 days to back up!
I ran the diagnostic command prompt:
sudo tmdiagnose
And here are some of the results (I did not include the lines that identify my computer name and self-identifying info; also a zip file was generated by I did not include it because it is almost 3 megs):
2013-11-09 09:27:43.038 tmdiagnose[864:2303] Executing '/usr/bin/fs_usage -w'...
2013-11-09 09:27:53.069 tmdiagnose[864:2303] Executing '/usr/bin/top -l 10'...
2013-11-09 09:28:04.859 tmdiagnose[864:2303] Sampling 'backupd'...
2013-11-09 09:28:11.385 tmdiagnose[864:2303] Sampling 'mtmd'...
2013-11-09 09:28:11.451 tmdiagnose[864:2303] Sampling 'mtmfs'...
2013-11-09 09:28:11.517 tmdiagnose[864:2303] Sampling 'Finder'...
2013-11-09 09:28:20.769 tmdiagnose[864:2303] Executing '/bin/ls -la /Volumes/'...
2013-11-09 09:28:20.898 tmdiagnose[864:2303] Executing '/bin/df -H'...
2013-11-09 09:28:20.964 tmdiagnose[864:2303] Executing '/sbin/mount'...
2013-11-09 09:28:21.030 tmdiagnose[864:2303] Executing '/usr/sbin/diskutil list'...
2013-11-09 09:28:21.288 tmdiagnose[864:2303] Executing '/usr/sbin/diskutil cs list'...
2013-11-09 09:28:21.354 tmdiagnose[864:2303] Executing '/bin/bash -c /usr/sbin/diskutil list | /usr/bin/awk '/disk/ {system("/usr/sbin/diskutil info "$NF); print "*********************"}''...
2013-11-09 09:28:29.019 tmdiagnose[864:2303] Executing '/usr/bin/hdiutil info'...
2013-11-09 09:28:29.284 tmdiagnose[864:2303] Executing '/usr/sbin/netstat -aW -p tcp'...
2013-11-09 09:28:47.321 tmdiagnose[864:2303] Executing '/bin/bash -c /bin/ps auxc | /usr/bin/awk '/mtmd/ {system("lsof -p "$2); print("\n\n")}''...
2013-11-09 09:28:47.478 tmdiagnose[864:2303] Executing '/bin/bash -c /bin/ps auxc | /usr/bin/awk '/mtmfs/ {system("lsof -p "$2); print("\n\n")}''...
2013-11-09 09:28:47.570 tmdiagnose[864:2303] Executing '/usr/sbin/ioreg -ls -w 0'...
2013-11-09 09:28:56.096 tmdiagnose[864:2303] Gathering system diagnostic logs for 'backupd'...
2013-11-09 09:28:56.103 tmdiagnose[864:2303] Gathering system diagnostic logs for 'mtmd'...
2013-11-09 09:28:56.104 tmdiagnose[864:2303] Gathering system diagnostic logs for 'mtmfs'...
2013-11-09 09:28:56.105 tmdiagnose[864:2303] Gathering system diagnostic logs for 'mds'...
2013-11-09 09:28:56.111 tmdiagnose[864:2303] Gathering system diagnostic logs for 'Locum'...
2013-11-09 09:28:56.112 tmdiagnose[864:2303] Gathering system diagnostic logs for 'diskimages-helper'...
2013-11-09 09:28:56.113 tmdiagnose[864:2303] Gathering system diagnostic logs for 'newfs_hfs'...
2013-11-09 09:28:56.114 tmdiagnose[864:2303] Gathering system diagnostic logs for 'NetAuthSysAgent'...
2013-11-09 09:28:56.115 tmdiagnose[864:2303] Gathering system diagnostic logs for 'Finder'...
2013-11-09 09:28:56.116 tmdiagnose[864:2303] Gathering system diagnostic logs for 'Locum'...
2013-11-09 09:28:56.117 tmdiagnose[864:2303] Gathering system diagnostic logs for 'System Preferences'...
2013-11-09 09:28:56.126 tmdiagnose[864:2303] Gathering system diagnostic logs for 'SystemUIServer'...
2013-11-09 09:28:56.127 tmdiagnose[864:2303] Gathering system diagnostic logs for 'iPhoto'...
2013-11-09 09:28:56.128 tmdiagnose[864:2303] Gathering system diagnostic logs for 'MailTimeMachineHelper'...
2013-11-09 09:28:56.129 tmdiagnose[864:2303] Gathering system diagnostic logs for 'Address Book'...
2013-11-09 09:28:56.130 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'Finder'...
2013-11-09 09:28:56.294 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'Locum'...
2013-11-09 09:28:56.318 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'System Preferences'...
2013-11-09 09:28:56.343 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'SystemUIServer'...
2013-11-09 09:28:56.366 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'iPhoto'...
2013-11-09 09:28:56.391 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'MailTimeMachineHelper'...
2013-11-09 09:28:56.416 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'Address Book'...
2013-11-09 09:28:58.687 tmdiagnose[864:4303] Executing '/usr/sbin/system_profiler -xml SPParallelATADataType SPAirPortDataType SPBluetoothDataType SPDiagnosticsDataType SPEthernetDataType SPFibreChannelDataType SPFireWireDataType SPFirewallDataType SPHardwareDataType SPHardwareRAIDDataType SPNetworkLocationDataType SPManagedClientDataType SPMemoryDataType SPNetworkDataType SPPowerDataType SPSerialATADataType SPSoftwareDataType SPUSBDataType'...
2013-11-09 09:29:14.646 tmdiagnose[864:4303] Gathering host information...
2013-11-09 09:29:14.649 tmdiagnose[864:4303] Getting Time Machine configuration...
2013-11-09 09:29:14.984 tmdiagnose[864:4303] Executing '/bin/bash -c /bin/launchctl list | /usr/bin/grep -e 'PID' -e 'com.apple.mtm' -e 'com.apple.backup' -e 'com.apple.TMLaunchAgent''...
2013-11-09 09:29:15.052 tmdiagnose[864:2303] Making backup disk available...
2013-11-09 09:29:15.086 tmdiagnose[864:4303] Building classic Time Machine snapshot skeletons...
2013-11-09 09:29:16.675 tmdiagnose[864:4303] Executing '/bin/ls -lde /Volumes/TimeMachine/Backups.backupdb/.spotlight_repair'...
2013-11-09 09:29:16.741 tmdiagnose[864:4303] Executing '/usr/bin/xattr -l /Volumes/TimeMachine/Backups.backupdb/.spotlight_repair'...
2013-11-09 09:29:17.523 tmdiagnose[864:4303] Executing '/bin/ls -lde /Volumes/TimeMachine/Backups.backupdb/.spotlight_temp'...
2013-11-09 09:29:17.589 tmdiagnose[864:4303] Executing '/usr/bin/xattr -l /Volumes/TimeMachine/Backups.backupdb/.spotlight_temp'...
013-11-09 09:29:17.788 tmdiagnose[864:4303] Executing '/bin/ls -l /Volumes/TimeMachine/Backups.backupdb/.spotlight_repair'...
2013-11-09 09:29:18.614 tmdiagnose[864:4303] Executing '/bin/ls -l /Volumes/TimeMachine/Backups.backupdb/.spotlight_temp'...
2013-11-09 09:29:19.392 tmdiagnose[864:4303] Building Mobile Time Machine overlay snapshot skeletons...
2013-11-09 09:29:19.393 tmdiagnose[864:4303] Building Mobile Time Machine delta store snapshot skeletons...
2013-11-09 09:29:19.505 tmdiagnose[864:2303] Gathering information about reachable AirPort devices...
2013-11-09 09:29:49.509 tmdiagnose[864:2303] unable to locate any Bonjour services within 30 seconds
2013-11-09 09:29:49.540 tmdiagnose[864:2303] Executing '/usr/bin/mddiagnose -h'...
2013-11-09 09:29:49.708 mddiagnose[974:707] Executing '/usr/bin/sw_vers'...
2013-11-09 09:29:49.776 mddiagnose[974:707] Getting system version...
2013-11-09 09:29:49.778 mddiagnose[974:707] Executing '/usr/bin/arch'...
2013-11-09 09:29:49.865 mddiagnose[974:707] Executing '/usr/bin/what /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mds'...
2013-11-09 09:29:49.866 mddiagnose[974:707] Executing '/usr/bin/what /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Metadata'...
2013-11-09 09:29:49.867 mddiagnose[974:707] Executing '/usr/bin/top -l 2 -s 2'...
2013-11-09 09:29:54.050 mddiagnose[974:707] Executing '/bin/df -H'...
2013-11-09 09:29:54.117 mddiagnose[974:707] Executing '/bin/ls -la /Volumes/'...
2013-11-09 09:29:54.184 mddiagnose[974:707] Executing '/sbin/mount'...
2013-11-09 09:29:54.251 mddiagnose[974:707] Executing '/usr/bin/vmmap -resident -w mds'...
2013-11-09 09:29:54.761 mddiagnose[974:707] Executing '/usr/bin/heap mds'...
2013-11-09 09:29:55.018 mddiagnose[974:707] Executing '/usr/local/bin/ddt mds'...
2013-11-09 09:29:55.166 mddiagnose[974:707] Sampling 'mds'...
2013-11-09 09:30:01.114 mddiagnose[974:707] Spindumping 'mds'...
2013-11-09 09:30:08.686 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/TimeMachine/Backups.backupdb/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:08.753 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/TimeMachine/Backups.backupdb/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:08.823 mddiagnose[974:707] Executing '/usr/bin/find /.MobileBackups/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:08.890 mddiagnose[974:707] Executing '/usr/bin/find /.MobileBackups/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:08.958 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/TimeMachine/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:23.311 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/TimeMachine/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:23.570 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Video/.MobileBackups/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:23.637 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Video/.MobileBackups/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:23.705 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/IPOD/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:23.772 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/IPOD/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:23.841 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Video/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:23.971 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Video/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:24.041 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Audio/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:24.297 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Audio/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'..
2013-11-09 09:30:24.816 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Photo/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:24.946 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Photo/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:25.077 mddiagnose[974:707] Executing '/usr/bin/find //.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:25.207 mddiagnose[974:707] Executing '/usr/bin/find //.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:35.454 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Audio/Backups.backupdb/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:35.520 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Audio/Backups.backupdb/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:35.587 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Photo/.MobileBackups/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:35.654 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Photo/.MobileBackups/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:35.951 mddiagnose[974:707] Executing '/usr/bin/find / -name .metadata_never_index -maxdepth 1'...
2013-11-09 09:30:36.018 mddiagnose[974:707] Executing '/usr/bin/find /Volumes -name .metadata_never_index -maxdepth 2'...
2013-11-09 09:30:36.590 mddiagnose[974:707] Getting crash logs for 'mds'...
2013-11-09 09:30:36.651 mddiagnose[974:707] Getting crash logs for 'mdworker'...
2013-11-09 09:30:36.652 mddiagnose[974:707] Getting crash logs for 'Spotlight'...

Time Machine running on Linksys WRT600n with external drive.

Hey Folks,
After searching the internet for the answer on how to setup OS X Time Machine on my Linksys WRT600n with storage link, and finding nothing or only parts of what I needed, I finally got it to work. Hopefully this will help you in your setup.(this should work for any linksys routers with storage link.)
1) First you will need to attach your external USB drive to the Linksys Router, and format it using the linksys utility. This will format the drive as fat32 so it can be access by the mac and the router.
2) You now need to create a share on the drive using the Linksys utility (I called mine "TimeMachine") and grant R&W permission to it. I found and article that said you have to create a group called "root" and a user called "root" within that group, then grant the group R&W access to you share. I did this but I am not sure if its required. you may be able to edit the default "admin" account.
3) Once you have the share created you should be able to access the share from your mac by logging into it using your (Linksys) "root" account and password. Make sure you can save a file here. You maybe able to create a folder but make sure you can save a file (.doc for example).
4) Apple has blocked the use of unsupported drives in Time machine so you will have to make a change for this to work. open a terminal window and type the following in one line:
defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1
Hit enter, and close terminal.
5) For some reason Time Machine will have issues creating the .sparse bundle Disk required for the backup over the network. So you will have to create it yourself. Safely unplug the USB drive from the router and plug it into your mac. Open disk utility (applications > utilities > disk utility) and create one the same size as your external drive.
parameters:
- Volume name: "Time Machine" (has to be this to work)
- Mac OS Extended (Journaled);
- No partition map
- sparse bundle disk image
Make sure the sparse bundle is in the share folder. If Time Machine had created this sparse bundle it would named it after your machine. You will have to rename it accordingly. This is the required format 'computername'_'mac address without colons'.sparsebundle
(eg. "joe's MacBook Pro_000000000000.sparsebundle")
6) Once all the above is complete you can reattach the drive to the router, and attach to the share again from your mac. Open Time Machine and you should see your share. Setup Time Machine to use this drive. You may want to be connected using Ethernet for the first backup as it may take a while.
I have found the wireless backup to take a bit of time to prepare and run but it seams to work nonetheless. The slowness could be caused by the difference in mac addresses from wired to wireless. So you may want to change the sparse bundle file name depending on how you are accessing time machine.
Hopefully this will work for you as it did for me.

I am afraid I have to pour some cold water on your enthusiasm.
Yes, what you say can get TimeMachine working, but there is a nasty snag:
WRT600N uses FAT32 for its external harddrives and (regretably) understands nothing else. FAT32 has two restrictions:
1) Maximum file size is 4GB
2) (a lesser-known one) Maximum number of files in a directory of 65,535.
The first restriction isn't really a problem because Time Machine organizes its data in 8MB "bands", which are files within your sparsebundle directory.
The second restriction, however, will cause Time Machine to eventually hit a brick wall: The sparsebundle bands are given a sequence number in hexadecimal and there isn't really a limit to how many you can have. If you run Time Machine on a large harddrive attached to the WRT600N, you will eventually run into a situation where you are hitting the 65,535-files-in-a-directory limit. Time Machine will, therefore, run for a while and then suddenly fail for no apparent reason.
Given the parameters of Time Machine, you can't run Time Machine reliably on a WRT600N with an external harddrive larger than 8MB * 65535 = 512GB. If that's good enough for you, then great. If not, you can do one of two things:
1) Get something that doesn't format its harddrive in FAT32.
2) Install DD-WRT on your router (thus voiding its warranty), fight with it for a while in order to get SAMBA running on it, and gain the ability to format your harddrive in Ext2.
I hope this helps somebody.

Time machine running slow

Similar Messages

Maybe you are looking for