Could not read MBR after upgrade to 2.0

1

I upgraded my server to 2.0.30. Then I went to one of my clients and downloaded its client from my server. It installed ok. That particular machine only does image backups. when it trys to do an incremental image backup I get

Could not read MBR
Cannot retrieve master boot record (MBR) for the disk from the client.

This was working under 1 series. I have tried removing urbackup reboot intall client downloaded from server but that has not solved the issue. I have tried going to server and forcing incremental backup but get same errors. Any ideas ?

2

Have you try a full image backup ?

3

Same Errors

4

Could you have a look at the client side log file at C:\Program Files\UrBackup\debug.log?

5

2016-07-05 17:34:40: ERROR: Recvfrom error in CUDPThread::UdpStep

2016-07-05 17:34:40: ERROR: Last error: 0

2016-07-05 18:38:50: ERROR: Ident reset (1)

2016-07-05 18:39:15: ERROR: Ident reset (1)

2016-07-06 04:39:42: ERROR: Ident reset (1)

6

Just checked other backup machine and it is having this issue

Error opening previous bitmap (/Backups/XPS7100/Image_C_160620-2051.vhdz.cbitmap). No such file or directory

There are cbitmap files under SYSVOL directories but none match the above.

7

I have been running server 2.0.29 for a week and have one client on 2.0.29 and it is working fine. Just added a brand new client using 2.0.29 on windows and now I am getting:
Errors 07/07/16 15:20 Could not read MBR
Errors 07/07/16 15:20 Cannot retrieve master boot record (MBR) for the disk from the client.
Errors 07/07/16 15:20 Backup failed

Update: After rebooting the client, backup has started and appears to be working.

8

The *.cbitmap files are created since 2.0.x, so this is a backward compatibility issue. Will fix it such that it has a fall back in case the cbitmap file does not exist. A full image backup should fix this as well.

9

An update if anyone has this issue. Uroni’s answer is the solution to all problems I had. So after upgrading have all clients do full image and full backup to avoid issues.

10

Hello

I have the same Problem since updatet from 1.4 to 2.0.31 (Client 2.0.30)

Operating System = Windows Server 2012 NO R2

Protokoll: (SERVER XXXX)
Level
Zeit
Nachricht
Fehler
02.08.16 14:54
Could not read MBR. Error message: Did not find PartitionNumber of dynamic volume. Volume: ‘D:’

Fehler
02.08.16 14:54
Cannot retrieve master boot record (MBR) for the disk from the client.

Fehler
02.08.16 14:54
Backup failed

Protokoll: (SERVER XXXX)
Level
Zeit
Nachricht
Fehler
02.08.16 13:38
Could not read MBR. Error message: Did not find PartitionNumber of dynamic volume. Volume: ‘D:’

Fehler
02.08.16 13:38
Cannot retrieve master boot record (MBR) for the disk from the client.

Fehler
02.08.16 13:38
Backup failed

FULL BACKUP

I have no Idea … Please Help

11

All you need do is force full image backup and full backup that will correct the issue,

12

how do you force a backup …thanks

13

Hello

I made a FULL BACKUP.

How can i “FORCE” a Backup?

Regards

14

Forcing a backup means telling server to do a backup, as in go to webinterface, choose a client and click on Full Image Backup. Forcing here is “doing a backup outside of intended backup window”

15

Ok

Thats what I’m doing X-Times. But this will not help to run the backup correctly.

regards

16

I’ll make it continue after such an error with 2.0.33, but as before restoring dynamic volumes will be problematic.

17

Urbackup 2.0.33 ?
https://www.urbackup.org/ = 2.0.21 is the last Version

18

But the page you linked says 2.0.31 for server, 2.0.2 being recovery CD

19

Sorry correct 2.0.31 but not 2.0.33

20

Either Uroni drops 2.0.33 today, or his finger slipped. You can check newest version here -> https://www.urbackup.org/downloads/Server/