APFS changes in Big Sur: how Time Machine backs up to APFS

Re:APFS changes in Big Sur: how Time Machine backs up to APFS by mrpippy on Monday September 28, 2020 @11:33PM (#24623948)

That’s bizarre, I have no idea why anyone would recommend HFS+ for that. It’s a Linux system running Netatalk, which uses normal POSIX file I/O. ext4 is a far better choice.

Cargo-cult HOWTOs is the only explanation I can think of.

[ Parent | on HN ]

Re:APFS changes in Big Sur: how Time Machine backs up to APFS by snapetom on Tuesday September 29, 2020 @01:10AM (#24624342)

> Cargo-cult HOWTOs is the only explanation I can think of.

Pretty much. When I google "raspberry Pi time machine," every result I see, except one, tells you to do the HFS+/AFP method. These results include content churning sites like techradar and howtogeek.

The only site that recommends ext4/smb that comes up, fourth on my list of results, is this one: https://mudge.name/2019/11/12/using-a-raspberry-pi-for-time-...

[ Parent | on HN ]

Re:APFS changes in Big Sur: how Time Machine backs up to APFS by duskwuff on Monday September 28, 2020 @11:52PM (#24624016)

netatalk is also the wrong solution nowadays. AFP is unmaintained, both on the netatalk side and on macOS. Instead, Samba supports Time Machine backups via the "fruit" (!) extension, which also provides some nice performance improvements for macOS clients.

https://manpages.debian.org/buster/samba-vfs-modules/vfs_fru...

TL;DR though: add the following configuration to the global section of your smb.conf:

    vfs objects = fruit streams_xattr
    fruit:aapl = yes
    fruit:metadata = netatalk

And under the section for your Time Machine share:

    fruit:time machine = yes

[ Parent | on HN ]

Re:APFS changes in Big Sur: how Time Machine backs up to APFS by nikisweeting on Tuesday September 29, 2020 @02:12AM (#24624621)

SMB on ZFS also works excellently, 4 years and counting with many power losses, ungraceful ejections, etc. never a corrupted backup.

[ Parent | on HN ]