> # running "samba-tool domain provision" to wipe databases and create a > # Running as "active directory domain controller" will require first > # Most people will want "standalone server" or "member server". > # domain controller", "classic backup domain controller", "active > # values are "standalone server", "member server", "classic primary Defines in which mode Samba will operate. > #fruit:wipe_intentionally_left_blank_rfork = yes
> vfs objects = catia fruit streams_xattr > panic action = /usr/share/samba/panic-action %d > # Do something sensible when Samba crashes: mail the admin a backtrace > # Append syslog at 1 if you want important messages to be sent to syslog too. > I find the following possibly helpful error in the log:
> drwxrwxrwx 5 MY_USER smbusers 4096 Apr 3 12:35 smb > `ls -la` showing permissions of the share point: I thought maybe a permissions issue, but for debugging purposes I have /usr/local/smb set to 0777 and still get the error. > If I first connect to the share with AFP and do the initial backup, I can then connect with SMB and add subsequent incremental backups without error. The backup disk image could not be created." > If I use the exact same directory (/usr/local/smb), so same permissions etc, and create a samba share, when Time Machine attempts to create a new backup it give the error: "Time Machine couldn’t complete the backup to SERVER.local. On a fresh AFP share I can start a new Time Machine backup in System Preferences and it will create a new. Since Mavericks macOS has preferred SMB, and given SMB is marginally faster I decided to switch to using SMB for the Time Machine shares. > I'm running macOS Catalina and my Time Machine backs up to a Debian 10 server with NetAtalk and Avahi. > TL DR: Time Machine cannot create a *new* backup on my shared drive, but can add to an *existing* backup.
On Mon, Apr 6, 2020, at 6:40 PM, Michael Robinson wrote: This is listed on the wiki for OS X support, but I somehow missed it. changing fruit:metadata = netatalk to fruit:metadata = stream fixed my issue. It turns out the issue was a single line in smb.conf.
#Time machine cannot connect to netatalk download#
Next message (by thread): Samba 4.12.1 Available for Download.Previous message (by thread): issues with Time Machine - did macOS change how they handle things?.issues with Time Machine - did macOS change how they handle things? Michael Robinson samba at Issues with Time Machine - did macOS change how they handle things?
0 kommentar(er)
