Troubleshooting Common Issues in Windows BMR

Bacula Enterprise Only

This solution is only available for Bacula Enterprise. For subscription inquiries, please reach out to sales@baculasystems.com.

QUESTION: I don’t seem to have any connectivity with the WindowsBMR, what can I do?

ANSWER: This is most probably because the drivers of your Ethernet NIC

are not present on the WindowsBMR iso.

The Using Additional Hardware Drivers section explains how to solve this problem.
QUESTION: It looks like the Bacula Director cannot connect to my client, I have checked that passwords and port match, but I still cannot connect, why?

ANSWER: This happens most often if the machine that you are trying to restore is on a different subnet than your director; place the machine into the subnet where your Director is connected.
QUESTION: I restored onto different hardware, and it doesn’t reboot, why?

ANSWER: This is most probably because your original Windows didn’t include the drivers for your new hardware or Windows has not been set up to use these drivers as boot device. Restore onto the same hardware or install the required drivers in the original machine, add these drivers to the list of drivers on which the system can boot on and back up again.
QUESTION: I restored onto the same hardware, but a different disk, and it doesn’t reboot, why?

ANSWER: This is because you still have the original partition in your BCD file; you can solve this by removing your original drive from the machine. It may also help to disable the original drive in the BIOS configuration.

Please note that if you already rebooted and tried to repair the bootloader things can be broken – it is much better to have the original disk removed before the first attempt to boot the recovered system.
QUESTION: The diskpart never ends the disk inventory. What can I do?

ANSWER: Please check if some of the disks are made available through an HBA interface and disconnect it. The HBA disk may be restored after the basic server is restored.