So, Mac user here,
Before Unraid, I was running a rpi with an external drive setup for Time Machine. It works ok given the limitations of the rpis usb/nic/io etc. Now with unraid I wanted to make that more robust.
Watched Spaceinvaderone's videos, would work once then unable to complete incremental backups. Same Failed to attach using DiskImages2 errors.
added the suggested changes to smb conf, same failure for incremental backups
got excited for 6.11 and the macOS optimizations, same failure.
gave up and ran the docker version, initial backup and hourlies for the past 36 hours. Success!
now, according the the smb.conf from the docker app version, they use several different options in smb conf:
[global]
access based share enum = no
hide unreadable = no
inherit permissions = no
load printers = no
log file = /var/log/samba/log.%m
logging = file
max log size = 1000
security = user
server min protocol = SMB2
server role = standalone server
smb ports = 445
workgroup = WORKGROUP
vfs objects = acl_xattr fruit streams_xattr
fruit:aapl = yes
fruit:nfs_aces = yes
fruit:model = TimeCapsule8,119
fruit:metadata = stream
fruit:veto_appledouble = no
fruit:posix_rename = yes
fruit:zero_file_id = yes
fruit:wipe_intentionally_left_blank_rfork = yes
fruit:delete_empty_adfiles = yes
[TimeMachine]
path = /opt/timemachine
inherit permissions = no
read only = no
valid users = myusername
vfs objects = acl_xattr fruit streams_xattr
fruit:time machine = yes
fruit:time machine max size = 1 T
notably,
[Global]
vfs objects = acl_xattr fruit streams_xattr
fruit:aapl = yes
fruit:nfs_aces = yes
fruit:model = TimeCapsule8,119
fruit:metadata = stream
fruit:veto_appledouble = no
fruit:posix_rename = yes
fruit:zero_file_id = yes
fruit:wipe_intentionally_left_blank_rfork = yes
fruit:delete_empty_adfiles = yes
and with the descriptions of the new optimizations here:
there is mention of some of the desired options being overruled when a Mac isn't the first to use the share or that some of the fruit options that may be required for Time Machine to function properly needing to be added to [Global] may negatively impact the overall samba shares on unraid.
My overarching frustration is that the option exists in the share export dropdown, yes, Timemachine or yes, TimeMachine (hidden), and this lends me to believe that the service that is not working is something that my license paid for.
If we can't get it working, I'd rather see the developer for the docker app https://github.com/mbentley/docker-timemachine be compensated and his option be added to unraid as the "official" way to use unraid for a timemachine server.
tl;dr remove the export option (yes, Time Machine) and add the docker app TIMEMACHINE APPLICATION as the officially supported option
my USD$0.02,
-Dan