Is it just me or did Time Machine backups stop working with TrueNAS-Fangtooth-RC? Things are working fine before the update but now I get The selected network backup disk does not support the required capabilities.
What? I even created a new dataset and share - get the same error.
If you have configured some SMB shares with the mutliprotocol NFS preset, then time machine shares may be affected because enabling kernel oplock breaks requires disabling SMB2/3 lease support (which is required by Time Machine).
Yes … I had one unrelated share configured as multi protocol. Reconfigured and Time Machine is working again. Thank You.
@awalkerix Does that mean that if you need to use time machine you can’t have any shares using multiprotocol preset (i.e. NFS + SMB)? Or is this just specific for the TM share?
In my setup the TM share is just SMB but I have other shares that are multiprotocol.
2 Likes
I have similar questions.
For example I use a multi protocol share for isos… and I have a multi user Time Machine…
I guess I could switch to SMB for the isos.
The above language, with my added emphasis, suggests that having any multi-protocol share in the system is incompatible with Time Machine. Hopefully, @awalkerix can come back and provide an authoritative answer.
Is there any update to this? I just upgraded to Fangtooth and my Time Machine share no longer works for backups. I don’t want to disable NFS on my other non-Time Machine shares as most of my other machines are using them with NFS.
No update: You cannot have TimeMachine if there is any multi-protocol share.
This would seem to be a pretty large break from 24.10 and previous versions, back to core.
Some clarity would be great - is the solution going forward really going to mandate having two different Truenas machines - one for NFS/SMB shares, and an entirely separate one for Time Machine backups?
1 Like
I am not sure I follow, but admittedly that may be because I didn’t follow this issue intently from the start.
Someone please correct me if I am wrong, but my understanding is as follows.
In 25.04 you:
- can have NFS shares
- can have SMB shares
- can have Time Machine shares
- can have all three at the same time on a single server, albeit different datasets
- cannot have shares using the multiprotocol* share preset.
*The intent of this type of share is to share the same data over NFS and SMB at the same time, necessitating features that are incompatible with Time Machine, as stated above.
If you’re using the shares as backup targets, are NFS and SMB protocols both required to be enabled on the same datasets?
1 Like
This is my understanding of the issue as well, but @awalkerix can confirm
1 Like
Right. This is also an issue in earlier versions of TrueNAS and it specifically relates to whether we allow client-side caching on SMB clients.
There was a basically a situation where some SMB clients could be performing client-side caching on paths that were simultaneously exported via NFS. The steps required to prevent this require globally turning off a server feature that time machine depends on.
2 Likes
I don’t have any multi-protocol SMB shares, in fact I have NFS and iSCSI turned off. But after upgrading to Fangtooth 25.04.0, I can’t back up to a time machine SMB share from a MacBook running Sequoia 15.4. It was working on TrueNAS 24. I’ve deleted the share and the dataset and started everything fresh, but still no luck.