Big Sur + SMB based Time Machine

Question

Created Nov ’20

Replies 20

Boosts 0

Views 12k

Participants 15

Has anyone tested SMB based time machine backups in any of the various revisions of Big Sur?

Direct change from Catalina to BS result in permissions issues generated by time machine. If you force the folders to inherit permissions, time machine will complain about missing features.

Either way, time machine is completely non-functional. I've reported feedback and seen that others have the same issue, but no one I know has worked around it yet.

Samba 4.11.6 from ubuntu 20.04

standard options in smb.conf like fruit:aapl = yes and fruit:timemachine = yes, as well as the proper vfs etc. It is configured properly, worked great in Catalina and all previous revisions.

Boost

Answer 1

wojciech_czyz OP

Jan ’21

Sophos was a problem. They plan to solve it in ... March 2021.

1

Answer 2

baspr OP

Feb ’21

As @philko I got something similar on Big Sur, but with another error:

Code Block 2021-02-02 11:54:56.253924+0300 0x1162743  Info        0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Starting manual backup
2021-02-02 11:54:56.666469+0300 0x1162743  Info        0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Attempting to mount 'smb://baspr@store/TimeMachine'
2021-02-02 11:55:01.038059+0300 0x1162743  Info        0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Mounted 'smb://baspr@store/TimeMachine' at '/Volumes/.timemachine/store/10BA71B7-F138-4A36-8A39-6947FA5DF053/TimeMachine'
2021-02-02 11:55:01.038153+0300 0x1162743  Info        0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Initial network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 60, QoS: 0x0, attributes: 0x1C}
2021-02-02 11:55:01.246189+0300 0x1162743  Info        0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Configured network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C}
2021-02-02 11:55:01.668781+0300 0x1162743  Info        0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Mountpoint '/Volumes/.timemachine/store/10BA71B7-F138-4A36-8A39-6947FA5DF053/TimeMachine' is still valid
2021-02-02 11:55:01.672073+0300 0x1162743  Info        0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Mountpoint '/Volumes/.timemachine/store/10BA71B7-F138-4A36-8A39-6947FA5DF053/TimeMachine' is still valid
2021-02-02 11:55:01.680093+0300 0x1162743  Info        0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Creating an encrypted sparsebundle using Case-sensitive APFS filesystem
2021-02-02 11:55:08.885736+0300 0x1162743  Error       0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Failed to create '/Volumes/.timemachine/store/10BA71B7-F138-4A36-8A39-6947FA5DF053/TimeMachine/1C3A8B14-9B42-51E5-9069-FD3C6B7DE771.sparsebundle', results: {
}, error: -25300 No such process
2021-02-02 11:55:10.501443+0300 0x1162743  Error       0x1235205            473    0    backupd: (TimeMachine) [com.apple.TimeMachine:General] Backup failed (20: BACKUP_FAILED_DISK_IMAGE_NOT_CREATED)

0

Answer 3

ChrisB20 OP

Feb ’21

So glad I found this page. Uninstalling Sophos and rebooting the Mac worked for me.

0

Answer 4

calebadavis OP

Mar ’21

Upgrading to Big Sur caused the same problem for me. I had a samba share on a Linux server working with Catalina (Fedora 33 sharing an ext4 filesystem).

To get it going agin, in /etc/smb.conf, explicitly disabling the 'fruit:nfs_aces' global option got my backups going again:
fruit:nfs_aces = no

0

Answer 5

smittycodes OP

Dec ’23

On my ubuntu, I ended up needing to install the VFS modules:

sudo apt install samba-vfs-modules

0