TrueNAS 25.04 Time Machine not working

TrueNAS General
, ,
1

Hey,

after install the Update from 24.10.2.1 to 25.04.0 Time Machine not working.
App not find the Time Machine Share from TrueNAS.
When i switch back to 24.10.2.1 Time Machine Share is found and Backup running.

Has anyone the same problem ?

BG
Maik

2

Do you perhaps have SMB shares flagged for mixed mode SMB/NFS access? This requires some global changes that are incompatible with time machine backups.

3

No issues with TM SMB shares here

4

No, is only a Basic Time Machine Share

image
image958Ă—1328 87.8 KB

The Error is:

image
image598Ă—464 68.5 KB

5

I think the issue that’s been reported is that Time Machine shares will stop working if any other share on the server is configured for mixed SMB/NFS use. This was a known issue at least during RC1, I think.

3 Likes
6

Correct. I’m adding a note about this to the Upgrade Notes section of the 25.04 release notes for better visibility.

2 Likes
7

This command should show you if you have any mixed shares:

1 Like
8

Thanks for your help.
After i deconfigure Multi Protocol NFS from a other Share, the backup works.

Thanks and
BG
Maik

3 Likes
9

I was just about to ask if there was a command that would show the share types. Thanks!

What would the output be for a share using the multi-protocol setting?

10

On my Site:

{
“name”: “share”,
“purpose”: “MULTI_PROTOCOL_NFS”
},

11

Thanks!

12

I don’t think this is a valued solution, it might be a workaround. This workaround is not valid for me, as I have and need a mixed mode SMB/NFS share, not the time-machine share.
So I can’t run 25.04.0 in its current state. I had to downgrade to the lates 24.10 version.

2 Likes
13

Chiming in as I’m getting caught by this as well. My primary use of shares is mixed SMB/NFS4 - I have the Time Machine share as I’ve got space and it makes sense to have it on the same machine. It seems that the path going forward is going to require two different machines?

14

Agreed. Mixed-mode shares are useful, and it’s not clear to me why they kill Time Machine shares when they didn’t before. That seems like a bug/known issue.

Is there a Jira issue tracking this?

15

There is a NAS ticket linked from the Upgrade Notes section of the Release Notes that has some explanation of what the conflict was.

1 Like
16

Thanks for pointing that out. :slight_smile:

That’s this ticket: Jira

Is this something that might be fixable at some point in the future? From reading the Upgrade Notes and the ticket, it sounded like the answer is probably no; that seems like a core conflict between how SMB and NFS work.

17

It’s more of a general question of how you want to deal with client-side caching. In general, if you want to access SMB shares outside the SMB protocol (including local FS access or via apps, containers, whatever) then you need to put thought into how you’re going to handle SMB oplocks and such. This isn’t a new consideration, and is a matter of how risk tolerant you are.

18

This solution seems particularly bad to me, as it necessitates the purchase of additional hardware and admin-ing an additional system just to be able to use Time Machine. Is there no hope of samba upstream being able to use kernel oplocks / disable smb2+ leases on specific shares, while still allowing leases on others (eg, Time Machine shares)?

19

Negotiation of lease support happens during SMB2 negotiate, so no, you don’t do it on a per-share basis.

20

I realize I’m only one small voice here, but this is a blocking issue that will prevent me from upgrading going forward for the foreseeable future.