• Time Machine unbelievably slow


    rctneil
    • Minor
    Message added by limetech

    Please be aware that these comments were copied here from another source and that the date and time shown for each comment may not be accurate.

    Hello,

    I have a Time Machine share set up on my server to backup my MacBook Pro too but it's unbelievably slow.  Any suggestions how to speed it up or figure out why it's slow?

     

    I'm using a 2017 13" MacBook Pro running Catalina 10.15.2. Connected via Ethernet as well.

     

    All suggestions very much welcome!

     

    Thanks,

    Neil

     

    Edit: As per @limetech instructions I have attached diagnostics:

     

     

    tardis-diagnostics-20200204-2055.zip

    • Like 1



    User Feedback

    Recommended Comments



    8 minutes ago, phunktional said:

    Share is in the array.


    Very strange, you are in my exact situation, I also disabled hard links, but I still have very slow backups with Time Machine.

    Link to comment

    If you can guarantee your Time Machine data will always only exist on a pool (or a single disk) you might get some speed improvement by bypassing shfs. Please verify these instructions because it's been a while since I tested.

     

    NOTE: Because we'll be specifying the share options manually changes to the share with the webgui will be ignored. Make sure the share's settings are already optimized for time machine before proceeding.

     

    1. Record your time machine share's settings from this file:

    cat /etc/samba/smb-shares.conf

     

    2. Stop the array

     

    3. Go to Settings -> SMB -> SMB Extras and verify this line exists near the bottom. If it doesn't, create it

    include = /boot/config/smb-custom.conf


    3. Add your time machine share's settings recorded in Step 1 to /boot/config/smb-custom.conf replacing user in the path line with your pool's name, e.g. for pool named "fast"

    path = /mnt/user/Time-Machine

     

    becomes:

    path = /mnt/fast/Time-Machine

     

    4. Save and start the array

     

     

    Edited by CS01-HS
    Link to comment
    9 hours ago, Gian Marco Cinalli said:


    Very strange, you are in my exact situation, I also disabled hard links, but I still have very slow backups with Time Machine.

    Time Machine has never been very fast for me, I mostly care about reliability. I use TimeMachineEditor to only backup to my Unraid server once per day and I record hourly local snapshots (every snapshot is included during the once daily backup).

    • Like 1
    Link to comment

    Just thought I'd add my experience with this in case it helps others. I had a ~250GB time machine backup trying to complete, the last one having been made back in June sometime. Every time I ran it, the speeds were painstakingly slow and it eventually just failed. I would come back to it in the morning and it had just stopped.

     

    Based on this thread, the things I did that finally got this working:

     

    • Turned off hard link support (Settings/Global Share Settings/Tunable (support hard links))
    • Changed the Time Machine share to use private authentication, with my username/password combination, rather than public
    • Turn on "Case Sensitive": (Settings > SMB > SMB Extras and add "case sensitive = yes", then save.
    • Also turned on "Case-sensitive Names" on the Time Machine share itself: (Shares > Time Machine > SMB Security Settings > Set Case-sensitive Names to "Yes" and save
    • Deleted the entire Time Machine backup (but kept the share) and started the backup on my Mac from scratch

     

    I didn't do anything with pools/single disk etc. Can't say which of the above specifically solved this, but I'm just happy that it's now working. I started a 341 GB backup around 10am yesterday, and  by 3:30pm it had done 150GB, completing at 8:51pm all over wi-fi. Screenshots attached

     

     

    Screenshot 2021-09-08 at 15.39.53.png

    Screenshot 2021-09-09 at 05.16.38.png

    Screenshot 2021-09-09 at 07.55.17.png

    • Like 1
    Link to comment
    1 hour ago, gooner_47 said:

    Just thought I'd add my experience with this in case it helps others. I had a ~250GB time machine backup trying to complete, the last one having been made back in June sometime. Every time I ran it, the speeds were painstakingly slow and it eventually just failed. I would come back to it in the morning and it had just stopped.

     

    Based on this thread, the things I did that finally got this working:

     

    • Turned off hard link support (Settings/Global Share Settings/Tunable (support hard links))
    • Changed the Time Machine share to use private authentication, with my username/password combination, rather than public
    • Turn on "Case Sensitive": (Settings > SMB > SMB Extras and add "case sensitive = yes", then save.
    • Also turned on "Case-sensitive Names" on the Time Machine share itself: (Shares > Time Machine > SMB Security Settings > Set Case-sensitive Names to "Yes" and save
    • Deleted the entire Time Machine backup (but kept the share) and started the backup on my Mac from scratch

     

    I didn't do anything with pools/single disk etc. Can't say which of the above specifically solved this, but I'm just happy that it's now working. I started a 341 GB backup around 10am yesterday, and  by 3:30pm it had done 150GB, completing at 8:51pm all over wi-fi. Screenshots attached

     

     

    Screenshot 2021-09-08 at 15.39.53.png

    Screenshot 2021-09-09 at 05.16.38.png

    Screenshot 2021-09-09 at 07.55.17.png

     

    Unfortunately, what happened is normal, the first backup always goes very well, it is from the second that they start to slow down incredibly.

    Link to comment
    25 minutes ago, gooner_47 said:

    Interesting, I haven't experienced this. All my backups today have completed in good time.

     

     

    Keep an eye on it then and let us know if indeed everything continues to go as it should.

    Link to comment

    In case it helps anyone... I ran 

    sudo fs_usage -w | grep Volumes.Backups

    to see what was accessing my backups volume, besides my backup software. (I'm using Carbon Copy Cloner instead of Time Machine.)

     

    It turns out that Finder was updating every time the directory was being written, because I had a window open to the directory. After closing that window, speeds shot up.

     

    Hopefully that helps someone...

    Link to comment
    On 9/9/2021 at 2:16 AM, gooner_47 said:
    • Deleted the entire Time Machine backup (but kept the share) and started the backup on my Mac from scratch

     

    Can't say which of the above specifically solved this...

    I'm going to guess it was the last one you tried that 'fixed' it 🧐

     

    btw, I've got the same issue too and I have to delete the entire sparsebundle and completely start over every time it gets borked (haven't tried running TM outside the array yet.) Frustrating to say the least!

    Edited by Joseph
    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.