Full Image Backup fails:Could not read MBR

client
1

Hi,

I am fairly new to UrBackup so this can be a rookie mistake. However: I am failing to get UrBackup to work for imaged based backups. I already checked all the forum posts regarding that issue, none of them leaded to a solution.

Setup

Server:

Infscape Appliance
(Shell-install on fresh Debian 11 on a Hetzner Cloudserver)
System version: 11.43
Linux kernel version: Linux 5.10.226
Based on: Debian GNU/Linux

Client:

Windows Server 2022 21H2 (all the latest updates applied)
UrBackup Client 2.5.25

Issue:

  • After starting an Full image based backup it fails with the following error message:
21.12.24 00:16  	INFO  	Starting unscheduled full image backup of volume "C:"...
21.12.24 00:16  	DEBUG  	Backing up SYSVOL...
21.12.24 00:16  	DEBUG  	Backing up SYSVOL done.
21.12.24 00:16  	DEBUG  	Backing up EFI System Partition...
21.12.24 00:16  	DEBUG  	Backing up EFI System Partition done.
21.12.24 00:16  	INFO  	Basing image backup on last incremental or full image backup
21.12.24 00:16  	WARNING  	Error retrieving last image backup. Doing full image backup instead.
21.12.24 00:17  	ERROR  	Could not read MBR
21.12.24 00:17  	ERROR  	Cannot retrieve master boot record (MBR) for the disk from the client.
21.12.24 00:17  	INFO  	Time taken for backing up client XX.XXX.com: 1m 2s
21.12.24 00:17  	ERROR  	Backup failed

debug.log

4-12-21 00:16:10: ClientService cmd: STATUS DETAIL#pw=XXX
2024-12-21 00:16:10: Started connection to SERVICE_COMMANDS
2024-12-21 00:16:10: ClientService cmd: #I5TQVOqYja0S5ZzRgNaPZ#MBR driveletter=SYSVOL&disk_path=SYSVOL&image_full=1&running_jobs=1&token=XXX
2024-12-21 00:16:10: rc=0 hasError=true state=0
2024-12-21 00:16:10: SERVICE_COMMANDS finished
2024-12-21 00:16:11: ClientService cmd: STATUS DETAIL#pw=XXX
(... some status pings here...)
2024-12-21 00:16:20: ClientService cmd: STATUS DETAIL#pw=XXX
2024-12-21 00:16:20: Started connection to SERVICE_COMMANDS
2024-12-21 00:16:20: ClientService cmd: #I5TQVOqYja0S5ZzRgNaPZ#FULL IMAGE letter=SYSVOL&token=XXX&bitmap=1&status_id=31&running_jobs=1&zero_skipped=1
2024-12-21 00:16:20: Filesystem type is ntfs (\\?\Volume{b0debac4-0000-0000-0000-100000000000})
2024-12-21 00:16:20: TotalNumberOfClusters=25599 numberOfClusters=25599 n_clusters=3200 StartingLcn=0 BitmapSize=25599 r_bytes=3216
2024-12-21 00:16:20: FSINFO: blocksize=4096 size=104857088 has_error=false used_space=29134848 type=ntfs_win
2024-12-21 00:16:21: Sending full image done
2024-12-21 00:16:21: Removing running process (1) id 3 server_id 31 token 8LDeiBIgIfu3Pz9V4CTw action 3
2024-12-21 00:16:21: Service finished. Transferred 12.3596 MB
2024-12-21 00:16:21: SERVICE_COMMANDS finished
2024-12-21 00:16:21: ClientService cmd: STATUS#pw=XXX
(... some status pings here ...)
2024-12-21 00:16:31: ClientService cmd: STATUS DETAIL#pw=XXX
2024-12-21 00:16:31: Started connection to SERVICE_COMMANDS
2024-12-21 00:16:31: ClientService cmd: #I5TQVOqYja0S5ZzRgNaPZ#MBR driveletter=ESP&disk_path=ESP&image_full=1&running_jobs=1&token=XXX
2024-12-21 00:16:31: rc=0 hasError=true state=0
2024-12-21 00:16:31: SERVICE_COMMANDS finished
2024-12-21 00:16:32: ClientService cmd: PONG
2024-12-21 00:16:32: ClientService cmd: STATUS DETAIL#pw=XXX
(... some status pings here...)
2024-12-21 00:16:41: ClientService cmd: STATUS DETAIL#pw=XXX
2024-12-21 00:16:42: Started connection to SERVICE_COMMANDS
2024-12-21 00:16:42: ClientService cmd: #I5TQVOqYja0S5ZzRgNaPZ#FULL IMAGE letter=ESP&token=XXX&bitmap=1&status_id=32&running_jobs=1&zero_skipped=1
2024-12-21 00:16:42: ERROR: Not found
2024-12-21 00:16:42: rc=0 hasError=true state=0
2024-12-21 00:16:42: SERVICE_COMMANDS finished
2024-12-21 00:16:42: ClientService cmd: STATUS DETAIL#pw=XXX
(... some status pings here...)
2024-12-21 00:16:52: ClientService cmd: STATUS DETAIL#pw=XX
2024-12-21 00:16:52: Started connection to SERVICE_COMMANDS
2024-12-21 00:16:52: ClientService cmd: #I5TQVOqYja0S5ZzRgNaPZ#2PING RUNNING pc_done=0&status_id=30&speed_bpms=0&total_bytes=-1&done_bytes=0&paused_fb=1#token=XXX
2024-12-21 00:16:53: ClientService cmd: STATUS DETAIL#pw=XXX
(... some status pings here...)
2024-12-21 00:17:02: ClientService cmd: STATUS DETAIL#pw=XXX
2024-12-21 00:17:02: ClientService cmd: #I5TQVOqYja0S5ZzRgNaPZ#2PING RUNNING pc_done=0&status_id=30&speed_bpms=0&total_bytes=-1&done_bytes=0&paused_fb=1#token=XXX
2024-12-21 00:17:03: ClientService cmd: STATUS DETAIL#pw=XXX
(... some status pings here...)
DETAIL#pw=XXX
2024-12-21 00:17:12: rc=0 hasError=true state=0
2024-12-21 00:17:12: SERVICE_COMMANDS finished
2024-12-21 00:17:13: ClientService cmd: STATUS#pw=XXX
2024-12-21 00:17:13: ClientService cmd: STATUS DETAIL#pw=XXX
2024-12-21 00:17:13: Started connection to SERVICE_COMMANDS
2024-12-21 00:17:13: ClientService cmd: #I5TQVOqYja0S5ZzRgNaPZ#2LOGDATA 1734735380 0-1734735325-Starting unscheduled full image backup of volume "C:"...
0-1734735367-Basing image backup on last incremental or full image backup
1-1734735367-Error retrieving last image backup. Doing full image backup instead.
2-1734735377-Could not read MBR
2-1734735377-Cannot retrieve master boot record (MBR) for the disk from the client.
0-1734735380-Time taken for backing up client XX.XXX.com: 55s
2-1734735380-Backup failed

2024-12-21 00:17:13: rc=0 hasError=true state=0
2024-12-21 00:17:13: SERVICE_COMMANDS finished

What I already tried to resolve the issue

  • ran chkdsk on C:
  • Researched this forum for a solution

Any help would be greatly appreciated.

2

Hi,

Just a couple of quick questions…

Are the two systems (server and client) on the same network, or is there some routing between them…?

Have you got file backups working on this…?

Client is physical or virtual…?

Do you have any other clients on this server that are working…?

3

Hi @OnlyMe,

thanks for your reply. Here some answers:

  • No, there is routing in between.
  • File Backups work just fine (except for one error: “C/Users/Administrator/AppData/Local/Docker/run/userAnalyticsOtlpHttp.sock” from XXX.XXX.com. Errorcode: CANNOT_OPEN_FILE (3)"
  • Both client and server are virtual.
  • Currently I do not have any other client on that server, because I just started testing UrBackup. But for sure I can add another client for testing purpose.
4

There should be some MBR driveletter=C message in the client log. Is this really not there or is it in the part you skipped?

5

I can confirm, it is really not there.

Bildschirmfoto 2024-12-21 um 16.14.18
Bildschirmfoto 2024-12-21 um 16.14.18802×698 154 KB

However, in regard to this thread

I want to point out, that C is set as drive to create an image from:

Bildschirmfoto 2024-12-21 um 16.15.19
Bildschirmfoto 2024-12-21 um 16.15.191184×860 138 KB