First I have to say, I’m not sure, if that post here helps in any way to find the error, since there seem to be no usable log files. anyway:
We’ve got a windows 2011 small bussiness server with urbackup client 2.0.36 running on it.
Backups worked well, until at once, about 1 or 2 weeks ago, incremental, full and image backups failed, always with one of 3 messages:
Info
02.02.17 22:08
Starting full image backup…
Errors02.02.17 22:08
Could not read MBR
Errors02.02.17 22:08
Cannot retrieve master boot record (MBR) for the disk from the client.
Info02.02.17 22:08
Time taken for backing up client RMI-Windows-SBS2011: 15ms
Errors02.02.17 22:08
Backup failed
or
Info
02.02.17 22:03
Starting full image backup…
Errors02.02.17 22:03
Backing up System Reserved (SYSVOL) partition failed. Image backup failed
Info02.02.17 22:03
Time taken for backing up client RMI-Windows-SBS2011: 1s
Errors02.02.17 22:03
Backup failed
or
Info
02.02.17 22:03
Starting full file backup…
Errors02.02.17 22:03
Constructing of filelist of “RMI-Windows-SBS2011” failed: ERR
Errors02.02.17 22:03
Backup had an early error. Deleting partial backup.
So today I finally found time to look into it, and noticed that on the client, debug.log wasn’t updated anymore since the 16.1.2017 (that’s when the last successfull backup was made). So since then I always got error messages (only logged on the server) and the client didn’t manage to write to debug.log anymore. So I wanted to activate the log level “debug” (before we used “warn”) to see if I get something written and restarted the urbackup service on the windows machine. And since then it works perfectly again. Also debug.log is updated again.
I guess there must be a bug somewhere, but unfortunately I really can not provide you any more information than the above ones (if there is any, just ask). My best guess is that he tried to write some warnings to the debug.log, for whatever reason couldn’t write them, and because of that utterly failed, whatever he just tried or he already failed before he even couldn’t open the debug.log file.