Time Machine Backups Stopped Working

[MediaManRIT]

I'm not sure when this happened, but Time Machine backups have stopped working either after an macOS update or a TrueNAS update. They had worked for >1 year without issues. I discovered this when I tried setting up a new Mac, and couldn't make Time Machine work.

Time Machine sees the share, but I get an error "The backup disk image could not be created".

I created a basic dataset...

And when making the SMB share I used the "Multi-user time machine" preset, resulting in:

For permissions, I've tried to rule out any session issues, and just used my user, giving my user full control.

No errors in log.smbd, and the auth_audit.log shows a successful logon. Moreover, Time Machine is making the child dataset for the user, so I know it's connecting and able to do something...

I've been banging my head against the wall with this for a while now. Anyone have any insights here?

Thanks!

 

[Sayares13]

Brand new to TrueNAS and I'm running into an identical issue. Have you had any luck troubleshooting this recently?

 

[rsander5]

Brand new to TrueNAS and I'm running into an identical issue. Have you had any luck troubleshooting this recently?

Ditto... stopped working after updating to latest MAC OS

 

[Constantin]

It seems to have stopped working after I applied the 13.4.1 update. Worked flawlessly before.

 

[paulinventome]

Can confirm, this is not working at 13.4.1. Need to see if I can find an older Mac and see if it still works...

 

[rzara]

Same observation with a 2019 intel iMac with 13.4.1(c). There seems to be a problem creating new files. Purging a backup works OK.
I do see errors in log.smb:
[2023/07/22 21:17:18.385135, 1] ../../source3/rpc_server/srv_pipe_hnd.c:104(np_open)
np_open: 'MsFteWds' is not a registered pipe!
[2023/07/22 21:17:19.370173, 0] ../../source3/modules/vfs_ixnas.c:2165(ixnas_fsetxattr)
ixnas_fsetxattr: BAADA68D-9E38-50C3-A823-AA65F3EB9AB1.sparsebundle: failed to reopen O_PATH descriptor: Is a directory
[2023/07/22 21:17:19.370260, 0] ../../source3/modules/vfs_fruit.c:2717(fruit_pwrite_meta_stream)
fruit_pwrite_meta_stream: On-demand create [BAADA68D-9E38-50C3-A823-AA65F3EB9AB1.sparsebundle:AFP_AfpInfo] in write failed: Is a directory
[2023/07/22 21:17:19.370355, 1] ../../source3/smbd/smb2_setinfo.c:430(smbd_smb2_setinfo_send)
smbd_smb2_setinfo_send: vfs_stat() of BAADA68D-9E38-50C3-A823-AA65F3EB9AB1.sparsebundle:AFP_AfpInfo failed (No such file or directory)
[2023/07/22 21:56:40.052433, 1] ../../source3/rpc_server/srv_pipe_hnd.c:104(np_open)
np_open: 'MsFteWds' is not a registered pipe!

Another arm mac also fully up to date has no problem backing up to the same system (different share and dataset)
And a 2017 intel iMac also fully up to date has no problem backing up to the same system (different share and dataset)

When Time Machine tries to create the disk image, I do see locks being taken on files in the target dataset via smbstatus, but only briefly.

 

[rzara]

Updating to TrueNAS-13.0-U5.2 solves this problem (via fixing NAS-122487 net/samba - fix setting ADS on dirs)