When a local client connects via IPv6 file backups fail:
ERROR Error getting filelist of CLIENT. Errorcode: TIMEOUT (2)
In order to get it to run, I have to restart the client service a random number of times till it randomly decides it will use IPv4.
Would be helpful if the server had an option to simply disable IPv6 support, as I don’t use IPv6 for local connections & my ISP doesn’t support it for remote ones.
Took me quite a while to figure out what was going on & why one client suddenly stopped completing file backups (oddly image backups were working, which distracted me from looking at simple client/server connectivity issues).
@Bearded_Blunder thanks for the analyses! I can confirm this issue in different installations.
The backup of the windows clients runs only sometimes or very delayed. I got error mails every time and the urbackup.log contains the error messages:
...
2020-09-01 08:47:55: ERROR: Incremental Backup of NBTerra-Rektor failed - CONNECT error -2
2020-09-01 08:48:01: ERROR: Backup had an early error. Deleting partial backup.
2020-09-01 08:48:02: WARNING: Exponential backoff: Waiting at least 40m before next file backup
2020-09-01 09:28:16: WARNING: Restarting shadow copy of C:\ because it was started by this server
2020-09-01 09:28:16: ERROR: Incremental Backup of NBTerra-Rektor failed - CONNECT error -2
2020-09-01 09:28:22: ERROR: Backup had an early error. Deleting partial backup.
2020-09-01 09:28:23: WARNING: Exponential backoff: Waiting at least 1h 20m before next file backup
2020-09-01 10:48:36: WARNING: Restarting shadow copy of C:\ because it was started by this server
2020-09-01 10:48:36: ERROR: Incremental Backup of NBTerra-Rektor failed - CONNECT error -2
2020-09-01 10:48:43: ERROR: Backup had an early error. Deleting partial backup.
2020-09-01 10:48:44: WARNING: Exponential backoff: Waiting at least 2h 40m before next file backup
...
As soon as i deactivate ipv6 on the urbackup linux host, the backup of the windows clients works smoothly.
@uroni @ Developers
Please take note of this report and maybe there is a possibility to find a fix.
Thanks for this great backup software!
@dmnet On my setup (Server 2012R2), since I don’t use IPv6 anyway, I worked around the issue by simply unchecking IPv6 in my network adapter properties on the server.
This sadly renders any debug logs I might have produced for @uroni before doing so moot only I’d done it already by the time he suggested obtaining them, but fixed backups.