TimeMachine - NetaTalk and High Sierra

  • Hi!


    As you probably know, Apple will release High Sierra soon. High Sierra comes with a new filesystem that is mandatory for all SSD based machines.


    With this upgrade of filesystem comes a change to TimeMachine. TimeMachine used to use AFP/NetaTalk, but will from this release use SMB. This might be a major issue. Especially since Apple requires proprietary extensions to SMB for timeMachine to work.


    Has someone started looking into this? Will this be supported by OMV at time of release of High Sierra? Any info on this at this point?

    • Offizieller Beitrag

    It has been discussed although I can't find the thread right now. Even Debian 9/OMV 4.x only has samba 4.5 and the time machine extensions patch needs samba 4.6 as far as I know. I have tried compiling Debian 10's samba 4.6.7 (which may not have the extensions either) on Debian 9 and it fails. OMV generally uses the packages in the Debian repo. So, not sure how this one will be resolved. You may have to do something like this.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Einmal editiert, zuletzt von ryecoaaron ()

  • Well, sounds like this upgrade of MacOS is going to hurt. Time Machine on OMV is one of the most used features in my house! Compiling from source should in my book be a last resort. It adds a lot of complexity/responsibility to the sysadmin of the OMV box.


    Hoping for a solution.

  • But this indicates that Netatalk is not really needed anymore soon

    I disagree since older macOS clients still need performant access to OMV shares (also doing backups).


    I tested a few months ago at several clients serving macOS machines with a self compiled Samba but the journey wasn't that smooth (and before Ralph, remaining Netatalk developer and the SerNet guy coding all the Apple relevant Samba stuff in the meantime, sent me his smb.conf performance sucked a lot and we ran into a lot of concurrent access issues).

  • https://blog.macsales.com/4231…ra-and-apfs-compatibility



    APFS and Time Machine

    • You don’t need to change any Time Machine settings to back up APFS-formatted disks.
    • Any Time Machine share points must be shared over SMB instead of AFP.

    Translation: You should be able to connect your Time Machine backup drive to your APFS-formatted Mac and things should run as expected. The Backup Drive can be formatted as APFS or HFS+. If you share your Time Machine drive over a network, it will need to be shared over SMB rather than AFP (Apple Filing Protocol). Apple has been moving away from AFP for the past few iterations of macOS.

    Version7.0-32 (Sandworm)
    ProcessorAMD EPYC 7302P 16-Core Processor
    KernelLinux 6.1.15-1-pve
    HardwareDell R7515
  • Just FYI:
    In the latest discussions of the github PR it says, HighSierra can STILL backup to AFP. The question "How long" remains.


    I also tried to create a VBOX with HighSierra and I am also still able to just restore through an AFP connection.

  • Hi!


    Just wanted to let people know that it's possible to get it working through SMB with a few hacks.
    The patches to samba has been included in samba 4.8.0 - so i basically hand compiled that on a new OMV installation.


    The rough guide to that is

    • Follow this guide (Install OMV4 on Debian 9 (Stretch)) to get OMV 4 running on Debian 9 - P.s. note i did this on raspberry pi with raspbian and there a "apt-get install resolvconf" was required before running omv-initsystem (otherwise i got some errors)
    • Edit /etc/apt/sources.list to ensure you have a source code store configured (usually just need to remove a comment)
    • Follow below commands to compile samba. This will first install all tools and libraries required from the debian package stores, and then download a "vanilla" version of samba 4.8.0. The configure command is based on that used by debian samba maintainers so it look as much as the samba package as usual
    • The use of screen is optional - but the configure and compile process is quite slow. if you are running this over ssh the screen command will make sure the process runs on even if you looses the connection (when reconnecting type screen -r to see the result). Furthermore it's probably possible to do the compile as non-root but this way is a bit more hasslefree
    • When you are done, go into the webgui and for the share you want to use for timemachine type "fruit:time machine = yes" under extra options


    Also note that OS X has some bug regarding handling signing of samba authentication requests. This causes transfer speeds to drop to abysmal levels, so if you want to use this for backup you need to edit /etc/nsmb.conf (on your mac, not on your OMV) so it looks like the last source code piece


    /etc/nsmb.conf

    Code
    [default]
        signing_required=no
    • Offizieller Beitrag

    The patches to samba has been included in samba 4.8.0 - so i basically hand compiled that on a new OMV installation.

    4.8 is right now in experimental branch. I know a user here @thctlo that supplied some time ago samba backports for server-side spotlight


    How to spotlight-index an AFP share - best methods?


    Maybe if he has time he can give it a try with experimental branch to bpo for stretch. ATM he has 4.7


    http://downloads.van-belle.nl/…-stretch-unstable-apt.txt


  • Thank you very much for this step-by-step guide, my box is currently compiling. :)
    However it's not a good idea to configure and compile as the root user.
    In fact other projects even disallow doing so (linux kernel does so I think).
    Only the last 2 steps need root permissions afaik.


    So this should not take place in /root anyway, better would be /tmp (also for better speed) or just $HOME.
    Maybe you can adapt the steps a little.


    Edit: actually that doesn't work for me:


    Code
    Apr 12 11:01:38 homeserver smbd[1273]: /usr/sbin/smbd: error while loading shared libraries: libsmbldap.so.2: cannot open shared object file: No such file or directory

    Edi2: Ok didn't realize it was built for raspberry pi, aka ARM.


    My adjusted steps for x86 are here:

  • Hi,


    Just tried to get timemachine things working on my OMV3 Installation:


    - Got Samba 4.8.1 successfully compiled and installed
    - Samba is now 4.8.1 and my existing shares continue to work :)
    - tried to add a timemachine share via the Webinterface with the some of the following suggested options:


    Code
    fruit:aapl = yes
    fruit:time machine = yes
    kernel oplocks = no
    kernel share modes = no
    posix locking = no
    vfs objects = catia fruit streams_xattr


    Tried this by adding the above options via extended options, but this doesn't seam to work.
    Also I can't find the Share in the "TimeMachine" Options.


    After that I added the Share manually in the smb.conf, just to check if it's working, but again no success.


    Then I tried to add a avahi/bonjour setting to get Timemachine advertised, but the suggest Settings seams to conflict with the standard/default avahi smbd.service settings:




    Finally after disabling the smbd.service avahi announcement, the manually added timemachine.service avahi setting gets honored and now I can find my TimeMachine Share in the "Timemachine options" on my mac. Also the initial backup seams to work.


    The questions are now:


    - Do I really need to add all the settings manually in the config files ( and do they get overwritten by any actions in the web interface) ?
    - Any chance in simplify the whole process, maybe it's possible to pass some of the used options for the timemachine share ?
    - How about that avahi stuff, is it possible to add the timemachine options to the normal smbd.service settings , it seams to be similar in the basic settings, but my example of the timemachine.service has some more settings included ?


    Or do I over-complicate the whole thing and it's far simpler to get this up and runnning ?



    Regards,


    Markus

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!