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'...

Similar Messages

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 Entering Time Machine Backup SO SLOW ???

I have been using Time Machine (TM) for almost 2 years and when I enter TM - its is SLOW when I go back the timeline. I have the email window open when entering TM and it is taking minutes to fill in only 50 or so emails (I know I have 1000's).
Any suggestions to help this????
I have an external hardrive for TM connected to Time capsule.
Skip

60 seconds !!!
I solved it!
What I did:
I interrupted a running incremental backup after 20 minutes by switching off Time Machine in the control panel. In the log the message was:
     Stopping backupd to allow ejection of backup destination disk!
Then I rebooted the iMac from the Snow Leopard DVD and repaired the SSD and the FireWire Drive. In both cases no failures could be found.
Then I restarted the iMac from its internal SSD and waited until Time Machine started again (after one hour). Now there was something new in the log:
              Event store UUIDs don't match for volume: Speedy HD
              Node requires deep traversal:/ reason:must scan subdirs|new event db|
This backup took just 12 Minutes and was much faster than the previous incremental backups which took 30..45 minutes.
Now I tried the ultimate thing: I ordered Time Machine to make a new incremental backup. See what happens:
30.06.11 21:10:23 Starting standard backup
30.06.11 21:10:23 Backing up to: /Volumes/Archiv 1/Backups.backupdb
30.06.11 21:10:32 No pre-backup thinning needed: 1.83 GB requested (including padding), 911.84 GB available
30.06.11 21:11:03 Copied 9117 files (647.1 MB) from volume Speedy HD.
30.06.11 21:11:08 Copied 9365 files (647.1 MB) from volume Speedy Medien.
30.06.11 21:11:10 No pre-backup thinning needed: 1.08 GB requested (including padding), 911.18 GB available
30.06.11 21:11:15 Copied 2811 files (1 KB) from volume Speedy HD.
30.06.11 21:11:18 Copied 3059 files (1 KB) from volume Speedy Medien.
30.06.11 21:11:22 Starting post-backup thinning
30.06.11 21:11:22 No post-back up thinning needed: no expired backups exist
30.06.11 21:11:23 Backup completed successfully.
I don't know what made the difference and I do not know how long Time Machine behaves well from now on. But I hope, that the problem is solved.

Why is my time machine backup so slow even when directly connected with usb 3.0?

On my new 15" Retina running OS 10.7.5 the backup of about 225 GB would estimate about 17 hours and then stall out around 22 GB or so.
Now it seems to hang on the setup.
I've just gone back to my old machine (late 2008 15" MBP running OS 10.7.4) to see if it would work any faster I am getting an estimate of "about a day" on about 280 GB. (Backwards compatible at USB 2.0 speeds of course).
In both instances I am directly connected via USB 3.0 to a Seagate 3TB desktop drive that I reformatted to Mac OS Extended (Journaled) right out of the box.
I bought this drive to replace my old 500 GB Time Capsule which is much too small to maintain backups for my MBP and my wife's Air. My plan was to run the initial backups hard-wired (for speed) and then attach it to a new Airport Express for subsequent backups.
No network or wireless to potentially cause this lag.
Any thoughts?
Thanks!

It's true. I love Google. Miss the maps on the iPhone5 for sure.
Like you say, I end up expanding all my searches in Google to give me more results within apple discussions rather than search here.
I moved the external 3 TB drive over to the Time Capsule via its USB port and it is showing up. So that's one bullet maybe dodged so far.
On a grander scale, I'm currently in the midst of trying to redo my home network and I'm in a little over my head.
I will try to explain...
My previous network ran as follows:
Time Warner cable coax ----------> their provided Motorola modem ----via ethernet---> My old 500 GB Time Capsule creating the WIFI network for my place and feeding three other old style Airport Express devices in various rooms extending the network but essentially just for AirTunes
Also, the Time Capsule ran ethernet cables to my Western Digital TV and Western Digital MyBook Live Duo 4TB drive. Both of these Western Digital devices have wifi built in but I wasn't getting the playback speeds I was expecting so I hardwired them with ethernet for faster service which has been working for a while.
NOW.....
I am replacing the three old Airport Express devices with three new Airport Express devices and making one of them the Master device to create a new network (dumping the old one and trying to start fresh).
Here's my plan and what I have hooked up so far.
TWC coax ----> Motorola modem ---ethernet----> Airport Express #1 (creating WIFI network for Airport Express #2 and #3 AND ---------ethernet-------> Old 500 GB Time Machine-----ethernet #1-----> WDTV Live AND ----ethernet #2------> WD MBLD 4TB AND NOW -------USB-----> 3TB Seagate external for Time Machine drive expansion. ALSO POSSIBLY -----ethernet #3------> Apple TV 2 for the same reasons I have the WD devices hooked up via ethernet. I don't trust the wifi to be fast enough for video streaming.
Now, despite having read wikis and other explanations for Bridge mode, DHCP and NAT settings for routers (in this case, the TM) I still can't figure exactly what mode the TM should get setup with.
Also all of these devices are set up in different pockets on the same shelf so I was worried that all the WIFI signals would interfere with each other (hence all the ethernet).
My plan was to turn of the wireless in the TM and have all of these devices branch off via ethernet. Which brings me back to my uncertainty regarding whether to set the TM to Off (Bridge Mode), DHCP, or DHCP and NAT.
From what I've read I would think it should be in Bridge mode but I also read some things about how bandwidth use in bridge mode can be very high and could cause problems using the internet possibly over my overall wifi network? Although I'm not sure I'm understanding that correctly.
I apologize for my lack of understanding in setting up a complicated network. I've just been wanting to get all of this working the way I've hoped (correctly) for a long time.
Thanks in advance for any more advice!

Time machine backups have slowed considerably since my installation of Mavericks -- why?

Ever since installation of Mavericks, time machine backups have slowed to a crawl. The message preparing backup used to to take 10 seconds to a minute, now it takes 5 minutes. The status of the backup used to show 10mb's of 80 mb's backed up, and take under 1 minute, now it takes 5 minutes. Finally cleaning up notice, and the time to clean up has increased significantly. My backups go to an external HD (7200rpm) connected vis firewire 800, that has approx 180 gigabytes available of its 1 terrabybyte capacity.

I upgraded to Mountain Lion a few weeks ago. Everything was fine with Time Machine until a few of days ago.
Same problem others described: extremely slow, taking hours to back up just a few MB.
I verified the Time Capsule drive and my Mac hard drive - no problems found.
I then erased the Time Capsule and started Time Machine. It did the full backup in a fairly reasonable amount of time (several hours, but not unexpectedly long).
When it started its first incremental backup, it reverted to the same problem: extremely slow, but it did finish eventually.
I then shut down the Mac and restarted (power cycled) the Time Capsule. Then I started up the Mac and told Time Machine to back up now. It backed up 30+ MB in just a few minutes, so it seems back to normal. We'll see how it goes when the next scheduled backup starts up.
But you might try rebooting the Time Capsule (and your Mac).
By the way, when it was in the middle of the extremely slow backup, I disabled Norton Anti-virus and it didn't seem to speed it up any. But I left it disabled after I rebooted the Time Capsule and had a successful incremental backup, so I'm not sure yet if Norton is a factor.

HT1175 I have OSX Lion 10.7.5 and the backup in time machine is extremely slow

I have OSX 10.7.5 installed on my MacBook Pro and the backup to time machine is extemely slow. Time Machine indicates 4 days or more. Why?

Did you happen to update early in the piece.. there is a supplement.
http://support.apple.com/kb/DL1599
Test regime for software patches is now left to end users it seems.

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.

Just upgraded to ML, and Time Machine is super slow

Why is time machine backup so slow? Normally it took only about ten minutes...now it seems like it needs a whole day or more?!?!?!

Hello Harold,
Sorry to hear that Time Machine has not been backing up. I recommend following the steps in the article below for steps to isolate and troubleshoot this issue:
Time Machine: Troubleshooting backup issues
http://support.apple.com/kb/HT3275
Thank you for using Apple Support Communities.
Best,
Sheila M.

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.

Why is my macbook pro running so slow and how do I improve the speed?

why is my macbook pro running so slow and how do I improve the speed?

Write off the MS stuff as indicators for now--starting with Office 2008, they developed very long launch times. The time to launch 2008 on my old 1.25Ghz G4 and my MBP 2.2G are virtually the same. Even document opens/saves are slow compared to Office 2004 and earlier.
1) You have adequate hard drive space so that eliminates one of the usual suspects.
2) Check for runaway background processes. Quit all running user applications so the computer is at normal idle. Find Activity Monitor in Applications > Utilities and launch it. If you've not run it before, change the "Show" pulldown at the top of the AM window from its default of "User Processes" to "All Processes." There is a column for "%CPU." Click that column header to sort by CPU usage. Watch the processes "bubble" for about a minute to get a better picture of the usage.
If any process is using more than about 25 percent of the CPU cycles while the computer is idling, post the names of the processes and we can see if they can be eliminated. My MBP shows nothing using more that about 5 percent on any given test run as long as I close all my user apps.
3) If you have never done any sort of maintenance procedures, taht can slow you down. Simply restarting the computer a few times a week clear a lot of temporary files. You also may wish to review this article on the Mac OSX periodic maintenance scripts, which, if run, also do a lot of cleanup:
http://thexlab.com/faqs/maintscripts.html
There are other useful articles on file maintenance associated with the one. Here's the index:
http://thexlab.com/faqs/faqs.html
Check out articles with "Maintain" and "Tuning" in the titles.
4) Use Disk Utility to check the SMART Status of your hard drive. A failing drive can make things slow before it makes things stop.

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

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 is very slow....

After upgrading to ML, time machine seems very slow. I usually make back up once a week. First back up took nearly a day, but completed successfully.

After upgrading to ML, time machine seems very slow. I usually make back up once a week. First back up took nearly a day, but completed successfully.

Suddenly, time machine is very slow. Used to take up a minute and now more than half an hour. Does anybody know how this can happen? Indexing the back-up disk is off, but Timde Machine keeps on indexing!

Suddenly, time machine is very slow. Used to take up a minute and now more than half an hour. Does anybody know how this can happen? Indexing the back-up disk is off, but Timde Machine keeps on indexing!

same issue here...

Why is my Time Machine running so slow?

Similar Messages

Maybe you are looking for