Samba timemachine config

_etc_avahi_services_samba.service

<?xml version="1.0" standalone='no'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
 <name replace-wildcards="yes">%h</name>
 <service>
   <type>_adisk._tcp</type>
   <txt-record>sys=waMa=0,adVF=0x100</txt-record>
   <txt-record>dk0=adVN=Time Capsule,adVF=0x82</txt-record>
 </service>
  <service>
    <type>_smb._tcp</type>
    <port>445</port>
  </service>
</service-group>

_etc_samba_smb.conf

[global]

wins support = yes
workgroup = WORKGROUP
netbios name = SAMBA
vfs objects = acl_xattr fruit
map acl inherit = yes
store dos attributes = yes
security = user
valid users = @shareaccess
username map = /etc/samba/users.map

passdb backend = tdbsam:/etc/samba/passdb.tdb
guest ok = no
read only = no

# Time Machine
durable handles = yes
kernel oplocks = no
kernel share modes = no
posix locking = no
fruit:advertise_fullsync = true
smb2 leases = yes

# Security


client ipc max protocol = default
client max protocol = default
server max protocol = SMB3

client ipc min protocol = default
client min protocol = CORE
server min protocol = SMB2


[Time Capsule]

path = /tank/Backups
browseable = Yes
vfs objects = catia fruit streams_xattr
fruit:aapl = yes
read only = No
inherit acls = Yes

For more background, see also the (official) thread on Samba 4.8.0:

• samba-team/samba#64

If you are using ZFS and want a huge speedup (not just for time machine):

• Make sure you activate storage of xattr in inode for zfs: http://www.nerdblog.com/2013/10/zfs-xattr-tuning-on-linux.html
• Set fruit:resource = xattr in smb.conf

This will store resource forks directly in inodes instead of littering the place with ._ AppleDouble files.

None of above works

Use this: https://kirb.me/2018/03/24/using-samba-as-a-time-machine-network-server.html

If anyone is still having issues make sure you don't have oplocks and level 2 oplocks disabled.

Time Machine would not work with the following in my config file

level2 oplocks = no                                                                   
oplocks = no   

Has anyone encountered:

Time Machine can’t connect to the backup disk. The operation couldn’t be completed. (OSStatus error 13.)

After they type their password on the time machine menu