sky step

Q: Time Machine very slow after upgrade to El Capitan

Time Machine very slow after upgrade to El Capitan (MacBook Air (13-inch, Mid 2011), 1,7 GHz Intel Core i5, 4 GB 1333 MHz DDR3,)

 

I upgraded my MacBook Air to El Capitan about 3 weeks ago. I previously used os x 10.7.4.

 

After 3 weeks it never managed to achieve a complete time machine backup on my Time Capsule (connected by ethernet).

 

The message was 1 MB of 34 GB - about ... (many hours) remaining

after several hours calculating time

 

So I decided to take a look on the forums and found some advise to stop spotlight for the time time machine was going.

Using terminal commands like "mdutil -da" and excluding all disks from spotlight and stopping all processes in activity monitor, Time Machine finally accepted to do the job in a couple of hours.

 

But is there a solution to use time machine "normally" every day.

In this moment have the message : "9 MB of 288 MB - About 6 hours remaining"

This does not seem normal.

 

My question is : is Apple about to do something about this problem which seems widely known even in the discussions here ?

Or would I better restore to my previous OS 10.7.4 (Time Machine was not very fast either but it still completed in less than a couple of hours)

 

I also use 2 disks

1) the time capsule (the backup always was a little slow)

2) a USB hard drive : before upgrading the backup never took more than several minutes, after upgrading it was more than 10 hours !

 

Thank you for any help.

MacBook Air, OS X El Capitan (10.11.1), (13-inch, Mid 2011), 1,7 GHz Intel

Posted on Nov 14, 2015 10:15 AM

Close

Q: Time Machine very slow after upgrade to El Capitan

  • All replies
  • Helpful answers

  • by a brody,

    a brody a brody Nov 14, 2015 10:19 AM in response to sky step
    Level 9 (66,876 points)
    Classic Mac OS
    Nov 14, 2015 10:19 AM in response to sky step
    My question is : is Apple about to do something about this problem which seems widely known even in the discussions here ?

    What if anything Apple would be doing would be pure speculation.    As such, this discussion forbids all speculation.

     

    USB hard drives are actually slower than Firewire when it comes to USB 2.   They are limited to several things:

     

    1. The power of devices on their port.

    2. The number of devices sharing the same bus.

    3. The amount of data being shared on the bus.

     

    Your System Profiler under the USB section can give you more information when you hook it up to each port.   If you are seeing a slowdown, it is likely for one of those reasons.   Also as a general rule of thumb, you don't want hard drives to become over 85% full, or your Time Machine backup drive to be less than twice the size of the original hard drive to avoid slowness.

  • by sky step,

    sky step sky step Nov 14, 2015 10:34 AM in response to a brody
    Level 1 (0 points)
    Nov 14, 2015 10:34 AM in response to a brody

    Thank you for your reply.

    I don't think the free space can be the cause of my problem :

    My Time capsule is about 50% full of 1Tb

    As for the USB hard drive I use a partition of 160 Gb and my main SSD is 120.

    But it was quite fast before El Capitan.

     

    Does System profiler mean System Information ?

    I certainly found some information about my USB disk but none on the bandwidth used on the port.

     

    Anyway I can not see something justifying 6 hours of transfer for less than 300MB ?

  • by Linc Davis,

    Linc Davis Linc Davis Nov 14, 2015 1:32 PM in response to sky step
    Level 10 (208,000 points)
    Applications
    Nov 14, 2015 1:32 PM in response to sky step

    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 and start typing the name.

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

    When you post the log extract, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

    If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

  • by sky step,

    sky step sky step Nov 15, 2015 2:00 AM in response to Linc Davis
    Level 1 (0 points)
    Nov 15, 2015 2:00 AM in response to Linc Davis

    Thank's for your help.

    Here is the link : http://pastebin.com/8xy0tnnW

    About 2000 lines in several minutes.

    Time machine still announces 30 minutes left for 236 MB on the time capsule.

  • by Linc Davis,

    Linc Davis Linc Davis Nov 15, 2015 5:45 AM in response to sky step
    Level 10 (208,000 points)
    Applications
    Nov 15, 2015 5:45 AM in response to sky step

    Please read this whole message before doing anything.

    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.

    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

    Test while in safe mode. Same problem?

    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • by sky step,

    sky step sky step Nov 15, 2015 7:20 AM in response to Linc Davis
    Level 1 (0 points)
    Nov 15, 2015 7:20 AM in response to Linc Davis

    Here are the logs :

    Time capsule : http://pastebin.com/gmW8Ci6e

    About 30 min for 430 MB

    (I still think it's not reasonable)

     

    USB disk : http://pastebin.com/pVzScqg5

    About 5 min for 460 Mb

    (Probably normal time)

     

    What I observed repeating in the logs :

    15/11/2015 15:09:39,603 com.apple.xpc.launchd[1]: (com.apple.watchdogd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

    15/11/2015 15:09:47,490 secd[305]:  SOSAccountThisDeviceCanSyncWithCircle sync with device failure: Error Domain=com.apple.security.sos.error Code=1035 "Account identity not set" UserInfo={NSDescription=Account identity not set}

    15/11/2015 15:09:49,657 watchdogd[499]:  [watchdog_daemon] @(    wd_watchdog_open) - IOIteratorNext failed (kr=0)

    15/11/2015 15:09:49,658 watchdogd[499]:  [watchdog_daemon] @(      wd_daemon_init) - could not open connection with the kernel watchdog

    15/11/2015 15:09:49,658 watchdogd[499]:  [watchdog_daemon] @(                main) - cannot initialize the watchdog service

     

    Thank's again for your help

  • by Linc Davis,

    Linc Davis Linc Davis Nov 15, 2015 7:32 AM in response to sky step
    Level 10 (208,000 points)
    Applications
    Nov 15, 2015 7:32 AM in response to sky step

    I don't think any more log extracts are needed. The question was whether Time Machine works better in safe mode.

  • by sky step,

    sky step sky step Nov 15, 2015 8:11 AM in response to Linc Davis
    Level 1 (0 points)
    Nov 15, 2015 8:11 AM in response to Linc Davis

    Not much better

    Here is the data :

    In safe mode : Time capsule backup time = 32 minutes for 430 MB saved

    In normal mode : Time capsule backup time = 35 minutes for 470 MB saved

     

    In safe mode : USB disk backup time = 5 minutes for 460 MB saved

    In normal mode : USB disk backup time = 7 minutes for 450 MB saved

  • by Linc Davis,

    Linc Davis Linc Davis Nov 15, 2015 8:48 AM in response to sky step
    Level 10 (208,000 points)
    Applications
    Nov 15, 2015 8:48 AM in response to sky step

    You wrote earlier that the backups to the USB drive were taking hours. It seems now that they're running normally. The problem is the Time Capsule. How old is it?

  • by sky step,

    sky step sky step Nov 15, 2015 9:08 AM in response to Linc Davis
    Level 1 (0 points)
    Nov 15, 2015 9:08 AM in response to Linc Davis

    The time capsule is about 6 years old. But it still used to save in reasonable time on os x 10.7.4.

     

    It is true that the USB disk backup time gets regular for small incremental backups.

    It was very long for large backups of several GB.

    (about 30 Gb the first time, 4-5 Gb a few days later, ...)

  • by Linc Davis,

    Linc Davis Linc Davis Nov 15, 2015 11:48 AM in response to sky step
    Level 10 (208,000 points)
    Applications
    Nov 15, 2015 11:48 AM in response to sky step

    I would need to see the log of an abnormal backup to the USB drive. Otherwise I can't suggest anything except to replace the Time Capsule. After six years, its hard drive is ready to fail, if it hasn't already done so.

  • by sky step,

    sky step sky step Nov 16, 2015 9:12 AM in response to Linc Davis
    Level 1 (0 points)
    Nov 16, 2015 9:12 AM in response to Linc Davis

    Ok, I will wait a few days and try again when I have a larger volume to save.

    If it fails again I will save the logs.

     

    Thanks for your help

  • by ericj72,

    ericj72 ericj72 Jan 4, 2016 1:29 AM in response to sky step
    Level 1 (0 points)
    Jan 4, 2016 1:29 AM in response to sky step

    I had the same problem and wasted a lot of time searching forums, only to find very complicated answers that were out of my league.
    The incremental backup was 73Gb and it would take forever just to go up 0.1MB

     

    With everything I've read, I came to the conclusion that it had to do with re-archiving the existing backup with lots of changes.

    If my assumption was right, it left me 2 options:

    a) Go on faith and delete the backup like some recommended. I was too afraid to do that...

    b) Partition my drive in order to have a new destination where Time Machine could do a new Full backup while keeping the previous backup untouched on the other partition.

     

    I went with b) and so far so good. I have to do a 262Gb backup while the previous one that took forever was 73Gb.

    I just started approx 10 minutes ago and I'm at 8Gb. The transfer rate is good.

     

    If it works, then I could go back and maybe remove the partition and do a)

    The partition I did is only 400Gb out of a 1.5Tb drive. It's too small to keep a good history of TM.

  • by ericj72,

    ericj72 ericj72 Jan 6, 2016 5:27 PM in response to sky step
    Level 1 (0 points)
    Jan 6, 2016 5:27 PM in response to sky step

    UPDATE: This fresh new backup on the partition worked perfectly and went to 100% without any problems.

     

    But I was still not ready to erase my full original backup and loose everything so here's what I did and it worked.

    In Finder, I've opened the folder Backups.backupdb and started deleting some subfolders for dates in 2011-2012-2013. For those years, I kept only one each quarter (January, April, July, September and the last one of the year). Then for 2014, I kept one per month. For 2015, I kept them all.

     

    Then I emptied the Trash which took overnight because it had over 3 000 000 items to delete.

     

    I started the backup this morning around 8AM and left for work. It was doing this very long "Preparing Backup" when I left.

    When I got back from work, the backup was done and it said it was done at 2h48pm. A reasonable time compared to the approximative 185 DAYS !!!! it was going to take originally at the speed it was doing the full backup.