Job fails with Bareos 18.2 filedaemon on Windows server 2019

[Jurgen Goedbloed]

Hi all,

I have installed the Bareos 18.2.5-123.1 filedaemon (64-bit) on Windows server 2019.

Everything works fine, but after a few days the backup job fails.

This is what I get in the job report:

25-Mar 11:35 bareos-dir JobId 14030: Start Backup JobId 14030, Job=backup-prd-tpn-stepstone-win.2019-03-25_11.35.45_00
25-Mar 11:35 bareos-dir JobId 14030: Connected Storage daemon at 172.20.36.21:9103, encryption: PSK-AES256-CBC-SHA
25-Mar 11:35 bareos-dir JobId 14030: Using Device "store1" to write.
25-Mar 11:35 bareos-dir JobId 14030: Using Client Initiated Connection (prd-tpn-stepstone-win).
25-Mar 11:35 bareos-dir JobId 14030: Handshake: Immediate TLS
25-Mar 11:35 bareos-dir JobId 14030: Sending Accurate information.
25-Mar 11:35 store1 JobId 14030: Volume "daily0002" previously written, moving to end of data.
25-Mar 11:35 store1 JobId 14030: Ready to append to end of Volume "daily0002" size=88238242893
25-Mar 11:35 store1 JobId 14030: Spooling data ...
25-Mar 11:35 prd-tpn-stepstone-win JobId 14030: Created 19 wildcard excludes from FilesNotToBackup Registry key
25-Mar 11:35 prd-tpn-stepstone-win JobId 14030: Connected Storage daemon at 172.20.36.21:9103, encryption: PSK-AES256-CBC-SHA
25-Mar 11:35 prd-tpn-stepstone-win JobId 14030: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C"
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Error: Cannot open C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/UsrClass.dat: ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Cannot open "C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/UsrClass.dat": ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Error: Cannot open C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/UsrClass.dat.LOG1: ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Cannot open "C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/UsrClass.dat.LOG1": ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Cannot open "C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/UsrClass.dat.LOG2": ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Error: Cannot open C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/WebCache/V01.log: ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Cannot open "C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/WebCache/V01.log": ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Error: Cannot open C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/WebCache/WebCacheV01.dat: ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Cannot open "C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/WebCache/WebCacheV01.dat": ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Error: Cannot open C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/WebCache/WebCacheV01.jfm: ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:41 prd-tpn-stepstone-win JobId 14030: Cannot open "C:/users/jurgengoedbloed/AppData/Local/Microsoft/Windows/WebCache/WebCacheV01.jfm": ERR=The process cannot access the file because it is being used by another process.
.
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: Error: lib/bsock_tcp.cc:417 Wrote 6 bytes to Storage daemon:172.20.36.21:9103, but only 0 accepted.
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: Fatal error: filed/backup.cc:1354 Network send error to SD. ERR=Input/output error
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "TermServLicensing", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 prd-tpn-stepstone-win JobId 14030: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE)
25-Mar 11:42 bareos-dir JobId 14030: Fatal error: Director's comm line to SD dropped.
25-Mar 11:42 bareos-dir JobId 14030: Error: Bareos bareos-dir 18.2.5 (30Jan19):
Build OS: Linux-4.4.92-6.18-default redhat CentOS Linux release 7.6.1810 (Core)
JobId: 14030
Job: backup-prd-tpn-stepstone-win.2019-03-25_11.35.45_00
Backup Level: Incremental, since=2019-03-22 19:00:23
Client: "prd-tpn-stepstone-win" 18.2.5 (30Jan19) Microsoft Windows Server 2012 Standard Edition (build 9200), 64-bit,Cross-compile,Win64
FileSet: "prd-tpn-stepstone-win" 2019-01-10 09:11:29
Pool: "daily" (From command line)
Catalog: "Onetrail" (From Client resource)
Storage: "store1" (From Pool resource)
Scheduled time: 25-Mar-2019 11:35:44
Start time: 25-Mar-2019 11:35:47
End time: 25-Mar-2019 11:42:29
Elapsed time: 6 mins 42 secs
Priority: 10
FD Files Written: 17
SD Files Written: 0
FD Bytes Written: 121,451 (121.4 KB)
SD Bytes Written: 0 (0 B)
Rate: 0.3 KB/s
Software Compression: 100.0 % (gzip3)
VSS: yes
Encryption: no
Accurate: yes
Volume name(s):
Volume Session Id: 3535
Volume Session Time: 1551338230
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 17
SD Errors: 0
FD termination status: Fatal Error
SD termination status: Error
Bareos binary info: bareos.org build: Get official binaries and vendor support on bareos.com
Termination: *** Backup Error ***

When I reboot the Windows server the backup runs fine, but after a few days, I get the same "Wrote x bytes to Storage daemon but only 0 accepted".

Configuratin is quite straightforward. The only special is that I'm using client initiated connection from FD to DIR:

Director {
Name = bareos-dir
Password = "password"
Description = "Allow the configured Director to access this file daemon."
Address = ip address

Connection from Client to Director = yes
Connection from Director to Client = no

}

[Jurgen Goedbloed]

An update to this issue: the cause was network misconfiguration.

This Windows server is running on Openstack. The MTU on an openstack network is lower than the default of 1500 bytes. The windows server had an MTU of 1500 bytes, that caused this issue. I changed it to the correct MTU and now backups run fine.