On disks formatted with APFS in MacOS 10.13 High Sierra, files can't be shared over AFP anymore (see this article on the Apple support site). As such, this guide here no longer works for making a TimeMachine backup location on an Ubuntu server.

Does anyone have any thoughts on how to set up the TimeMachine backup destination to be visible over SMB? Or some other possible solution?

  • 1
    I'm unable to test the theory at this moment, but I have read in the past if you create a sparsebundle image on your Ubuntu server, then point the time machine to it, it should work. See here for possible info. I cannot guarantee it works, but it's worth looking in to. – nullmeta Sep 4 '17 at 20:02

[Updated answer]

On disks formatted with APFS in MacOS 10.13 High Sierra, files can't be shared over AFP anymore [...]

This is a popular misconception - you can back up an APFS volume to a Time Machine using AFP via Netatalk. Confusion stems from ambiguous wording on https://support.apple.com/en-gb/HT208018 :

Any Time Machine share points must be shared over SMB instead of AFP. [emphasis added]

This caught out a number of people (including me). The HT208018 support article is trying to say: you can't do fileserving of files from an APFS volume to other Macs using AFP and further, you can't use a Mac APFS volume as the destination for a Time Machine backup (see https://apple.stackexchange.com/a/299720 for a detailed explanation).

Having said all the above, you can also use Time Machine with an SMB server (such as Samba) if the SMB server advertises the correct options (see below). At the time of writing (1 Oct 2017) you're in for a mildly rocky ride when trying to use Samba because you have to do a custom compile of Samba in the near-term (it will likely be next year that an appropriate pre-built Samba turns up by default in the periodic release Linux distributions).

[Update 2]

The patches have gone in and will likely be part of the Samba 4.8 release (currently that future release is too new to have a date on https://wiki.samba.org/index.php/Samba_Release_Planning ).

[Update 3]

The changes are now part of Samba 4.8 and above.

[Original text below]

The short of it is keep an eye on https://github.com/samba-team/samba/pull/64 and the mailing list thread related to it over on https://lists.samba.org/archive/samba-technical/2017-September/thread.html#122882 because something like it will have to go in for Time Machine to work with Samba without extra manual configuration on the Mac.

It's unclear how much Apple care about Samba these days (which started occurring when they stopped shipping it with MacOS after the Samba project switched to be GPLv3) so I'm afraid delays are to be expected. Let's see how it goes - kevinanderson1, omor1 and Ralph seem to be making progress so good luck to them!

  • 1
    Thanks for the comprehensive response about the status of this issue. I've upvoted, but I won't yet accept, since I'm hoping someone will come along with some kind of updated step-by-step guide for other people in the future with this problem. – Daniel Porteous Oct 25 '17 at 10:16
  • @DanielPorteous the question is - will you accept this answer if no one gets around to doing that ;-) – Anon Oct 26 '17 at 5:57

There are instructions at:


It involves getting Samba 4.8 or higher (4.9.3 is current as of 30 Nov 2018) and compiling it locally. I'm on Ubuntu 16.04 LTS and had to add a few updates (lmdb, gnutls) before I got it to compile, but that was simple with brew. I followed the directions but still can't see the share from my Mac. :-(

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.