Having issues with image backups

Server
1

Hi,

Putting this in the “Server” category as it happens for multiple [Windoze] clients with the exact same error…

Until around the second week of February, all of the Windoze (7/10/11) clients were happily running image backups, but suddenly stopped working for any image backups, whether full or incremental jobs…sharing the logs for one client in particular…

Screenshot_20250410-225234
Screenshot_20250410-2252341080×2340 233 KB

Level Time Message
Info
06/04/25 20:18
Starting scheduled full image backup of volume “C:”…
Info
06/04/25 20:20
Basing image backup on last incremental or full image backup
Errors
06/04/25 20:22
Exchanging data with client during image backup preparation failed. Connection to client broke.
Info
06/04/25 20:22
Time taken for backing up client ####LAP002: 4m 30s
Errors
06/04/25 20:22
Backup failed

Screenshot_20250410-225316
Screenshot_20250410-2253161080×2340 227 KB

Have restarted the server and also all the clients, but still no dice…

For reference, in case it matters, host is a physical Ubuntu server and this is the UrBackup 2.5.33 server code…there aren’t any issues with storage on the host, and other backup jobs have been seen running before, during, and after the image jobs that fail - have also tested running manually, and when no other jobs [including housekeeping maintenance] are running…

Has anyone else seen this, or have any ideas as to how to get image backups working again…?

2

Hello

Seems like you have something on your network that cut connections when it see much traffic to specific hosts.

Is our backup server local or via internet backup?

3

My backup host server sits on a segregated VLAN to everything else, but it is internet accessible for when I go elsewhere…

This was working happily until about the first half of Feb this year, and was in place for over a year before it stopped…

Can see that it starts the backup, and it doesn’t matter whether the image is the only thing running [to my UrBackup host] or if there are other jobs running…the host is also happy with there being a handful of concurrent file jobs running, it just refuses/drops the image jobs’ data transfer…