I have two TrueNAS systems both running Scale v25.10.1. I have a Time Machine dataset on each configured exactly the same on each system. The respective SMB shares are configured exactly the same on each as well. The strange thing is that the Auto Snapshot feature is not working as expected on one of the systems (System 2, below.)
System 1: One user backing up two Macs, one running Sequoia and the other running Tahoe. For each, a TM backup is done daily. After each backup, TrueNAS automatically creates a snapshot.
System 2: One user backing up one Mac running Tahoe. For this Mac, a TM backup is also done daily; however, no “auto” snapshots are created unless I first disable and then re-enable the TM share. That seems to be the only way to trigger an “auto” snapshot.
If anyone has an explanation and / or a solution, I’d be very grateful. Also, please add a comment if you’re experiencing this same behavior. Thanks.
I’ve seen a variety of behaviors with MacOS tahoe. Our auto-snapshot relies on a certain workflow from the SMB client.
connect to share using credentials stored for the time machine backup
Do I/O then update the plist file containing snapshots
disconnect from share when backup completes
I’ve seen some cases where the MacOS Tahoe SMB client never does (3). The behavior seems erratic and might be a new bug or behavior in tahoe. I haven’t been able to consistently reproduce, but it lies outside of TrueNAS.
@awalkerix, well a TM backup has just completed on the Tahoe Mac backing up to TrueNAS system 2. On the Mac, issuing “sudo smbutil statshares -a” lists the time machine smb share as still connected after completion of the backup. I then disable/enable the share on TrueNAS and subsequently check the connection status on the Mac. The time machine smb share is no longer listed in the output of “sudo smbutil statshares -a”. It’s certainly a Tahoe issue. I’ll have to reach out to an Apple engineer to understand if this is by design or due to an oversight.
