PC turned off during backup -> backup doesn't timeout

client
1

6 days ago, during backup, PC was turned off by user and then never turned on again (he went on vacation). Even after those 6 days Admin Center still showed that backup is currently ongoing. I had to manually Stop it from “Activites” page. Why didn’t Urbackup detect timeout and stop backup and notify me about it? Log is:

|25.09.24 13:20  |INFO  |Starting scheduled incremental image backup of volume C:...|
|---|---|---|
|25.09.24 13:20  |DEBUG  |Backing up SYSVOL...|
|25.09.24 13:20  |DEBUG  |Backing up SYSVOL done.|
|25.09.24 13:20  |DEBUG  |Backing up EFI System Partition...|
|25.09.24 13:20  |DEBUG  |Backing up EFI System Partition done.|
|25.09.24 13:20  |INFO  |Basing image backup on last full image backup|
|01.10.24 08:19  |DEBUG  |Script does not exist urbackup/post_incr_imagebackup|
|01.10.24 08:19  |INFO  |Time taken for backing up client xyz: 5 days 18h 58m 47s|
|01.10.24 08:19  |ERROR  |Backup failed|
2

Maybe - client literally “turned machine off” - ie - didn’t shutdown and hence the windows networking didn’t detect a disconnect?
Did your server network status show that there was no connection? Anything in system logs?
It may be a bug in Urbackup timeout code. But, that has not been my experience. (Different OS)
If you have got a machine you don’t mind playing with - you could add it to the urbackup server list of clients and pull the plug on it - then compare to shutting down.

Good luck
David

3

I’m 99,9% sure that he didn’t “turn off power” or “held power button for 4 seconds” or something like that. I don’t remember what was his “last seen”, but I have another similar case. One PC was lagging very much during backup because it is an older low spec PC. Not thinking about it too much, I just uninstalled urbackup from that PC during it’s backup, and then I went to webadmin and removed that pc. And today I received this e-mail from urbackup

UrBackup just did an incremental image backup of "somepc".

Report:
( 4 infos, 0 warnings, 2 errors)

2024-09-24 14:34:41(info): Starting unscheduled incremental image backup of volume "C:"...
2024-09-24 14:36:22(info): Basing image backup on last full image backup
2024-10-04 14:39:56(error): Timeout while trying to reconnect
2024-10-04 14:39:56(info): Transferred 1.26401 GB - Average speed: 12.56 KBit/s
2024-10-04 14:39:56(info): Time taken for backing up client somepc: 10 days 4m 54s
2024-10-04 14:39:56(error): Backup failed

It looks like the timeout window is ~240 hours. I didn’t see anywhere in options to change it. Is it hardcoded?

4

Backups can resume from where they left off, even after 6 days.
That’s why it kept showing in the Activities.

5

@MrBates that it’s true and checked myself backups being resumed after several days waiting, but if you have defined “Max simultaneous backup” at “1” and machine doing backup goes down for a week you have all that week the Only Slot Busy without doing any backup more till machine going up or timeout comes.

So I think would be very interesting having THAT TIMEOUT user configurable.

Thanks
Raimon