# when requested by an SMB client instead of the program listed in
#NETATALK TIME MACHINE BACKUP FAILED PASSWORD#
# This boolean controls whether PAM will be used for password changes Passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully*.
# sending the correct chat script for the passwd program in Debian Sarge). # parameters must be set (thanks to Ian Kahan for # For Unix password sync to work on a Debian GNU/Linux system, the following # password with the SMB password when the encrypted SMB password in the # This boolean parameter controls whether Samba attempts to sync the Unix # 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 Panic action = /usr/share/samba/panic-action %d # Do something sensible when Samba crashes: mail the admin a backtrace # Append if you want important messages to be sent to syslog too. I find the following possibly helpful error in the log: Failed to create '/Volumes/.timemachine/SERVER._smb._tcp.local/DDE06691-7411-41DD-8419-24FEFC21CE29/TimeMachine Set A - SMB/8E394711-7E3F-520B-800C-192D4F680177.sparsebundle', results. Ls -la showing permissions of the share point: drwxrwxrwx 5 root smbusers 4096 Apr 3 12:35 smb 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. I'm not sure which location is more appropriate, my apologies if the duplication causes issues. Note: originally posted on StackExchange.
0 kommentar(er)
