Time Machine Taking a Long Time to Index / Back Up

Hi everyone.
I noticed this on the latest backup to my Time Capsule device.  I'm backing up over a WiFi connection to a time capsule device.  It is taking a long time to index the backup.  Here's the code from the latest backup.
10/17/12 9:43:03.799 PM com.apple.backupd: Starting standard backup
10/17/12 9:43:04.091 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
10/17/12 9:43:12.657 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
10/17/12 9:43:34.015 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
10/17/12 9:43:37.440 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
10/17/12 9:43:37.459 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
10/17/12 9:45:23.296 PM com.apple.backupd: 500.1 MB required (including padding), 3.27 GB available
10/17/12 9:46:48.844 PM com.apple.backupd: Copied 1436 files (3.4 MB) from volume Macintosh HD.
10/17/12 9:46:51.897 PM com.apple.backupd: 448.1 MB required (including padding), 3.27 GB available
10/17/12 9:46:51.898 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:47:53.681 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:48:55.642 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:49:56.511 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:50:56.564 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:51:57.643 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:52:57.903 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:53:59.341 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:55:01.281 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:56:03.171 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:57:03.966 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:58:33.083 PM com.apple.backupd: Copied 824 files (1.2 MB) from volume Macintosh HD.
10/17/12 9:58:40.359 PM com.apple.backupd: Starting post-backup thinning
10/17/12 9:59:51.851 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-213620 (5.6 MB)
10/17/12 10:00:17.440 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-113505 (1.6 MB)
10/17/12 10:00:30.046 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-103509 (1.6 MB)
10/17/12 10:00:43.781 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-093513 (1.3 MB)
10/17/12 10:00:43.781 PM com.apple.backupd: Post-back up thinning complete: 4 expired backups removed
10/17/12 10:00:45.207 PM com.apple.backupd: Backup completed successfully.
10/17/12 10:00:56.988 PM com.apple.backupd: Ejected Time Machine disk image.
10/17/12 10:00:57.550 PM com.apple.backupd: Ejected Time Machine network volume.
I am just curious as to why this is, and what I might do to fix it.  I did see one suggestion in another website suggesting diabling spolight indexing of the backup image with sudo mdutil -i off /Volumes/Time Machine Backups, but don't know where to type that in.  It then states to reenable it, but don't know where to type that in, either.  Any advice would be helpful.  I did run a verification not too long ago, and here's that code.
10/14/12 3:44:14.289 PM com.apple.backupd: Backup verification requested by user.
10/14/12 3:44:41.503 PM com.apple.backupd: Running backup verification
10/14/12 4:04:31.602 PM com.apple.backupd: Backup verification passed!
If any of you have or had a similar problem, I'd appreciate your help.  For the time being, I may just disable time machine during the evening, and only have it run during the day when I'm at work.

Is your sig still current (10.7.3)? Or did you update to 10.7.5? Because 10.7.5 had a Spotlight/Time Machine bug that slowed down a lot of backups. If that's what it is, there's now a 10.7.5 Supplemental Update that fixes the slow Time Machine problem.
If it isn't 10.7.5, I don't know what the problem might be.

Similar Messages

  • Time Machine Taking a Long Time to Index

    Hi everyone.
    I first noticed this today.  My Time Machine is taking a long time to index.  It's stuck on "Waiting for index to be ready (100)" for about 10 minutes at least, it seems.  I did notice earlier today that it had to delete old backups to make space for new backups, and I'm wondering if that has anything to do with it.  I'm in the process of doing a verification now, but here's the code from two backups earlier today.
    Here's the one where it had to delete backups to make room for new and future backups.
    1/30/13 5:48:13.069 PM com.apple.backupd: Starting standard backup
    1/30/13 5:48:13.267 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
    1/30/13 5:48:13.749 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
    1/30/13 5:48:35.120 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
    1/30/13 5:48:40.280 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
    1/30/13 5:48:40.407 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
    1/30/13 5:54:50.703 PM com.apple.backupd: 500.8 MB required (including padding), 403.3 MB available
    1/30/13 5:55:00.163 PM com.apple.backupd: Ejected disk image: /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle
    1/30/13 5:55:00.163 PM com.apple.backupd: Compacting backup disk image to recover free space
    1/30/13 5:58:52.014 PM com.apple.backupd: Completed backup disk image compaction
    1/30/13 5:58:52.016 PM com.apple.backupd: Starting standard backup
    1/30/13 5:58:52.065 PM com.apple.backupd: Network destination already mounted at: /Volumes/Time Machine Backups
    1/30/13 5:59:13.694 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
    1/30/13 5:59:17.577 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
    1/30/13 5:59:17.673 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
    1/30/13 6:01:22.433 PM com.apple.backupd: 500.9 MB required (including padding), 424.6 MB available
    1/30/13 6:02:40.909 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2013-01-28-225651 containing 5.8 MB; 430.4 MB now available, 500.9 MB required
    1/30/13 6:02:40.909 PM com.apple.backupd: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
    1/30/13 6:25:09.045 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-05-12-095019 containing 1.08 GB; 1.50 GB now available, 500.9 MB required
    1/30/13 6:25:09.045 PM com.apple.backupd: Deleted 2 backups containing 1.09 GB total; 1.50 GB now available, 500.9 MB required
    1/30/13 6:25:09.045 PM com.apple.backupd: Backup date range was shortened: oldest backup is now May 20, 2012
    1/30/13 6:28:35.009 PM com.apple.backupd: Copied 2289 files (7.3 MB) from volume Macintosh HD.
    1/30/13 6:28:35.920 PM com.apple.backupd: 494.0 MB required (including padding), 424.6 MB available
    1/30/13 6:28:35.921 PM com.apple.backupd: No expired backups exist - deleting oldest backups to make room
    1/30/13 6:30:36.145 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-05-20-194752 containing 55.0 MB; 479.6 MB now available, 494.0 MB required
    1/30/13 6:30:36.146 PM com.apple.backupd: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
    1/30/13 6:33:16.203 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-05-27-093117 containing 64.5 MB; 544.0 MB now available, 494.0 MB required
    1/30/13 6:33:16.203 PM com.apple.backupd: Deleted 2 backups containing 119.4 MB total; 544.0 MB now available, 494.0 MB required
    1/30/13 6:33:16.203 PM com.apple.backupd: Backup date range was shortened: oldest backup is now Jun 7, 2012
    1/30/13 6:34:11.232 PM com.apple.backupd: Copied 1171 files (2.5 MB) from volume Macintosh HD.
    1/30/13 6:34:44.355 PM com.apple.backupd: Backup completed successfully.
    1/30/13 6:34:54.258 PM com.apple.backupd: Ejected Time Machine disk image.
    1/30/13 6:34:54.493 PM com.apple.backupd: Ejected Time Machine network volume.
    And here's the one where it started to take awhile to index.
    1/30/13 7:21:11.358 PM com.apple.backupd: Starting standard backup
    1/30/13 7:21:11.955 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
    1/30/13 7:21:12.540 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
    1/30/13 7:21:38.074 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
    1/30/13 7:21:41.754 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
    1/30/13 7:21:41.768 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
    1/30/13 7:23:47.444 PM com.apple.backupd: 452.8 MB required (including padding), 401.2 MB available
    1/30/13 7:23:56.687 PM com.apple.backupd: Ejected disk image: /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle
    1/30/13 7:23:56.687 PM com.apple.backupd: Compacting backup disk image to recover free space
    1/30/13 7:27:52.753 PM com.apple.backupd: Completed backup disk image compaction
    1/30/13 7:27:52.754 PM com.apple.backupd: Starting standard backup
    1/30/13 7:27:52.898 PM com.apple.backupd: Network destination already mounted at: /Volumes/Time Machine Backups
    1/30/13 7:28:14.638 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
    1/30/13 7:28:18.207 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
    1/30/13 7:28:18.309 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
    1/30/13 7:34:32.780 PM com.apple.backupd: 399.3 MB required (including padding), 937.6 MB available
    1/30/13 7:34:32.780 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:35:32.919 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:36:34.779 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:37:36.419 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:38:37.465 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:39:39.420 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:40:40.628 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:41:41.317 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:42:42.105 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:43:42.982 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:45:20.244 PM com.apple.backupd: Copied 1381 files (6.4 MB) from volume Macintosh HD.
    1/30/13 7:45:21.507 PM com.apple.backupd: 382.5 MB required (including padding), 826.5 MB available
    1/30/13 7:45:21.508 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:46:22.938 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:47:24.914 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:48:25.931 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:49:26.589 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:50:27.743 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:51:27.952 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:52:28.736 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:53:29.707 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:54:30.516 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:55:31.297 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:56:33.290 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:57:35.031 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:58:36.765 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 7:59:37.721 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 8:00:38.577 PM com.apple.backupd: Waiting for index to be ready (100)
    1/30/13 8:01:48.483 PM com.apple.backupd: Copied 1069 files (5.6 MB) from volume Macintosh HD.
    1/30/13 8:02:02.230 PM com.apple.backupd: Starting post-backup thinning
    1/30/13 8:02:46.083 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2013-01-29-183909 (5.4 MB)
    1/30/13 8:02:46.083 PM com.apple.backupd: Post-back up thinning complete: 1 expired backups removed
    1/30/13 8:02:46.083 PM com.apple.backupd: Warning: backup disk now has only 644.1 MB free without removing old backups
    1/30/13 8:02:46.259 PM com.apple.backupd: Backup completed successfully.
    1/30/13 8:02:58.025 PM com.apple.backupd: Ejected Time Machine disk image.
    1/30/13 8:02:58.407 PM com.apple.backupd: Ejected Time Machine network volume.
    I'm backing up to a Time Capsule over WiFi.  This time capsule has a total of 3 laptops that are backed up on it.

    Never mind.  Whatever it was, it's fine now.  We'll see what happens when it has to delete old backups to make space.  It's down to about 720 MB free without removing old backups.

  • Time machine taking a LONG time

    I have a IMac with OS Mountain Lion, and I backup automatically through Time Machine to a My Book.  Ever since I updated the OS the backups are taking a long time.  The initial backup after updating the OS took 3 1/2 days.  It did finally end and then they seemed to be taking the "normal" amount of time, minutes versus hours or days.  The last backup has been running since last Thursday night, and today is Tuesday.  It is showing "backing up 3.21GB of 3.53 GB".  I have been writing down where it is at before going to bed and last night it was 3.20 GB of 3.53 GB.  At 1 GB per day I have about 22 days left.  That seems a bit strange.  This last backup had been taking a long time and I've stopped it once and restarted.    Is this a current issue with the latest OS?  Any suggestions?

    Ok, I was trying to check something else and accidentally stopped the backup that had been running from last Thursday.   I restarted my computer and began another backup.  It is running now and here are the messages from the "console" from when I began the back up.  It is still running.  It started at 213.1 mb of 1.68 gb and has gone up to  11.91 gb of 13.10 gb.
    8/21/12 9:21:18.367 PM com.apple.backupd[320]: Starting manual backup
    8/21/12 9:21:19.110 PM com.apple.backupd[320]: Backing up to: /Volumes/My Book/Backups.backupdb
    8/21/12 9:21:24.179 PM com.apple.backupd[320]: Using file event preflight for Macintosh HD
    8/21/12 9:21:34.000 PM kernel[0]: Sandbox: sandboxd(325) deny mach-lookup com.apple.coresymbolicationd
    8/21/12 9:21:35.247 PM sandboxd[325]: ([324]) mdworker(324) deny file-write-create /private/var/folders/f1/9cxkqg6s73j_63tfftkrcktw0000gn/T/TemporaryItems (import fstype:hfs fsflag:480D000 flags:240000005E diag:0 uti:com.apple.iphoto.ipspot plugin:/Library/Spotlight/iPhoto.mdimporter - find suspect file using: sudo mdutil -t 8935199)
    8/21/12 9:21:35.251 PM sandboxd[325]: ([324]) mdworker(324) deny file-write-create /Users/VandenHeuvel/Pictures/iPhoto Library/.ipspot_update.sb-4015bbeb-kVJcRk (import fstype:hfs fsflag:480D000 flags:240000005E diag:0 uti:com.apple.iphoto.ipspot plugin:/Library/Spotlight/iPhoto.mdimporter - find suspect file using: sudo mdutil -t 8935199)
    8/21/12 9:21:35.278 PM com.apple.backupd[320]: Will copy (1.53 GB) from Macintosh HD
    8/21/12 9:21:35.774 PM com.apple.backupd[320]: Found 7193 files (1.53 GB) needing backup
    8/21/12 9:21:35.829 PM com.apple.backupd[320]: 3.24 GB required (including padding), 746.69 GB available
    8/21/12 9:21:50.673 PM mdworker32[326]: CGSGetDisplayBounds: Invalid display 0x00000000
    8/21/12 9:24:10.720 PM mdworker[302]: FontImporter: Validation failed - "/Library/Application Support/Adobe/PDFL/9.0/Fonts/Adobe Sans MM".
    8/21/12 9:24:10.000 PM kernel[0]: Sandbox: sandboxd(348) deny mach-lookup com.apple.coresymbolicationd
    8/21/12 9:24:10.721 PM mdworker[302]: FontImporter: Validation Result - "(
        kATSFontTestSeverityFatalError
    8/21/12 9:24:10.756 PM mdworker[302]: FontImporter: Validation failed - "/Library/Application Support/Adobe/PDFL/9.0/Fonts/Adobe Serif MM".
    8/21/12 9:24:10.757 PM mdworker[302]: FontImporter: Validation Result - "(
        kATSFontTestSeverityFatalError
    8/21/12 9:24:10.766 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.771 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.776 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.782 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.787 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.807 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.811 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.815 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.818 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.822 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.825 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.829 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.833 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.836 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.840 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.844 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.847 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.851 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.855 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.858 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.862 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:12.070 PM mdworker[302]: FontImporter: Validation failed - "/Library/Application Support/Adobe/PDFL/9.0/Fonts/Symbol".
    8/21/12 9:24:12.070 PM mdworker[302]: FontImporter: Validation Result - "(
        kATSFontTestSeverityFatalError
    8/21/12 9:29:12.941 PM mdworker32[369]: CGSGetDisplayBounds: Invalid display 0x00000000
    8/21/12 9:31:50.000 PM kernel[0]: (default pager): [KERNEL]: ps_allocate_cluster - send HI_WAT_ALERT
    8/21/12 9:31:50.000 PM kernel[0]: macx_swapon SUCCESS
    8/21/12 9:32:09.604 PM Dock[218]: no information back from LS about running process
    8/21/12 9:34:41.169 PM firefox[423]: -_scrollPhase is deprecated for NSScrollWheel. Please use -momentumPhase.
    8/21/12 9:34:41.169 PM firefox[423]: -_continuousScroll is deprecated for NSScrollWheel. Please use -hasPreciseScrollingDeltas.
    8/21/12 9:34:41.170 PM firefox[423]: -deviceDeltaY is deprecated for NSScrollWheel. Please use -scrollingDeltaY.
    8/21/12 9:34:41.170 PM firefox[423]: -deviceDeltaX is deprecated for NSScrollWheel. Please use -scrollingDeltaX.
    8/21/12 9:41:43.490 PM helpd[268]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
    8/21/12 9:41:43.491 PM helpd[268]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
    8/21/12 9:41:43.513 PM helpd[268]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
    8/21/12 9:41:43.513 PM helpd[268]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
    8/21/12 9:44:02.000 PM kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
    8/21/12 9:44:02.000 PM kernel[0]: macx_swapon SUCCESS

  • Time machine takes very long time

    Time machine takes very long time to write the back up.
    For writing 2,33 GB (from 26,33GB) it takes abou14 hours and I don't know, why it is so very slow. I work with USB 3.0 2 TB external hard disk drive.

    Try Here  >  http://pondini.org/TM/D2.html
    From Here  >  http://pondini.org/TM/Troubleshooting.html

  • Time machine taking too long (indexing)

    I run my time capsule to back up both of my computers
    a Imac 2GHz intel core duo running 10.6.8  and
    an Imac 3.4GHz intel core i7 running 10.7.4
    both are connected wirelessly to the Time Capsule
    Recently, on the older machine, backups have stalled. I can work on it for a while, doing disk repairs and disk permissions with the Snow Leopard installation disk utility and 'fix' it for multiple backups - and all is well.  Then it stalls on 'indexing backup' again.  Meanwhile, the new machine running Lion is just fine.  I just noticed it again.
    Last successful backup was 0517 this morning (EST) and this was at approx 1700 (5 evening).  I sat at the computer and was working away when Snow Leopard became really slow and I noted that the Time Capsule was indicating indexing backup, I let it run for 45 minutes and it was still indexing backup, so I quite Time Machine and restarted at 1845 (645 evening).  The restart of Time Machine allows Snow Leopard to regain its usual speed, Time machine reported a file count of 202 files that had changed and went to 'indexing backup'  a half hour later it is still at 'indexing backup'  (about 9 emails were received - how that relates to 202 files I am not sure)
    Why does it work multiple times just fine and then all of a sudden stall?  When it does stall it simply (over time I presume) eats up all available memory (1.5 gb)  with page swaps each one getting bigger and bigger until all memory is gone.  I can 'free memory' and recover to about 600 free (running email and browser app in the background) but the time machine does it all over again if I allow it to run.
    As I said, I have used Disk Utility (with the Snow Leopard Installation disk to allow repair of the boot volume) and have repaired the disk and repaired permissions - several times. (some disk permissions are repaired - no disk repairs reported)  After each time, I go back and restart Time Machine and 'poof' within an hour it performs a backup with no problems.  I note that backups are performed on schedule for the next few days with no problems, and then bingo, the system is totally bogged down again, and Time Machine is stuck on indexing backup once again.   I have not noticed any commonality as to when the problem occurs - sometimes after a day, sometimes after several days.  And meanwhile, the Lion machine is performing flawlessly 
    At the moment my kludge to work around is to turn off Time Machine so as not to use up all the memory and then periodically use the installation disk routine to 'repair'  (disk and permissions) and then backup, but this is NOT solving the problem long term of course.
    The first time I noticed this (about two months ago) the disk repair did note a disk error the system was claiming 2 bytes less free space than there was, but after that time, all the disk repairs report fine.

    Indexing can take a long time over wireless. You would do much better with ethernet connection.
    Maybe the hard drive is failing.. The fact that the disk passes tests does not mean it is ok. As a disk ages it can have issues reading, where the same sector has to read multiple times.
    I guess the ideal would be replace the machine.. it is several years old and really due for replacement.
    Or at least the hard disk... although the cost of doing that job might not be worth it.
    As a test I would do a backup using TM to a USB local disk plugged into it... that is good practice anyway when you are getting poor reliability on backups.
    You can create a disk image using a other tools.. CCC or superduper.
    A clone of the existing drive again can be worth it.
    You can set to boot from FW drive and ignore the internal.. see if the problems go away.
    Pondini is usually helpful although he doesn't have specific on this indexing issue.
    http://pondini.org/TM/Troubleshooting.html

  • Time machine taking too long.

    Time machine is backing up with an external disk. Its about 230GB but is taking more than one day and still less than the half. is this ok?

    Yes, I read, thanks.
    The excerpt says can be very very slow but dont specify how long. in my case more than one day.
    Not solving the problem yet. I gave up for now because already one day and a half and still doing backup (half of the 230GB).
    My computer is a 2.7 Core i7 with 16GB .
    If I wait the 3 days Backup that I see could take, for the rest of backups I have to wait the same ?
    I am copy like the old times, all my docs and folders.

  • After formatting and creating two partitions on my external HD, why is Time Machine taking 25x longer to perform a backup?

    Hi.
    I bought a macbookpro 13"retina, new two weeks ago and a G-tech 1TB external drive from the apple store. It's my first mac.
    I performed a backup, using Time Machine, which copied 18 GB onto he 1TB external HD in around 20 minutes.
    After a little more reading, I realised I should use Disk utility to partition the 1TB external G-tech drive into a 250gb partition, and a 750gb partition.
    [My MBP has a 250gb flash HD. I'll use the other 750gb for storage of my other files, like photos, music etc.]
    So, using disk utility I formatted the 1TB exernal drive, then created two partitions.
    However, I've started backing up my data using time machine again, onto the 250gb partition, on the external drive, and its now taking 5 hours to copy the 19.81GB
    So why is it taking 25x longer than the first time I did it? [First time it took 20 minutes]
    Thanks

    Since performing the fist backup, a couple of days ago, which took twenty minutes, and the second backup, which is taking 5 hours, I installed MS office for Mac 2011 and Silverlight.
    Dont know if thats responsible?

  • Time Machine taking too long (OS X 10.8.3).

    To any one who can help,
    I did the regular schedueled backup on an external HD and it took forever to prepare the backup, and then another long time to clear old backups. It now says it has to backup 171.69GB and it's been stuck at 7.3MB for hours!
    To try and solve the issue, I cancelled the backup and did what many forums suggest by deleting de /com.apple.TimeMachine.plist but it didn't help much. 3 hours on the clock and still only 7.3MB. Please help, I have OS X 10.8.3, Mac Book Pro.

    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.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • New backup to Time Machine taking ridicously long. Is this normal?

    I bought a brand new 1TB WD Mybook external drive to use for my Time Machine backups. It is connected via USB to my Macbook Pro 15" running Leopard 10.5.7. This is my first back up to Time Machine and I have only about 110GB of data for backing up. I have been backing up now for about 28 hours and the Time Machine status bar still says it only has backed up 864MB of 110GB. This cannot be right can it? Does anyone have any suggestions? Should I just continue to wait it out? Please help.

    V.K. wrote:
    PT wrote:
    Time Machine doesn't really care if the volume is GUID or MBR,
    yes, it does.
    http://support.apple.com/kb/TS1550?viewlocale=en_US
    It is referring to drives that use Master Boot Record (MBR) partition type, not GUID or APM, causing that issue. It then goes on to tell you how to reformat the drive for either GUID or APM for use with Time Machine.
    While the article does suggest one type for Intel Macs and another for PowerPC Macs, that really only matter if you are trying to make a bootable drive. Since TM volumes are not bootable, you can use either sceme.
    Regards,
    Patrick
    EDIT Whoops sorry about that. I read your original post and my mind substituted APM for MBR (as you can see in my reply here). But then when I re-read your post I see you were talking about Master Boot Record and NOT Apple Partition Scheme.
    Silly me!
    Message was edited by: PT

  • Time machine takes very long time and does not finish the backup

    Hi,
    Time machine is unable to backup my 2014 Mackbook Air 128 GB Drive anymore.
    I have tried numerously to initiate a backup but it could only backup a very small volume, less than 1KB, then stall for hours without any progress.
    I tries to repair my volume, using the Disk Utility, but it still does not backup, except for the 1K progress.
    I have noticed that "Spot Light" indexing is also taking forever.  It has been indexing for days without any pogress.
    What is going on.
    What should I do to fix it.
    My latest successful backup was on Jul 25.
    Please help.
    Thanks.
    Tareq

    These instructions must be carried out as an administrator. If you have only one user account, you are the 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.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
    Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
    CLEAR THE WORD "Starting" FROM THE TEXT FIELD
    so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    ☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
    ☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    ☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Time Machine takes very long time to back up with new large drive

    I started using Time Machine on my 17" MBP about a month ago. I was using a 250 GB Samsung drive. When I discovered that TM will back up other external drives (I have several firewire pocket drives), I purchased a 500 GB Cavalry drive with USB 2.0 and eSATA connections. The first backup of my MBP drive (about 85 GB) took several hours (4-6?). I backed up one of my pocket drives (about 60 GB), which took 3-4 hours. Then, when I changed the back-up drive in Time Machine to the new 500 GB drive with the eSATA connection, I stopped it after an hour, because only 2 GB had been backed up. I erased the drive and restarted using the USB connection. It backed up 3 GB in an hour. So, now I'm back to using the original back-up drive. I've performed benchmark tests on all drives (the Samsung 250, Cavalry USB and eSATA 500 GB, and the MBP internal drive) with Xbench. The USB speeds on the Samsung and Cavalry drives came out about the same with a slight edge to the Cavalry drive. The eSATA connection with the Cavalry drive operated at over twice the speed of the USB connections and at about twice the speed of the MBP internal drive (which is a 1.5 Gb/s SATA drive). Basically, I can't figure out why Time Machine takes so incredibly long to back up when I switched to the new drive. Any ideas?
    Jeff

    It took me 20 hours to backup 32GB out of 65. I don't know why. Using carbon copy clone to download to another backup drive I did it perfectly in about 30 minutes. I expect that those appllications which show applicatiions are at fault and will try later getting rid of apps such as F-10 and pathfinderfor the first download. I have no idea why this is so slow. Everything is so slow.

  • Time Machine spending a LONG time Preparing Backup

    I've upgraded to MAverick nd everything seems to be working. However time machine has spent the past 24 hours saying that it's prep[aring the backup. Part of this time it changed the messaged to say deleting old backups....
    Then it says backup failed..
    Any suggestions on what is happening?
    I'm tempted to wipe the time achine drive and start from scratch but thought that I'd ask you good folks first.
    Thanks!

    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.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to an abnormal backup. Now
    CLEAR THE WORD "Starting" FROM THE TEXT FIELD
    so that all messages are showning, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste (command-V) into a reply to this message.
    If all you see are messages that contain the word "Starting," you didn't clear the text field.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • After entering Time Machine-takes a long time to load. Thoughts?

    I've just installed Yosemite, and backed up to my Time Capsule over wifi. I can enter Time Machine easily enough, but when I go to choose a date earlier than 'NOW," it says "waiting." Eventually, it loads. But it can take up to 15-20 minutes. I didn't have this problem before upgrading to Yosemite. Thoughts? Thanks much.

    It took me 20 hours to backup 32GB out of 65. I don't know why. Using carbon copy clone to download to another backup drive I did it perfectly in about 30 minutes. I expect that those appllications which show applicatiions are at fault and will try later getting rid of apps such as F-10 and pathfinderfor the first download. I have no idea why this is so slow. Everything is so slow.

  • Copying time machine disk for long time archive

    not certain this is correct forum.
    I have a 1 gb raid ext drive (two 1gb disks in raid 1). I use it as my Time Machine drive. It is now full.
    I want to copy this data to a single 1GB drive, put it in permanent storage, and then reformat and reuse the raid drive as time machine #2.
    This, I hope, would allow me to have the security of a raid setup as my current time machine disk and, when it is full, I can copy to another disk, then continually reuse the raid disk, within reason, of course, as my latest Time Machine disk #4, etc.
    Can I do this and how would I do this?.

    I think you can still do that with incremental backups to a clone, but I'm not certain.
    I poked around Pondini's Time Machine FAQ and didn't see anything about making a duplicate of the TM disk.
    As I stated earlier, I think it would work. And, I would imagine CCC or SuperDuper could clone the TM drive.
    Searching for cloning a Time Machine drive I found this: http://hints.macworld.com/article.php?story=20071128055047339
    and this: http://help.bombich.com/kb/troubleshooting/cloning-a-time-machine-backup
    and this (which is much like the first, with pictures): http://www.macyourself.com/2008/12/10/how-to-copy-your-time-machine-backups-to-a -new-larger-drive/

  • Why is time machine taking so long to back up!

    I have a 13 inch (Late 2011) Macbook Pro and I need to know why its backing up so slow! I only have 20GB used up on my computer! Is this normal, Help!!!!

    ismail2000 wrote:
    my brand new Time Capsule.
    You never reported back that you read the link I posted.  You are under warranty.  Call Apple tech support.

Maybe you are looking for

  • Print Problems on new Canon Pixma 100 Pro

    I have a new canon pixma 100 pro pinter and want to print the best possible prints. Can someone point me to a detailed description of how to print in Aperture including the use of icc profiles (the difference between using icc profiles and printer ma

  • Web Service vs. Enterprise Service

    Hi all, what is the difference between this two things. I have built a web service on my own. But what is an enterprise service? And what is the difference between the UDDI for web services and the ESR?? regards

  • In system profiler it says "unable to list firewire devices"

    I have been trying to figure out for days why when I hook up my camcorder with a firewire that all that comes up on my screen is the isight camera and not my camcorder. I have tried everything. I finally went into the system profiler and checked my f

  • Bank Gurantee Process for Account Payble in SAP

    Dear Support,    We have a requirement to Implement the Bank Gurantee Process for Account Payble in SAP, So please provide any usefull link or process map document in SAP , means how to implement BG process and what will be the transaction and proces

  • I am having ALL SORTS of problems since downloading fox fire,I am afraid I am damaging my new computer

    When I try to watch a video sent to me on facebook,when I try to go to my yahoo,when I first downloaded I believe I have duplicate add-ons because they were not loaded,my Norton anti-virus does not allow afew of the foxfire add-ons etc,etc,etc can so