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

Similar Messages

Time machine extremely slow and size of backup keeps increasing. please help!

I bougth a external hard drive form western digital, MyBook World Edition, and at first it was working fine, I make a first backup with time machine and it was perfect. last month when I entered time machine to check my backups they were all gone, and now I've been trying to make a new backup but it's moving really slow, like less then 2Gb per hour, and also it seems as it's over but them the size of the backup keeps changing (as soon as it reaches the whole size it gets bigger) Don't know what to do, I haven't changed anything in the system or anything.
The hard driver is connected to a router and I connect to it trhough my wireless network.
ps: sorry my bad english I'm not a native speaker.

UPDATE: It's now trying to do a backup of 31.7MB. It's stuck at 993KB (first it was stuck at 8 bytes, then at 87 bytes, then 88KB), but it took a really long time to get there. So now it looks like it's just slow no matter what. I haven't been keeping track, but it may have been stuck on 993KB now for around 40 minutes.

OS X 10.8 time machine extremely slow, then stops working

after upgrading to Mountain Lion yesterday, I decided to erase & reformated my external HD to use with Time Machine in order to start fresh. It is the same HD I've used for Time Maching backups for the past 2 years and has worked flawlessly. However, when I started the Time Machine backup, it was painfully slow indicating that it was going to take 37 days to backup by 49 GB. I thought it might pickup speed after a while, but instead it just stopped working, displaying the message something to the effect that "no time machine drive was attached".
Anyone else having issues with Time Machine backups under Mountain Lion? Any suggestions"
Thanks.

My problem resolved itself. Please see the link
https://discussions.apple.com/message/19226237#19226237

TIME MACHINE EXTREMELY SLOW. AS IN S-L-O-W.

configuration: 1 Raid internal hd of 1.8 TB, 1 TB backup internal hd using retrospect. 2TB external HD for time machine and copy of home file from
computer's hd. 650gb external hd with clone of computer's hd.
running Time Machine on a 650GB Lacie external hd via fw800 for 6-9 months.
ran out of space. dumped old backups. still needed more space.
moved 250GB of a video archive onto internal raid drives (1.8TB) and backed up
via retrospect to another internal 1TB drive.
made a clone of my computers HD onto the 650GB external drive.
ran time machine onto the new 2TB external drive. as no previous backups were
recognized i did a new first time backup to time machine which took approx 12 hours. made a copy of my home file from my computers HD onto that same external 2TB drive.
now time machine is running backups at 1GB per minute speed as if it is doing an initial backup again. it only used to run for a few minutes. what is happening?

You might want to try formatting your time machine drive and starting again. And yes Time Machine only copies the changes that are made. However, judging by your screen pic and the size of your hard drives, I would assume that you are in the movie business? Therefore I would bet that you deal with constantly changing movie files and pictures that are relatively quite large in size. Since these have "changed" they would be re backed up. Also since you are dealing with quite large quantities of data, it would only make sense that time machine would take a while. One thing you could try is in the time machine preferences pane, click on Options and tell time machine what you don't want to be backed up. I dunno how raid drives work but it might be possible that one of the clones that you created on those drives was backed up too.
Steve

Time Machine, extremely slow, about 1 MB /minute

Something is wrong - it's taking an eternity. I think I've seen it do this before. Any help appreciated.

See #D2 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).

Time machine extremely slow on Mavericks; Spotlight never finishes indexing...

Hi there.
I read tons of complaints about this issue, but I did not read any solution, so I am posting this hoping that some good soul can help me and many many others.
I am really careful about OXS upgrades, I have a Macbook Air 13" 4GB/256GB ssd, 2013. last monday I finally did the Mavericks upgrade; Mountain Lion was working great, but as Yosemite coming soon, I thought that was a good time to do it. Guess what...
Time Machine is NOT WORKING. I never had a problem with TM, and I use Mac since 90's, so I even can't remember when it came out, but I trade at least 4 Macs using TM and never had an issue.
Now, over Mavericks, it is taking forever. By just now, after almost 30 hours, it is backing up 8.57 GB of 60 GB. I already did the reformating of the TM's drive, it did not work.
I got a new HD external, reformatted on Disk Utility, turno ON and OFF and ON TIme Machine as I read it many times on other posts, and nothing...
It is justing taking forever.
I bever swa this on any other OSX.
Spotlight is indexing too, takng too long, and probably this is the reason (or one of the reasons...) for TM take so long.
I started over wifi, I have an Aiport Express Extended thing, but my Macbook is really close to the first one, on the chain. I made sure that airport is connectec to this one, and, it is.
I plugged my TrendNet USB-Ethernet cable, which works really great and fast.
Nothing changes, System Preferences recognizes both connections, wifi and ethernet, both are working, but speed did not change at all...
Any hint?
Any help?
Any solution?
I can't really believe that Apple will leave Time Machine users on this ridiculous situation.
But I can't figure it out what to do next.
Thanks a lot for any feedback,
cheers from Brazil,
Andre

I solved the problem...
Go to terminal and enter:
rm -f ~/Library/Preferences/com.apple.Spotlight.plist
This will delete the preferences file. Restart your computer and it should work. It did for me.

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

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.

Time Machine very slow when backup disk almost full

My Time Machine backups on a Time Capsule (first generation, 1 TB) have become extremely slow recently. The disk is almost full, but I don't think that should be a problem as Time Machine deletes the oldest backups by itself. It has been, so I don't think that in itself should cause a problem.
This becomes particularly annoying because whenever backups are going on, the system doesn't allow me to access the "Open" or "Save" dialogues - probably because it wants to check the Time Machine disk, but can't, or only can very slowly. Whenever I do this, the app in question just freezes.
Anyone else has this problem, and does anyone know a fix? I don't want to start a new backup if I can avoid it.

Florian M. wrote:
Thank you. Did that, and it seems to be working now - though it actually seemed to have got better even before I ran Disk Utility. Before, even rebooting didn't help.
Yes, if there's a problem inside he sparse bundle, rebooting (the Mac and/or TC) won't help.
Time Machine is a great technology, but it seems to have strange quirks sometimes
It does indeed!
Once again, thank you.
You're quite welcome, and thanks for the star!

Time Machine backups slowing down after 25 days

I am experiencing a peculiar kind of behaviour from Time Machine under
Mountain Lion (10.8.2). In the multiple threads on Time Machine issues,
I could not find this exact problem described so I am wondering if
anyone else has seen the same thing or even has a solution.
Like for many others, the basic symptom is that Time Machine becomes
extremely slow. In my case this always happens about 25 days after the
last reboot. I am using a Mid 2010 27-inch IMAC and a Mid 2010 Mac Pro,
both connected to a Time Capsule via ethernet. Both are showing the
same behaviour.
Originally I was letting Time Machine do its regular hourly backups,
this has now been changed to twice a day using TimeMachineEditor. The
change has made no difference, backups are still getting slow after
25 days. This is accompanied by kernel_task gradually ramping up
its CPU usage, from below a percent to several percent.
Here are the backupd entries from a "normal" backup:
This takes 3-4 min, which I find tolerable - although I
am always surprised by the rather large number of files that
are backed up even if the machine has remained idle:
May 18 18:00:00 myhost.nl com.apple.backupd[75338]: Starting manual backup
May 18 18:00:00 myhost.nl com.apple.backupd[75338]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 18 18:00:01 myhost.nl com.apple.backupd[75338]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 18 18:00:23 myhost.nl com.apple.backupd[75338]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 18 18:00:23 myhost.nl com.apple.backupd[75338]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 18 18:00:56 myhost.nl com.apple.backupd[75338]: Using file event preflight for Macintosh HD
May 18 18:01:07 myhost.nl com.apple.backupd[75338]: Will copy (9.2 MB) from Macintosh HD
May 18 18:01:07 myhost.nl com.apple.backupd[75338]: Found 1150 files (9.2 MB) needing backup
May 18 18:01:07 myhost.nl com.apple.backupd[75338]: 14.53 GB required (including padding), 1.74 TB available
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: Copied 3082 files (48.4 MB) from volume Macintosh HD.
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: Using file event preflight for Macintosh HD
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: Will copy (5.7 MB) from Macintosh HD
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: Found 18 files (5.7 MB) needing backup
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: 14.53 GB required (including padding), 1.74 TB available
May 18 18:03:07 myhost.nl com.apple.backupd[75338]: Copied 1415 files (5.7 MB) from volume Macintosh HD.
May 18 18:03:08 myhost.nl com.apple.backupd[75338]: Created new backup: 2013-05-18-180307
May 18 18:03:12 myhost.nl com.apple.backupd[75338]: Starting post-backup thinning
May 18 18:03:12 myhost.nl com.apple.backupd[75338]: No post-back up thinning needed: no expired backups exist
May 18 18:03:13 myhost.nl com.apple.backupd[75338]: Backup completed successfully.
May 18 18:03:18 myhost.nl com.apple.backupd[75338]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 18 18:03:18 myhost.nl com.apple.backupd[75338]: Ejected Time Machine network volume.
And here are the corresponding entries one day later, after the
25-day "limit" had been reached. Note that it takes about an
hour to backup a few MB! Larger backups, when I have actually
been using the computer, can take hours.
May 19 18:00:00 myhost.nl com.apple.backupd[82625]: Starting manual backup
May 19 18:00:01 myhost.nl com.apple.backupd[82625]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 19 18:00:01 myhost.nl com.apple.backupd[82625]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 19 18:17:13 myhost.nl com.apple.backupd[82625]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 19 18:17:15 myhost.nl com.apple.backupd[82625]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 19 18:19:10 myhost.nl com.apple.backupd[82625]: Using file event preflight for Macintosh HD
May 19 18:20:45 myhost.nl com.apple.backupd[82625]: Will copy (5 MB) from Macintosh HD
May 19 18:20:45 myhost.nl com.apple.backupd[82625]: Found 1092 files (5 MB) needing backup
May 19 18:20:46 myhost.nl com.apple.backupd[82625]: 14.54 GB required (including padding), 1.74 TB available
May 19 18:48:03 myhost.nl com.apple.backupd[82625]: Copied 3178 files (47.2 MB) from volume Macintosh HD.
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Using file event preflight for Macintosh HD
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Will copy (6 MB) from Macintosh HD
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Found 170 files (6 MB) needing backup
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: 14.54 GB required (including padding), 1.74 TB available
May 19 18:56:50 myhost.nl com.apple.backupd[82625]: Copied 1831 files (6 MB) from volume Macintosh HD.
May 19 18:56:56 myhost.nl com.apple.backupd[82625]: Created new backup: 2013-05-19-185651
May 19 18:57:39 myhost.nl com.apple.backupd[82625]: Starting post-backup thinning
May 19 19:00:52 myhost.nl com.apple.backupd[82625]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-05-18-180307 (48.4 MB)
May 19 19:00:52 myhost.nl com.apple.backupd[82625]: Post-back up thinning complete: 1 expired backups removed
May 19 19:00:57 myhost.nl com.apple.backupd[82625]: Backup completed successfully.
May 19 19:01:38 myhost.nl com.apple.backupd[82625]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 19 19:01:38 myhost.nl com.apple.backupd[82625]: Ejected Time Machine network volume.
I have now rebooted the machine, and things are back to normal.
In about 25 days, I fully expect that things will start to grind to
a halt again. On the MacPro, which has now been running for 16
days, things should be fine for another 9-10 days.

These are the messages from the first slow backup. This one was only marginally slower than a normal backup, but a sure sign that things were going awry nonetheless:
May 19 06:00:00 myhost.nl com.apple.backupd[79247]: Starting manual backup
May 19 06:00:00 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 06:00:00 myhost.nl com.apple.backupd[79247]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 19 06:00:00 myhost.nl com.apple.backupd[79247]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 19 06:00:00 myhost kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
May 19 06:00:00 myhost kernel[0]: AFP_VFS afpfs_mount: /Volumes/Backup, pid 79248
May 19 06:00:00 myhost kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80ee82d008 /Volumes/Backup (error = 0, retval = 0)
May 19 06:00:23 myhost.nl com.apple.backupd[79247]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 19 06:00:23 myhost.nl com.apple.backupd[79247]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 19 06:01:14 myhost.nl com.apple.backupd[79247]: Using file event preflight for Macintosh HD
May 19 06:01:28 myhost.nl com.apple.backupd[79247]: Will copy (36.7 MB) from Macintosh HD
May 19 06:01:28 myhost.nl com.apple.backupd[79247]: Found 411 files (36.7 MB) needing backup
May 19 06:01:28 myhost.nl com.apple.backupd[79247]: 14.57 GB required (including padding), 1.74 TB available
May 19 06:02:34 myhost.nl mdworker[79274]: Unable to talk to lsboxd
May 19 06:02:34 myhost.nl mdworker[79275]: Unable to talk to lsboxd
May 19 06:02:34 myhost.nl sandboxd[79276] ([79274]): mdworker(79274) deny mach-lookup com.apple.ls.boxd
May 19 06:02:34 myhost.nl sandboxd[79276] ([79275]): mdworker(79275) deny mach-lookup com.apple.ls.boxd
May 19 06:02:34 myhost kernel[0]: Sandbox: sandboxd(79276) deny mach-lookup com.apple.coresymbolicationd
May 19 06:04:02 myhost.nl netbiosd[76]: name servers down?
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: Copied 2912 files (77.9 MB) from volume Macintosh HD.
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: Using file event preflight for Macintosh HD
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: Will copy (5.6 MB) from Macintosh HD
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: Found 22 files (5.6 MB) needing backup
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: 14.54 GB required (including padding), 1.74 TB available
May 19 06:04:36 myhost.nl mdworker[79290]: Unable to talk to lsboxd
May 19 06:04:36 myhost.nl mdworker[79291]: Unable to talk to lsboxd
May 19 06:04:36 myhost.nl sandboxd[79292] ([79290]): mdworker(79290) deny mach-lookup com.apple.ls.boxd
May 19 06:04:36 myhost.nl sandboxd[79292] ([79291]): mdworker(79291) deny mach-lookup com.apple.ls.boxd
May 19 06:04:36 myhost kernel[0]: Sandbox: sandboxd(79292) deny mach-lookup com.apple.coresymbolicationd
May 19 06:04:49 myhost.nl com.apple.backupd[79247]: Copied 1424 files (5.6 MB) from volume Macintosh HD.
May 19 06:04:50 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 06:04:50 myhost.nl com.apple.backupd[79247]: Created new backup: 2013-05-19-060449
May 19 06:04:53 myhost.nl com.apple.backupd[79247]: Starting post-backup thinning
May 19 06:05:40 myhost.nl com.apple.backupd[79247]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-04-19-001551 (83 MB)
May 19 06:05:48 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=79313[GoogleSoftwareUp] clearing CS_VALID
May 19 06:06:04 myhost.nl com.apple.backupd[79247]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-05-17-180350 (48.9 MB)
May 19 06:06:04 myhost.nl com.apple.backupd[79247]: Post-back up thinning complete: 2 expired backups removed
May 19 06:06:04 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 06:06:04 myhost.nl com.apple.backupd[79247]: Backup completed successfully.
May 19 06:06:11 myhost.nl com.apple.backupd[79247]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 19 06:06:11 myhost.nl com.apple.backupd[79247]: Ejected Time Machine network volume.
May 19 06:06:11 myhost kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Backup, flags 0, pid 79318
May 19 06:06:11 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/Backup 0xffffff80ee82d008
May 19 06:06:11 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/Backup 0xffffff80ee82d008
May 19 06:06:11 myhost kernel[0]: AFP_VFS afpfs_unmount : afpfs_DoReconnect sent signal for unmount to proceed
Here is then the full log for the next backup, 12 hrs later (this is the one I posted earlier):
The message at 19:01:11 about mds not responding seems to be related to this. I have seen that a few times during these slow backups, but not otherwise.
May 19 18:00:00 myhost.nl com.apple.backupd[82625]: Starting manual backup
May 19 18:00:00 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 18:00:01 myhost.nl com.apple.backupd[82625]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 19 18:00:01 myhost.nl com.apple.backupd[82625]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 19 18:00:02 myhost kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
May 19 18:00:02 myhost kernel[0]: AFP_VFS afpfs_mount: /Volumes/Backup, pid 82627
May 19 18:00:02 myhost kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80ee853008 /Volumes/Backup (error = 0, retval = 0)
May 19 18:00:43 myhost.nl apsd[59]: <APSConnectionNotificationQueue: 0x7f7f51021020>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
May 19 18:01:13 --- last message repeated 2 times ---
May 19 18:02:35 myhost.nl mdworker[82632]: Unable to talk to lsboxd
May 19 18:02:35 myhost.nl sandboxd[82633] ([82632]): mdworker(82632) deny mach-lookup com.apple.ls.boxd
May 19 18:02:35 myhost kernel[0]: Sandbox: sandboxd(82633) deny mach-lookup com.apple.coresymbolicationd
May 19 18:02:56 myhost.nl netbiosd[76]: name servers down?
May 19 18:05:27 myhost.nl apsd[59]: <APSConnectionNotificationQueue: 0x7f7f51021020>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
May 19 18:05:57 --- last message repeated 2 times ---
May 19 18:11:33 myhost.nl mdworker[82687]: Unable to talk to lsboxd
May 19 18:11:33 myhost.nl sandboxd[82688] ([82687]): mdworker(82687) deny mach-lookup com.apple.ls.boxd
May 19 18:11:33 myhost kernel[0]: Sandbox: sandboxd(82688) deny mach-lookup com.apple.coresymbolicationd
May 19 18:15:33 myhost.nl netbiosd[76]: name servers down?
May 19 18:17:13 myhost.nl com.apple.backupd[82625]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 19 18:17:15 myhost.nl com.apple.backupd[82625]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 19 18:19:10 myhost.nl com.apple.backupd[82625]: Using file event preflight for Macintosh HD
May 19 18:20:33 myhost.nl mdworker[82745]: Unable to talk to lsboxd
May 19 18:20:34 myhost kernel[0]: Sandbox: sandboxd(82747) deny mach-lookup com.apple.coresymbolicationd
May 19 18:20:34 myhost.nl sandboxd[82747] ([82745]): mdworker(82745) deny mach-lookup com.apple.ls.boxd
May 19 18:20:45 myhost.nl com.apple.backupd[82625]: Will copy (5 MB) from Macintosh HD
May 19 18:20:45 myhost.nl com.apple.backupd[82625]: Found 1092 files (5 MB) needing backup
May 19 18:20:46 myhost.nl com.apple.backupd[82625]: 14.54 GB required (including padding), 1.74 TB available
May 19 18:29:35 myhost.nl netbiosd[76]: name servers down?
May 19 18:31:11 myhost.nl mdworker[82800]: Unable to talk to lsboxd
May 19 18:31:11 myhost.nl sandboxd[82801] ([82800]): mdworker(82800) deny mach-lookup com.apple.ls.boxd
May 19 18:31:11 myhost kernel[0]: Sandbox: sandboxd(82801) deny mach-lookup com.apple.coresymbolicationd
May 19 18:41:03 myhost.nl netbiosd[76]: name servers down?
May 19 18:41:15 myhost.nl mdworker[82847]: Unable to talk to lsboxd
May 19 18:41:15 myhost kernel[0]: Sandbox: sandboxd(82848) deny mach-lookup com.apple.coresymbolicationd
May 19 18:41:15 myhost.nl sandboxd[82848] ([82847]): mdworker(82847) deny mach-lookup com.apple.ls.boxd
May 19 18:48:03 myhost.nl com.apple.backupd[82625]: Copied 3178 files (47.2 MB) from volume Macintosh HD.
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Using file event preflight for Macintosh HD
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Will copy (6 MB) from Macintosh HD
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Found 170 files (6 MB) needing backup
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: 14.54 GB required (including padding), 1.74 TB available
May 19 18:49:02 myhost.nl netbiosd[76]: name servers down?
May 19 18:49:08 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=82886[GoogleSoftwareUp] clearing CS_VALID
May 19 18:51:55 myhost.nl mdworker[82911]: Unable to talk to lsboxd
May 19 18:51:56 myhost.nl sandboxd[82912] ([82911]): mdworker(82911) deny mach-lookup com.apple.ls.boxd
May 19 18:51:56 myhost kernel[0]: Sandbox: sandboxd(82912) deny mach-lookup com.apple.coresymbolicationd
May 19 18:56:50 myhost.nl com.apple.backupd[82625]: Copied 1831 files (6 MB) from volume Macintosh HD.
May 19 18:56:55 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 18:56:56 myhost.nl com.apple.backupd[82625]: Created new backup: 2013-05-19-185651
May 19 18:57:39 myhost.nl com.apple.backupd[82625]: Starting post-backup thinning
May 19 19:00:52 myhost.nl com.apple.backupd[82625]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-05-18-180307 (48.4 MB)
May 19 19:00:52 myhost.nl com.apple.backupd[82625]: Post-back up thinning complete: 1 expired backups removed
May 19 19:00:54 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 19:00:57 myhost.nl com.apple.backupd[82625]: Backup completed successfully.
May 19 19:01:11 myhost.nl diskarbitrationd[16]: mds [38]:16919 not responding.
May 19 19:01:38 myhost.nl com.apple.backupd[82625]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 19 19:01:38 myhost.nl com.apple.backupd[82625]: Ejected Time Machine network volume.
May 19 19:01:38 myhost kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Backup, flags 0, pid 82962
May 19 19:01:38 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/Backup 0xffffff80ee853008
May 19 19:01:38 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/Backup 0xffffff80ee853008
May 19 19:01:38 myhost kernel[0]: AFP_VFS afpfs_unmount : afpfs_DoReconnect sent signal for unmount to proceed
In case you want to see yet another one, here is the next backup. This took even longer..
May 20 06:00:00 myhost.nl com.apple.backupd[85963]: Starting manual backup
May 20 06:00:00 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 20 06:00:01 myhost.nl com.apple.backupd[85963]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 20 06:00:02 myhost.nl com.apple.backupd[85963]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 20 06:00:02 myhost kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
May 20 06:00:02 myhost kernel[0]: AFP_VFS afpfs_mount: /Volumes/Backup, pid 85965
May 20 06:00:02 myhost kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80ee828008 /Volumes/Backup (error = 0, retval = 0)
May 20 06:00:49 myhost.nl mdworker[85968]: Unable to talk to lsboxd
May 20 06:00:49 myhost.nl sandboxd[85969] ([85968]): mdworker(85968) deny mach-lookup com.apple.ls.boxd
May 20 06:00:50 myhost kernel[0]: Sandbox: sandboxd(85969) deny mach-lookup com.apple.coresymbolicationd
May 20 06:08:47 myhost.nl mdworker[85995]: Unable to talk to lsboxd
May 20 06:08:48 myhost.nl sandboxd[85996] ([85995]): mdworker(85995) deny mach-lookup com.apple.ls.boxd
May 20 06:08:48 myhost kernel[0]: Sandbox: sandboxd(85996) deny mach-lookup com.apple.coresymbolicationd
May 20 06:08:59 myhost.nl netbiosd[76]: name servers down?
May 20 06:13:40 myhost.nl netbiosd[76]: name servers down?
May 20 06:16:58 myhost.nl mdworker[86043]: Unable to talk to lsboxd
May 20 06:16:59 myhost.nl sandboxd[86044] ([86043]): mdworker(86043) deny mach-lookup com.apple.ls.boxd
May 20 06:16:59 myhost kernel[0]: Sandbox: sandboxd(86044) deny mach-lookup com.apple.coresymbolicationd
May 20 06:17:12 myhost.nl com.apple.backupd[85963]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 20 06:17:14 myhost.nl com.apple.backupd[85963]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 20 06:20:49 myhost.nl fseventsd[48]: event logs in /Volumes/Time Machine Backups/.fseventsd out of sync with volume. destroying old logs. (13 220 40785)
May 20 06:25:39 myhost.nl mdworker[86090]: Unable to talk to lsboxd
May 20 06:25:40 myhost kernel[0]: Sandbox: sandboxd(86091) deny mach-lookup com.apple.coresymbolicationd
May 20 06:25:40 myhost.nl sandboxd[86091] ([86090]): mdworker(86090) deny mach-lookup com.apple.ls.boxd
May 20 06:31:31 myhost.nl netbiosd[76]: name servers down?
May 20 06:33:44 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=86114[GoogleSoftwareUp] clearing CS_VALID
May 20 06:34:54 myhost.nl mdworker[86117]: Unable to talk to lsboxd
May 20 06:34:55 myhost kernel[0]: Sandbox: sandboxd(86132) deny mach-lookup com.apple.coresymbolicationd
May 20 06:34:55 myhost.nl sandboxd[86132] ([86117]): mdworker(86117) deny mach-lookup com.apple.ls.boxd
May 20 06:43:57 myhost.nl mdworker[86154]: Unable to talk to lsboxd
May 20 06:43:57 myhost kernel[0]: Sandbox: sandboxd(86155) deny mach-lookup com.apple.coresymbolicationd
May 20 06:43:57 myhost.nl sandboxd[86155] ([86154]): mdworker(86154) deny mach-lookup com.apple.ls.boxd
May 20 06:45:12 myhost.nl netbiosd[76]: name servers down?
May 20 06:53:01 myhost.nl mdworker[86192]: Unable to talk to lsboxd
May 20 06:53:01 myhost.nl sandboxd[86193] ([86192]): mdworker(86192) deny mach-lookup com.apple.ls.boxd
May 20 06:53:01 myhost kernel[0]: Sandbox: sandboxd(86193) deny mach-lookup com.apple.coresymbolicationd
May 20 06:57:15 myhost.nl netbiosd[76]: name servers down?
May 20 07:01:40 myhost.nl mdworker[86231]: Unable to talk to lsboxd
May 20 07:01:40 myhost.nl sandboxd[86232] ([86231]): mdworker(86231) deny mach-lookup com.apple.ls.boxd
May 20 07:01:41 myhost kernel[0]: Sandbox: sandboxd(86232) deny mach-lookup com.apple.coresymbolicationd
May 20 07:09:06 myhost.nl fseventsd[48]: log dir: /Volumes/Time Machine Backups/.fseventsd getting new uuid: 581D7EBC-9D7D-40A2-861C-486D09F787AA
May 20 07:09:15 myhost.nl netbiosd[76]: name servers down?
May 20 07:09:48 myhost.nl mdworker[86257]: Unable to talk to lsboxd
May 20 07:09:49 myhost.nl sandboxd[86272] ([86257]): mdworker(86257) deny mach-lookup com.apple.ls.boxd
May 20 07:09:49 myhost kernel[0]: Sandbox: sandboxd(86272) deny mach-lookup com.apple.coresymbolicationd
May 20 07:10:18 myhost.nl com.apple.backupd[85963]: Using file event preflight for Macintosh HD
May 20 07:11:14 myhost.nl com.apple.backupd[85963]: Will copy (4.4 MB) from Macintosh HD
May 20 07:11:14 myhost.nl com.apple.backupd[85963]: Found 306 files (4.4 MB) needing backup
May 20 07:11:14 myhost.nl com.apple.backupd[85963]: 14.54 GB required (including padding), 1.74 TB available
May 20 07:13:47 myhost.nl netbiosd[76]: name servers down?
May 20 07:19:31 myhost.nl mdworker[86304]: Unable to talk to lsboxd
May 20 07:19:31 myhost kernel[0]: Sandbox: sandboxd(86305) deny mach-lookup com.apple.coresymbolicationd
May 20 07:19:31 myhost.nl sandboxd[86305] ([86304]): mdworker(86304) deny mach-lookup com.apple.ls.boxd
May 20 07:29:54 myhost.nl mdworker[86351]: Unable to talk to lsboxd
May 20 07:29:54 myhost kernel[0]: Sandbox: sandboxd(86366) deny mach-lookup com.apple.coresymbolicationd
May 20 07:29:54 myhost.nl sandboxd[86366] ([86351]): mdworker(86351) deny mach-lookup com.apple.ls.boxd
May 20 07:32:27 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=86372[GoogleSoftwareUp] clearing CS_VALID
May 20 07:33:26 myhost.nl com.apple.backupd[85963]: Copied 1917 files (11.7 MB) from volume Macintosh HD.
May 20 07:33:27 myhost.nl com.apple.backupd[85963]: Using file event preflight for Macintosh HD
May 20 07:33:27 myhost.nl com.apple.backupd[85963]: Will copy (5.9 MB) from Macintosh HD
May 20 07:33:27 myhost.nl com.apple.backupd[85963]: Found 156 files (5.9 MB) needing backup
May 20 07:33:27 myhost.nl com.apple.backupd[85963]: 14.54 GB required (including padding), 1.74 TB available
May 20 07:33:58 myhost.nl netbiosd[76]: name servers down?
May 20 07:44:14 myhost.nl mdworker[86412]: Unable to talk to lsboxd
May 20 07:44:15 myhost.nl sandboxd[86413] ([86412]): mdworker(86412) deny mach-lookup com.apple.ls.boxd
May 20 07:44:15 myhost kernel[0]: Sandbox: sandboxd(86413) deny mach-lookup com.apple.coresymbolicationd
May 20 07:45:27 myhost.nl netbiosd[76]: name servers down?
May 20 07:55:37 myhost.nl netbiosd[76]: name servers down?
May 20 07:58:57 myhost.nl mdworker[86459]: Unable to talk to lsboxd
May 20 07:58:57 myhost kernel[0]: Sandbox: sandboxd(86460) deny mach-lookup com.apple.coresymbolicationd
May 20 07:58:57 myhost.nl sandboxd[86460] ([86459]): mdworker(86459) deny mach-lookup com.apple.ls.boxd
May 20 08:09:31 myhost.nl netbiosd[76]: name servers down?
May 20 08:13:14 myhost.nl mdworker[86516]: Unable to talk to lsboxd
May 20 08:13:14 myhost kernel[0]: Sandbox: sandboxd(86517) deny mach-lookup com.apple.coresymbolicationd
May 20 08:13:20 myhost.nl sandboxd[86517] ([86516]): mdworker(86516) deny mach-lookup com.apple.ls.boxd
May 20 08:14:16 myhost.nl netbiosd[76]: name servers down?
May 20 08:27:46 myhost.nl mdworker[86567]: Unable to talk to lsboxd
May 20 08:27:47 myhost kernel[0]: Sandbox: sandboxd(86568) deny mach-lookup com.apple.coresymbolicationd
May 20 08:27:47 myhost.nl sandboxd[86568] ([86567]): mdworker(86567) deny mach-lookup com.apple.ls.boxd
May 20 08:29:21 myhost.nl com.apple.backupd[85963]: Copied 1608 files (907.6 MB) from volume Macintosh HD.
May 20 08:29:25 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 20 08:29:27 myhost.nl com.apple.backupd[85963]: Created new backup: 2013-05-20-082922
May 20 08:30:00 myhost.nl com.apple.backupd[85963]: Starting post-backup thinning
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KeystoneDaemon logServiceState] GoogleSoftwareUpdate daemon (1.1.0.3659) vending:
                    com.google.Keystone.Daemon.UpdateEngine: 2 connection(s)
                    com.google.Keystone.Daemon.Administration: 0 connection(s)
May 20 08:31:10 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=86593[GoogleSoftwareUp] clearing CS_VALID
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateEngine updateProductID:] KSUpdateEngine updating product ID: "com.google.Keystone"
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSCheckAction performAction] KSCheckAction checking 1 ticket(s).
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction starting update check for ticket(s): {(
                    <KSTicket:0x546640
                              productID=com.google.Keystone
                              version=1.1.0.3659
                              xc=<KSPathExistenceChecker:0x546580 path=/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/>
                              serverType=Omaha
                              url=https://tools.google.com/service/update2
                              creationDate=2010-06-26 09:28:46
                    >
          Using server: <KSOmahaServer:0x256da0
                    engine=<KSDaemonUpdateEngine:0x1856510>
                    params={
                              EngineVersion = "1.1.0.3659";
                              ActivesInfo = {
                                        "com.google.macphotouploader" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:57 +0000;
                                        "com.google.Chrome" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActiveDate = 2011-01-07 15:41:05 +0000;
                                                  LastActivePingDate = 2011-01-08 08:00:00 +0000;
                                        "com.google.GoogleDrive" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActivePingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActiveDate = 2013-05-20 05:38:35 +0000;
                                        "com.google.Keystone" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:57 +0000;
                                                  LastActivePingDate = 2013-05-19 06:59:57 +0000;
                                                  LastActiveDate = 2013-05-20 06:31:10 +0000;
                                        "com.Google.GoogleEarthPlugin.intel" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                        "com.Google.GoogleEarthPlus" = {
                                                  LastRollCallPingDate = 2011-05-31 07:00:00 +0000;
                                        "com.Google.GoogleEarthPlus.intel" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                              UserInitiated = 0;
                              IsSystem = 1;
                              OmahaOSVersion = "10.8.2_i486";
                              Identity = KeystoneDaemon;
                              AllowedSubdomains = (
                                        ".omaha.sandbox.google.com",
                                        ".tools.google.com",
                                        ".www.google.com",
                                        ".corp.google.com"
          >
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction running KSServerUpdateRequest: <KSOmahaServerUpdateRequest:0x25ad60
                    server=<KSOmahaServer:0x256da0>
                    url="https://tools.google.com/service/update2"
                    runningFetchers=0
                    tickets=1
                    activeTickets=0
                    rollCallTickets=0
                    body=
                              <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                              <o:gupdate xmlns:o="http://www.google.com/update2/request" protocol="2.0" version="KeystoneDaemon-1.1.0.3659" ismachine="1">
                                  <o:os platform="mac" version="MacOSX" sp="10.8.2_i486"></o:os>
                                  <o:app appid="com.google.Keystone" version="1.1.0.3659" lang="en-us" installage="1058" brand="GGLG">
                                      <o:updatecheck></o:updatecheck>
                                  </o:app>
                              </o:gupdate>
          >
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction(KSServerUpdateRequestDelegate) serverRequest:fetchedWithResponse:] KSUpdateCheckAction received KSServerUpdateResponse: <KSOmahaServerUpdateResponse:0x1c44170
                    server=<KSOmahaServer:0x256da0>
                    url="https://tools.google.com/service/update2"
                    status=200
                    tickets=1
                    activeTickets=0
                    rollCallTickets=0
                    data=
                              <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                              <gupdate xmlns="http://www.google.com/update2/response" protocol="2.0" server="prod">
                                  <daystart elapsed_seconds="84674"></daystart>
                                  <app appid="com.google.Keystone" status="ok">
                                      <updatecheck status="noupdate"></updatecheck>
                                  </app>
                              </gupdate>
          >
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction(PrivateMethods) finishAction] KSUpdateCheckAction found updates: {( )}
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSPrefetchAction performAction] KSPrefetchAction no updates to prefetch.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSMultiUpdateAction performAction] KSSilentUpdateAction had no updates to apply.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSMultiUpdateAction performAction] KSPromptAction had no updates to apply.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateEngine(PrivateMethods) updateFinish] KSUpdateEngine update processing complete.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateEngine updateAllProducts] KSUpdateEngine updating all installed products.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSCheckAction performAction] KSCheckAction checking 2 ticket(s).
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction starting update check for ticket(s): {(
                    <KSTicket:0x546640
                              productID=com.google.Keystone
                              version=1.1.0.3659
                              xc=<KSPathExistenceChecker:0x545c20 path=/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/>
                              serverType=Omaha
                              url=https://tools.google.com/service/update2
                              creationDate=2010-06-26 09:28:46
                    >,
                    <KSTicket:0x546ec0
                              productID=com.google.macphotouploader
                              version=1.5.0.1425
                              xc=<KSLaunchServicesExistenceChecker:0x547260 bundle=com.google.macphotouploader>
                              url=https://tools.google.com/service/update2
                              creationDate=2008-12-06 18:11:10
                    >
          Using server: <KSOmahaServer:0x1a4a600
                    engine=<KSDaemonUpdateEngine:0x1856510>
                    params={
                              EngineVersion = "1.1.0.3659";
                              ActivesInfo = {
                                        "com.google.macphotouploader" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:57 +0000;
                                        "com.google.Chrome" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActiveDate = 2011-01-07 15:41:05 +0000;
                                                  LastActivePingDate = 2011-01-08 08:00:00 +0000;
                                        "com.google.GoogleDrive" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActivePingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActiveDate = 2013-05-20 05:38:35 +0000;
                                        "com.google.Keystone" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:57 +0000;
                                                  LastActivePingDate = 2013-05-19 06:59:57 +0000;
                                                  LastActiveDate = 2013-05-20 06:31:10 +0000;
                                        "com.Google.GoogleEarthPlugin.intel" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                        "com.Google.GoogleEarthPlus" = {
                                                  LastRollCallPingDate = 2011-05-31 07:00:00 +0000;
                                        "com.Google.GoogleEarthPlus.intel" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                              UserInitiated = 0;
                              IsSystem = 1;
                              OmahaOSVersion = "10.8.2_i486";
                              Identity = KeystoneDaemon;
                              AllowedSubdomains = (
                                        ".omaha.sandbox.google.com",
                                        ".tools.google.com",
                                        ".www.google.com",
                                        ".corp.google.com"
          >
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction running KSServerUpdateRequest: <KSOmahaServerUpdateRequest:0x1a4dc20
                    server=<KSOmahaServer:0x1a4a600>
                    url="https://tools.google.com/service/update2"
                    runningFetchers=0
                    tickets=2
                    activeTickets=0
                    rollCallTickets=0
                    body=
                              <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                              <o:gupdate xmlns:o="http://www.google.com/update2/request" protocol="2.0" version="KeystoneDaemon-1.1.0.3659" ismachine="1">
                                  <o:os platform="mac" version="MacOSX" sp="10.8.2_i486"></o:os>
                                  <o:app appid="com.google.Keystone" version="1.1.0.3659" lang="en-us" installage="1058" brand="GGLG">
                                      <o:updatecheck></o:updatecheck>
                                  </o:app>
                                  <o:app appid="com.google.macphotouploader" version="1.5.0.1425" lang="en-us" installage="1625" brand="GGLG">
                                      <o:updatecheck></o:updatecheck>
                                  </o:app>
                              </o:gupdate>
          >
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction(KSServerUpdateRequestDelegate) serverRequest:fetchedWithResponse:] KSUpdateCheckAction received KSServerUpdateResponse: <KSOmahaServerUpdateResponse:0x1867890
                    server=<KSOmahaServer:0x1a4a600>
                    url="https://tools.google.com/service/update2"
                    status=200
                    tickets=2
                    activeTickets=0
                    rollCallTickets=0
                    data=
                              <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
                              <gupdate xmlns="http://www.google.com/update2/response" protocol="2.0" server="prod">
                                  <daystart elapsed_seconds="84675"></daystart>
                                  <app appid="com.google.Keystone" status="ok">
                                      <updatecheck status="noupdate"></updatecheck>
                                  </app>
                                  <app appid="com.google.macphotouploader" status="ok">
                                      <updatecheck status="noupdate"></updatecheck>
                                  </app>
                              </gupdate>
          >
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction(PrivateMethods) finishAction] KSUpdateCheckAction found updates: {( )}
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSPrefetchAction performAction] KSPrefetchAction no updates to prefetch.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSMultiUpdateAction performAction] KSSilentUpdateAction had no updates to apply.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSMultiUpdateAction performAction] KSPromptAction had no updates to apply.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateEngine(PrivateMethods) updateFinish] KSUpdateEngine update processing complete.
May 20 08:31:13 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KeystoneDaemon logServiceState] GoogleSoftwareUpdate daemon (1.1.0.3659) vending:
                    com.google.Keystone.Daemon.UpdateEngine: 1 connection(s)
                    com.google.Keystone.Daemon.Administration: 0 connection(s)
May 20 08:31:40 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KeystoneDaemon main] GoogleSoftwareUpdateDaemon inactive, shutdown.
May 20 08:32:43 myhost.nl netbiosd[76]: name servers down?
May 20 08:37:45 myhost.nl com.apple.backupd[85963]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-04-20-001649 (118.6 MB)
May 20 08:37:45 myhost.nl com.apple.backupd[85963]: Post-back up thinning complete: 1 expired backups removed
May 20 08:37:47 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 20 08:37:52 myhost.nl com.apple.backupd[85963]: Backup completed successfully.
May 20 08:38:06 myhost.nl diskarbitrationd[16]: mds [38]:16919 not responding.
May 20 08:38:06 myhost.nl diskarbitrationd[16]: fseventsd [48]:16643 not responding.
May 20 08:38:30 myhost.nl mdworker[86623]: Unable to talk to lsboxd
May 20 08:38:30 myhost kernel[0]: Sandbox: sandboxd(86624) deny mach-lookup com.apple.coresymbolicationd
May 20 08:38:31 myhost.nl sandboxd[86624] ([86623]): mdworker(86623) deny mach-lookup com.apple.ls.boxd
May 20 08:38:32 myhost.nl fseventsd[48]: disk logger: failed to open output file /Volumes/Time Machine Backups/.fseventsd/6365734200d27745 (No such file or directory). mount point /Volumes/Time Machine Backups/.fseventsd
May 20 08:38:36 myhost.nl com.apple.backupd[85963]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 20 08:38:36 myhost.nl com.apple.backupd[85963]: Ejected Time Machine network volume.
May 20 08:38:36 myhost kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Backup, flags 0, pid 86627
May 20 08:38:36 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/Backup 0xffffff80ee828008
May 20 08:38:36 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/Backup 0xffffff80ee828008
May 20 08:38:36 myhost kernel[0]: AFP_VFS afpfs_unmount : afpfs_DoReconnect sent signal for unmount to proceed
I let this go on for another couple of days, then rebooted. Things are now back to normal.

Time Machine Restore Slows Computer

I have a 24" iMac (Early 2008) 3.06GHz Intel Core 2 Duo computer. The original hard drive failed last week and I had it replaced with a new 1TB HD at a local Apple Premium Service Provider shop. The computer worked like new when I got it back...and then I restored my backup from Time Machine.
So I've had this Mac since 2008 and since then I have gone through almost all the OS X updates. I have downloaded and installed tons of apps, which over the years have become out-of-date and thus no longer work with the current OS. I have downloaded countless of albums and movies, tv shows etc, etc. I have deleted some of this information over the years. I have also been through a few different external hd's using Time Machine, but I always transferred all the old information to the new ones. Could someone tell me if bits of leftover information are now saved on my HD and are thus causing the computer to perform extremely slow? If this is the case, what would be the best approach to deleting this information? Thanks in advance!

When you have the problem, note the exact time: hour, minute, second.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above. Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first. Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough. It is never necessary or helpful to post more than about 100 lines. "The more, the better" is not the rule here.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

Time machine very slow with mountain lion

Time Machine backups seem very slow with Mountain Lion.

Same problem here. I just upgraded from Lion to Mountain Lion. I only got 19 GB of space, but Time Machine wants 10 hours, whereas in OSX Lion a full backup would take just under an hour, and incremental updates were lightning fast.
I even sat it up to do it overnight, but on 8 hours it was only half way through only 10 GB. I can't live with that in the future.
Im trying to backup on a SD card which seems to work very good in Lion. Im on a 2012 Macbook Air using a SSD.
My bite of the apple has been somewhat sour. I tried reformatting the SD card, well knowing that I would lose old backups. But still the backup is extremely slow. Now I can't install Lion or Mountain Lion from scratch without having to wait 10 hours for TM backup or installing tons of applications and settings again. Bummer. I'm never going to early adobt a OSX upgrade again.

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.

Is this first back up with Time Machine too slow?

I'm running my first backup onto a new Western Digital Essential 1 terrabyte via a USB connection.
It started at 2AM. It's now 9AM and the progress bar reads:
"16.5 Gigs of 118 Gigs"
That's a little better than two gigs an hour.
This seems very slow to me and I'd like to know if that impression is correct. At that rate it seems like the back up will take more than two days.
Is this "normal?"
The technical stuff from System Profiler is:
OS: 10.5.8
Model Name: Power Mac G4
Model Identifier: PowerMac3,6
Processor Name: PowerPC G4 (3.3)
Processor Speed: 1.25 GHz
Number Of CPUs: 1
L2 Cache (per CPU): 256 KB
L3 Cache (per CPU): 1 MB
Memory: 2 GB
Bus Speed: 167 MHz
Boot ROM Version: 4.4.8f2
My Book 1110:
Capacity: 930.86 GB
Removable Media: Yes
Detachable Drive: Yes
BSD Name: disk4
Product ID: 0x1110
Vendor ID: 0x1058 (Western Digital Technologies, Inc.)
Version: 20.03
Serial Number: 574341563541373730353233
Speed: Up to 12 Mb/sec
Manufacturer: Western Digital

vanderleun wrote:
I'm running my first backup onto a new Western Digital Essential 1 terrabyte via a USB connection.
It started at 2AM. It's now 9AM and the progress bar reads:
"16.5 Gigs of 118 Gigs"
That's a little better than two gigs an hour.
This seems very slow to me and I'd like to know if that impression is correct.
Yes, that's ridiculous. While Time Machine backups are slower than just copying things, and especially slower at the beginning, you should get roughly 40 - 60 GB/hour, on average.
First, make sure the drive is set up properly, per #C1 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).
If so, try the things in the green box of #D2 there. Most of them can be done without cancelling the backup.

Time machine extreme slow

Similar Messages

Maybe you are looking for