Unable to backup to NAS via SMB using VEEAM
Posted: 26 Nov 2020, 20:30
Hi All.
I have an F5-221 running TOS 4.2.06-2011031752, which I have been using for testing different backup services.
When trying to use VEEAM agent for Windows (4.0.1.2169), I am able to create a backup job and it sees the share on the TNAS however I am getting backup failures.
The error shown by the VEEAM agent is:
When SSH'd into the NAS, I ran the smbstatus command and reviewed the output:
If I'm interpreting the output correctly, the samba server settings on the NAS have opportunistic locking enabled with no way to modify from the GUI - I'd like to be able to change this...
Additionally, when reviewing the SMB configuration files via SSH, I can see it's set to allow both SMBv1 *and* to allow LM/NTLM authentication. Both settings having no way to modify from the GUI. Some of my clients have strict network infrastructures where obsolete and insecure network protocols and the like *must* be disabled prior to introducing a new device.
When can we expect to have these options available for modification via the GUI, or do we have to modify the SMB configuration by hand?
I have an F5-221 running TOS 4.2.06-2011031752, which I have been using for testing different backup services.
When trying to use VEEAM agent for Windows (4.0.1.2169), I am able to create a backup job and it sees the share on the TNAS however I am getting backup failures.
The error shown by the VEEAM agent is:
Code: Select all
Error: An unexpected network error occurred. Failed to write data to the file [\\192.168.15.107\TEST\Job 9020AIO\Job 9020AIO2020-11-26T114139.vbk]. Failed to backup file. File: [C:\WINDOWS\TEMP\digest_5c23e06b-ab09-4e65-9a9e-50f2918ce2af]. ItemSpec: [veeamfs:5:6745a759-2205-4cd2-b172-8ec8f7e60ef8 (4c4c4544-0042-4810-8048-cac04f543032)\digest_5c23e06b-ab09-4e65-9a9e-50f2918ce2af@\\192.168.15.107\TEST\Job 9020AIO\Job 9020AIO2020-11-26T114139.vbkVBK: 'veeamfs:5:6745a759-2205-4cd2-b172-8ec8f7e60ef8 (4c4c4544- Code: Select all
[root@TNAS-5E0E ~]# smbstatus
Samba version 4.9.1
PID Username Group Machine Protocol Version Encryption Signing
----------------------------------------------------------------------------------------------------------------------------------------
14133 admin admin 192.168.15.180 (ipv4:192.168.15.180:55555) SMB3_11 - partial(AES-128-CMAC)
12414 admin admin 192.168.15.109 (ipv4:192.168.15.109:59917) SMB3_11 - partial(AES-128-CMAC)
14133 admin admin 192.168.15.180 (ipv4:192.168.15.180:55555) SMB3_11 - partial(AES-128-CMAC)
Service pid Machine Connected at Encryption Signing
---------------------------------------------------------------------------------------------
TEST 12414 192.168.15.109 Thu Nov 26 08:02:41 PM 2020 CST - -
TEST 14133 192.168.15.180 Thu Nov 26 08:10:38 PM 2020 CST - -
TEST 14133 192.168.15.180 Thu Nov 26 08:10:38 PM 2020 CST - -
Locked files:
Pid Uid DenyMode Access R/W Oplock SharePath Name Time
--------------------------------------------------------------------------------------------------
14133 3 DENY_NONE 0x100080 RDONLY NONE /mnt/md0/TEST . Thu Nov 26 20:10:38 2020
14133 3 DENY_WRITE 0x12019f RDWR LEASE(RWH) /mnt/md0/TEST Job 9020AIO/Job 9020AIO2020-11-26T121019.vbk Thu Nov 26 20:10:39 2020
Additionally, when reviewing the SMB configuration files via SSH, I can see it's set to allow both SMBv1 *and* to allow LM/NTLM authentication. Both settings having no way to modify from the GUI. Some of my clients have strict network infrastructures where obsolete and insecure network protocols and the like *must* be disabled prior to introducing a new device.
When can we expect to have these options available for modification via the GUI, or do we have to modify the SMB configuration by hand?