Time Machine issue on 11.3

Das_Schaf · Feb 3, 2020

Since updating from 11.2 to 11.3 my mac (latest Catalina release) isn't able to backup to the time machine share anymore. The backup dialogue shows the following error: "the network backup disk does not support the required capabilities". I've already tried several things like deleting and recreating the share. The smb4.conf file does not contain a "fruit:time machine = yes" line. As soon as i reboot with the 11.2 version, time machine backups works like a charm. Does anyone have an idea what is going wrong here?

anodos · Feb 3, 2020

Das_Schaf said:
Since updating from 11.2 to 11.3 my mac (latest Catalina release) isn't able to backup to the time machine share any more. The backup dialogue shows the following error: "the network backup disk does not support the required capabilities". I've already tried several things like deleting and recreating the share. The smb4.conf file does not contain a "fruit:time machine = yes" line. As soon as i reboot with the 11.2 version, time machine backups works like a charm. Does anyone have an idea what is going wrong here?

Have you checked the "time machine" checkbox for the share?

Das_Schaf · Feb 3, 2020

Of course. The share already worked with 11.2.

anodos · Feb 3, 2020

Post output of testparm -s

Das_Schaf · Feb 3, 2020

Code:

Load smb config files from /usr/local/etc/smb4.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
        aio max threads = 2
        bind interfaces only = Yes
        disable spoolss = Yes
        dns proxy = No
        enable web service discovery = Yes
        kernel change notify = No
        load printers = No
        logging = file
        max log size = 51200
        nsupdate command = /usr/local/bin/samba-nsupdate -g
        obey pam restrictions = Yes
        restrict anonymous = 2
        server min protocol = SMB2_02
        server role = standalone server
        server string = FreeNAS Server
        unix extensions = No
        username map = /usr/local/etc/smbusername.map
        username map cache time = 60
        idmap config *: range = 90000001-100000000
        fruit:nfs_aces = No
        idmap config * : backend = tdb
        allocation roundup size = 0
        directory name cache size = 0
        dos filemode = Yes
        include = /usr/local/etc/smb4_share.conf


[Multimedia]
        aio write size = 0
        ea support = No
        mangled names = illegal
        path = /mnt/Obelix/Multimedia
        read only = No
        vfs objects = zfs_space zfsacl fruit streams_xattr
        nfs4:acedup = merge
        nfs4:chown = true
        fruit:resource = stream
        fruit:metadata = stream


[Time-Machine]
        aio write size = 0
        ea support = No
        level2 oplocks = No
        mangled names = illegal
        oplocks = No
        path = /mnt/Obelix/Time-Machine
        read only = No
        strict locking = Yes
        vfs objects = shadow_copy_zfs ixnas fruit streams_xattr
        fruit:time machine max size = 500 G
        nfs4:acedup = merge
        nfs4:chown = true
        fruit:volume_uuid = 108d5ca5-f847-4a51-9f4d-1d9136713b0c
        fruit:time machine = yes
        fruit:resource = stream
        fruit:metadata = stream
        streams_xattr:store_stream_type = no
        streams_xattr:prefix = user.
        fruit:locking = netatalk


[config]
        aio write size = 0
        browseable = No
        ea support = No
        hide dot files = No
        level2 oplocks = No
        mangled names = illegal
        oplocks = No
        path = /mnt/Asterix/config
        read only = No
        strict locking = Yes
        vfs objects = zfs_space zfsacl fruit streams_xattr
        nfs4:acedup = merge
        nfs4:chown = true
        fruit:resource = stream
        fruit:metadata = stream


[homes]
        aio write size = 0
        browseable = No
        ea support = No
        hide dot files = No
        mangled names = illegal
        path = /mnt/Obelix/home/%U
        read only = No
        vfs objects = zfs_space zfsacl fruit streams_xattr
        nfs4:acedup = merge
        nfs4:chown = true
        fruit:resource = stream
        fruit:metadata = stream


[iTunes]
        aio write size = 0
        ea support = No
        mangled names = illegal
        path = /mnt/Obelix/Multimedia/iTunes Media
        read only = No
        vfs objects = shadow_copy_zfs zfs_space zfsacl fruit streams_xattr
        nfs4:acedup = merge
        nfs4:chown = true
        fruit:resource = stream
        fruit:metadata = stream

anodos · Feb 3, 2020

Are you sharing the same dataset via SMB and AFP for time machine backups?

anodos · Feb 3, 2020

Also can you post the txt records being generated by the FN server? An easy way to do is this is to run the following commands form MacOS client:
1. dns-sd -B _adisk._tcp. -This will print out the mDNS name of the server with the Time Machine target
2. dns-sd -L <name from 1> _adisk._tcp.. This will print out the txt record for _adisk._tcp.

Das_Schaf · Feb 3, 2020

Code:

Browsing for _adisk._tcp.
DATE: ---Tue 04 Feb 2020---
 6:16:09.716  ...STARTING...
Timestamp     A/R    Flags  if Domain               Service Type         Instance Name
 6:16:09.717  Add        2   4 local.               _adisk._tcp.         freenas
Lookup freenas._adisk._tcp..local

DATE: ---Tue 04 Feb 2020---

 6:17:13.780  ...STARTING...

 6:17:13.982  freenas._adisk._tcp.local. can be reached at freenas.local.:9 (interface 4)

 sys=waMa=0,adVF=0x100 dk0=adVN=Time-Machine,adVF=0x82,adVU=108d5ca5-f847-4a51-9f4d-1d9136713b0c dk1=adVN=Time\ Machine,adVF=0x81,adVU=a3e657ea-88dd-41df-aedf-8225b6bf55d4

Sharing is done with SMB. AFP is disabled.

anodos · Feb 4, 2020

That's an interesting advertisement. Can you please PM me a debug?

SixthGear · Feb 10, 2020

I'm in the exact same situation as Das_Schaf. Any luck on resolving the problem? Txt record:

Code:

Lookup freenas._adisk._tcp..local
DATE: ---Mon 10 Feb 2020---
 7:07:34.415  ...STARTING...
 7:07:34.619  freenas._adisk._tcp.local. can be reached at freenas.local.:9 (interface 4)
 sys=waMa=0,adVF=0x100 dk0=adVN=TimeMachine,adVF=0x82,adVU=b6f7b2eb-8ed8-46b1-b2d3-902e74856d25

thedude123 · Feb 13, 2020

Code:

"the network backup disk does not support the required capabilities"

I have the same problem after the update to 11.3. A new installation doesn't help either.

anodos · Feb 14, 2020

thedude123 said:
Code:
"the network backup disk does not support the required capabilities"

I have the same problem after the update to 11.3. A new installation doesn't help either.

Can you post output of "testparm -s"?

thedude123 · Feb 14, 2020

Code:

nas# testparm -s
Load smb config files from /usr/local/etc/smb4.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
    aio max threads = 2
    bind interfaces only = Yes
    disable spoolss = Yes
    dns proxy = No
    enable web service discovery = Yes
    kernel change notify = No
    load printers = No
    logging = file
    map to guest = Bad User
    max log size = 51200
    nsupdate command = /usr/local/bin/samba-nsupdate -g
    server min protocol = SMB2
    server role = standalone server
    server string = FreeNAS Server
    unix extensions = No
    username map = /usr/local/etc/smbusername.map
    username map cache time = 60
    idmap config *: range = 90000001-100000000
    fruit:nfs_aces = No
    idmap config * : backend = tdb
    allocation roundup size = 0
    directory name cache size = 0
    dos filemode = Yes
    include = /usr/local/etc/smb4_share.conf


[nas_backup]
    ea support = No
    mangled names = illegal
    path = /mnt/dpool/backup
    read only = No
    vfs objects = shadow_copy2 catia zfs_space ixnas zfsacl fruit streams_xattr
    nfs4:acedup = merge
    nfs4:chown = true
    fruit:resource = stream
    fruit:metadata = stream
...
[nas_tm]
    ea support = No
    mangled names = illegal
    path = /mnt/usb2tb/tm
    read only = No
    vfs objects = shadow_copy2 catia zfs_space ixnas zfsacl fruit streams_xattr
    nfs4:acedup = merge
    nfs4:chown = true
    fruit:volume_uuid = 6d69de9f-cff3-4feb-aedb-09d8319d3bce
    fruit:time machine = yes
    fruit:resource = stream
    fruit:metadata = stream

Code:

nas# dns-sd -B _adisk._tcp.
Browsing for _adisk._tcp.
DATE: ---Fri 14 Feb 2020---
15:20:12.931  ...STARTING...
Timestamp     A/R    Flags  if Domain               Service Type         Instance Name
15:20:12.931  Add        2   1 local.               _adisk._tcp.         nas

nas# dns-sd -L nas _adisk._tcp.
Lookup nas._adisk._tcp..local
DATE: ---Fri 14 Feb 2020---
15:20:37.146  ...STARTING...
15:20:37.355  nas._adisk._tcp.local. can be reached at nas.local.:9 (interface 1)
 sys=waMa=0,adVF=0x100 dk0=adVN=nas_tm,adVF=0x82,adVU=6d69de9f-cff3-4feb-aedb-09d8319d3bce

would a tcpdump (port 445) be helpful?
THX

thedude123 · Feb 14, 2020

vfs_fruit (8)
...
The module enables alternate data streams (ADS) support for a share, intercepts the OS X special streams "AFP_AfpInfo" and "AFP_Resource" and handles them in a special way. All other named streams are deferred to vfs_streams_xattr which must be loaded together with vfs_fruit.

???

SixthGear · Feb 14, 2020

Looks like nearly identical setup and results for me with testparm:

Code:

[TimeMachine]
    aio write size = 0
    ea support = No
    level2 oplocks = No
    mangled names = illegal
    oplocks = No
    path = /mnt/Storage/TimeMachine
    read only = No
    strict locking = Yes
    vfs objects = shadow_copy_zfs ixnas fruit streams_xattr
    nfs4:acedup = merge
    nfs4:chown = true
    fruit:volume_uuid = b6f7b2eb-8ed8-46b1-b2d3-902e74856d25
    fruit:time machine = yes
    fruit:resource = stream
    fruit:metadata = stream

anodos · Feb 14, 2020

SixthGear said:

It looks like your time machine share may also be an NFS export. In 11.3 we re-configure the SMB shares in this case for safer behavior. If it's being exported by NFS, remove the NFS export and restart the SMB service through the GUI (to force an SMB re-configuration).

thedude123 · Feb 14, 2020

I have found a solution for me:

macOS# sudo rm -f /etc/nsmb.conf
reboot

in my case (/etc/nsmb.conf):

Code:

[default]
signing_required=no
streams=yes
file_ids_off=yes
protocol_vers_map=2

before deleting (smbstatus -b):

Code:

PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing
----------------------------------------------------------------------------------------------------------------------------------------
13512   marius       XXX       192.168.1.99 (ipv4:192.168.1.99:50393)    SMB2_10           -                    -

after:

Code:

PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing
----------------------------------------------------------------------------------------------------------------------------------------
13626   marius       XXX       192.168.1.99 (ipv4:192.168.1.99:50403)    SMB3_02           -                    partial(AES-128-CMAC)

Time Machine works like a charm. :)

SixthGear · Feb 14, 2020

anodos said:
It looks like your time machine share may also be an NFS export. In 11.3 we re-configure the SMB shares in this case for safer behavior. If it's being exported by NFS, remove the NFS export and restart the SMB service through the GUI (to force an SMB re-configuration).

Sure enough, that was it. Thank your for the help!

Supergrobi · Feb 15, 2020

Hi, I am also having problems with my Time Machine backups and Catalina / FreeNAS 11.3. I have created a SMB share with Time Machine enabled on my FreeNAS 11.2 system and I was using that for a year without any problems. Updating my Macbook to Catalina also did not cause any problems. Last week I updated my FreeNAS server to 11.3 and my TM Backups still were working without any problems. Yesterday I decided to do a clean install of macOS Catalina on my Macbook. After that the problems started: I can still select the FreeNAS SMB share in the TM settings but when the backup starts there is an error which tells me that the "backup volume does not support the necessary functionality" (translated from german...). Any ideas what could cause this? I did not change any settings on the FreeNAS! The last backup just before the clean install of the macbook finished successfully...

ChristianGrebe · Mar 16, 2020

Hi,

this is my current situation:

I am running FreeNAS 11.2-U7 and use it as a Time Machine backup and file server using SMB only.
My clients are running macOS 10.15.3.
I used AFP before (since FreeNAS 9) and datasets were setup as Mac share types initially.
I switched from AFP to SMB with this release (11.2-U7).
I set "fruit:time machine = yes" on all SMB shares.
Time Machine backups and file serving do work currently.
I had to mount the Time Machine share manually once on the clients to make Time Machine backups work.

I am pondering over the update from 11.2 to 11.3.

Is it save yet and is there a how-to (if the update is not trivial)?

Thanks,

Christian

Important Announcement for the TrueNAS Community.

Time Machine issue on 11.3

Cadet

Sambassador

Cadet

Sambassador

Cadet

Sambassador

Sambassador

Cadet

Sambassador

Cadet

Cadet

Sambassador

Cadet

Cadet

Cadet

Sambassador

Cadet

Cadet

Dabbler

Cadet

Similar threads