macOS Catalina SMB Time Machine not work with FreeNAS-11.3-U3.2

O

ObiTobi

Patron
Joined
Jul 12, 2013
Messages
316
Hi,

I would like disable AFP Protocol on my NAS box. But the Timae Machine will not work with SMB for me. Today I updated my FreeNAS from 11.3-U2.1 to U3.2 because SMB BUG, but no like.

Fro my smb4_shares.conf
Code:
[Time Machine]
        comment = Time Machine
        read only = no
        fruit:locking = netatalk
        strict locking = auto
        streams_xattr:prefix = user.
        streams_xattr:store_stream_type = no
        vfs objects = fruit streams_xattr shadow_copy_zfs zfs_space ixnas zfsacl
        fruit:metadata = stream
        fruit:resource = stream
        fruit:time machine = yes
        fruit:volume_uuid = b7d40336-7169-4975-bd27-4e3e3b8f9216
        nfs4:chown = true
        nfs4:acedup = merge
        aio write size = 0
        mangled names = illegal
        ea support = false
        kernel oplocks =   no
        oplocks =   no
        level2 oplocks =   no
        blocking locks =   no
        spotlight =  yes
        path = /mnt/zpool02/backup/OSX


Any Idea what I can do?
If I manually change /Library/Preferences/com.apple.TimeMachine.plist from afp to smb, Time Machine mean my share don's support all needed features :(
 
Samuel Tai

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
O

ObiTobi

Patron
Joined
Jul 12, 2013
Messages
316
Thank you, but it chances nothing here :(
I changes also some things for this share but no luck again.

Code:
[Time Machine]
        comment = Time Machine
        read only = no
        fruit:locking = netatalk
        strict locking = auto
        streams_xattr:prefix = user.
        streams_xattr:store_stream_type = no
        vfs objects = catia fruit streams_xattr
        fruit:metadata = stream
        fruit:resource = stream
        fruit:time machine = yes
        fruit:volume_uuid = b7d40336-7169-4975-bd27-4e3e3b8f9216
        nfs4:chown = true
        nfs4:acedup = merge
        aio write size = 0
        mangled names = illegal
        ea support =  true
        spotlight =  yes
        path = /mnt/zpool02/backup/OSX
 
Last edited:
Samuel Tai

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Did you restart SMB after your changes?
 
O

ObiTobi

Patron
Joined
Jul 12, 2013
Messages
316
@Samuel - please :) Of course.
I ca boot from my Recover Partition and restore all from my SMB Time Machine share, I can connect to this share with finder (go to server) smb://userName@ServerName/Share all this is not a problem. But I I will set my share as TM Volume, TM mean not all Features are supported
 
Samuel Tai

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Hmm. Similar problems over at UnRAID. This post may help:
Code:
fruit:time machine max size = 2T
fruit:encoding = native
fruit:locking = netatalk
fruit:metadata = netatalk
fruit:resource = file
fruit:time machine = yes
fruit:advertise_fullsync = true
 
Samuel Tai

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,553
ObiTobi said:
Hi,

I would like disable AFP Protocol on my NAS box. But the Timae Machine will not work with SMB for me. Today I updated my FreeNAS from 11.3-U2.1 to U3.2 because SMB BUG, but no like.

Fro my smb4_shares.conf
Code:
[Time Machine]
        comment = Time Machine
        read only = no
        fruit:locking = netatalk
        strict locking = auto
        streams_xattr:prefix = user.
        streams_xattr:store_stream_type = no
        vfs objects = fruit streams_xattr shadow_copy_zfs zfs_space ixnas zfsacl
        fruit:metadata = stream
        fruit:resource = stream
        fruit:time machine = yes
        fruit:volume_uuid = b7d40336-7169-4975-bd27-4e3e3b8f9216
        nfs4:chown = true
        nfs4:acedup = merge
        aio write size = 0
        mangled names = illegal
        ea support = false
        kernel oplocks =   no
        oplocks =   no
        level2 oplocks =   no
        blocking locks =   no
        spotlight =  yes
        path = /mnt/zpool02/backup/OSX


Any Idea what I can do?
If I manually change /Library/Preferences/com.apple.TimeMachine.plist from afp to smb, Time Machine mean my share don's support all needed features :(
Click to expand...
Looks like SMB share is also an NFS export and so we've automatically disabled some features in SMB that Time Machine requires in order to make the server less likely to encounter integrity issues on the mixed-protocol share. Try removing the NFS export and restarting the SMB service.
 
O

ObiTobi

Patron
Joined
Jul 12, 2013
Messages
316
anodos said:
Looks like SMB share is also an NFS export
Click to expand...

Nope.

/mnt/zpool02/backup <- dataset

/mnt/zpool02/backup/Linux <- NFS export
/mnt/zpool02/backup/OSX <- AFP/ SMB Share
/mnt/zpool02/backup/Windows <- SMB Share

I don't know why FreeNAS writes to all my shares entries like this
Code:
nfs4:chown = true
nfs4:acedup = merge

Maybe because I have NFSv4 active or because in last 6 Years I have only updated my system and newer changed something.
 
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,553
Set the following as auxiliary parameters for the share:

Code:
        oplocks =   yes
        level2 oplocks =   yes

Don't bother with trying to turn on spotlight support. We don't compile with it in 11.3.
 
O

ObiTobi

Patron
Joined
Jul 12, 2013
Messages
316
It's not helping.
It seems that there are no clear guidelines how the share has to look like and so it works for some people and not for others.
 
O

ObiTobi

Patron
Joined
Jul 12, 2013
Messages
316
Hi,
OK I give up. I've tried so many things. The last one was with these settings but no luck. Whether it is because of my settings or FreeNAS I don't know. It is not nice.
At the moment I have gone back to AFP protocol. Next week I will set up a new machine, I will see how it looks like with Windows Server 2019.

Code:
[Time Machine]
        comment = Time Machine
        read only = no
        fruit:locking =  none
        strict locking = auto
        streams_xattr:prefix = user.
        streams_xattr:store_stream_type = no
        vfs objects = catia fruit streams_xattr zfs_space ixnas zfsacl
        fruit:metadata = stream
        fruit:resource =  file
        fruit:time machine = yes
        fruit:volume_uuid = b7d40336-7169-4975-bd27-4e3e3b8f9216
        nfs4:chown = true
        nfs4:acedup = merge
        aio write size = 0
        mangled names = illegal
        ea support =  yes
        fruit:model =  MacSamba
        fruit:aapl =  yes
        fruit:advertise_fullsync =  true
        oplocks =   no
        kernel oplocks =   no
        level2 oplocks =   no
        blocking locks =   no
        path = /mnt/zpool02/backup/OSX
 
EsTaF

EsTaF

Contributor
Joined
Sep 20, 2013
Messages
163
ObiTobi said:
Hi,
OK I give up. I've tried so many things. The last one was with these settings but no luck. Whether it is because of my settings or FreeNAS I don't know. It is not nice.
At the moment I have gone back to AFP protocol. Next week I will set up a new machine, I will see how it looks like with Windows Server 2019.

Code:
[Time Machine]
        comment = Time Machine
        read only = no
        fruit:locking =  none
        strict locking = auto
        streams_xattr:prefix = user.
        streams_xattr:store_stream_type = no
        vfs objects = catia fruit streams_xattr zfs_space ixnas zfsacl
        fruit:metadata = stream
        fruit:resource =  file
        fruit:time machine = yes
        fruit:volume_uuid = b7d40336-7169-4975-bd27-4e3e3b8f9216
        nfs4:chown = true
        nfs4:acedup = merge
        aio write size = 0
        mangled names = illegal
        ea support =  yes
        fruit:model =  MacSamba
        fruit:aapl =  yes
        fruit:advertise_fullsync =  true
        oplocks =   no
        kernel oplocks =   no
        level2 oplocks =   no
        blocking locks =   no
        path = /mnt/zpool02/backup/OSX
Click to expand...
"June 18, 2020"
There're no posts/answers after it.
That says it all. And about FreeNA$ and about window$ server with afp one))
Opensource/Linux is the best way.
 
EsTaF

EsTaF

Contributor
Joined
Sep 20, 2013
Messages
163
About 4 years ago I'd use afp for time machine. But have troubles. Each snapshot was had creating very long time as from scratch.
 
C

c77dk

Patron
Joined
Nov 27, 2019
Messages
468
If possible consider upgrading to 12.0-U2.1 - my TMs are just working (now from Big Sur, but also when the systems were Catalina). In 11.3 it was a little hit or miss for my machines, but in 12.x I've had no issues (except a general SMB issue which @anodos quickly patched)
 
You must log in or register to reply here.

Important Announcement for the TrueNAS Community.

The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums.

Related topics on forums.truenas.com for thread: "macOS Catalina SMB Time Machine not work with FreeNAS-11.3-U3.2"

Similar threads

M
11.3 U2.1. Time Machine share crashes smbd
Replies
5
Views
2K
Mark Levitt
M
keson
SMB performance drops over time on 11.2.U2
Replies
15
Views
7K
keson
keson
J
SOLVED SMB share persisence with Mac client
Replies
7
Views
4K
Jedge
J
korrupto77
Move files between Datasets
Replies
0
Views
2K
korrupto77
korrupto77
M
Directory case sensitivity issue with macOS client
Replies
18
Views
5K
anodos
anodos
Top