the following error messages appear in the debug.log file a lot (as well as the server log)
2024-01-03 10:24:26: ERROR: FileSrv: Could not open file \?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\redcellpartners\eyris-demo\websites\dashboard\chain\node_modules\tar\node_modules.bin\mkdirp. The file cannot be accessed by the system. (code: 1920)
2024-01-03 10:24:39: FileSrv: SOCKET_ERROR in SendData(). BSize: 16384 WSAGetLastError: 10053
2024-01-03 10:24:46: ERROR: FileSrv: Could not open file \?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\redcellpartners\eyris-demo\websites\dashboard\chain\node_modules\web3-eth-accounts\node_modules.bin\uuid. The file cannot be accessed by the system. (code: 1920)
These files are actually on my E drive, and they are all zero bytes in length. Looks like Urbackup getting confused between not being able to read any data and the file does not existing ?
Window Client version 2.5.25.
server is running under truenas with the docker image from latest-zfs.
The client is running on Windows 10 with all current windows updates.