Create Recovery Media - include hardware drivers

[robnicholsonmalt]

When you run Create Recovery Media from a workstation protected by B&R server you get options to include network connections and hardware drivers:



However, if you create ISO from the B&R console, you don't get these options. Why the discrepancy and what options does creating recovery ISO from B&R console have enabled?



The reason I ask is that I've never been able to restore my Windows 10 workstation from the repository. If restores fine but then won't boot with this error:



In another post, there was a comment about using the recovery media from a different machine hence the reason for me asking about this difference in recovery media creation.

[Dima P.]

Hello Rob,

System drivers are collected automatically but you may need to load network or storage drivers while you are booting from the media. Please raise a support case and let our team investigate the debug logs - they can provide a clear picture on why machine is not booting. Do not forget to share the case ID with us. Thank you!

[Gostev]

Judging on the name kdnic.sys the BSOD is due to a wrong network card driver?

[robnicholsonmalt]

I've since replaced my PC running Windows 11 this time and it's working fine here.

[DanielJ]

I have not been able to get the recovery ISO working. It just goes to BSOD after a few seconds. Since it was created by VBR, I suspect that the OS version of the VBR server and of the backed up vm plays a role, even if I haven't found any such indication in the user guide. When you say "System drivers are collected automatically" is it then from the OS that VBR is running in, or from the OS in the backup from which the ISO is created?

[robnicholsonmalt]

Referring back to my bluescreen after restore, I suspect the problem was my motherboard which I suspect was a Friday/v1 jobby as it had several quirks: it was totally unstable with anything but the very first BIOS, Veeam and Macrium Reflect often reported errors restoring from backup (try a few times and it worked) and USB-3 was flaky.

I've since replaced the motherboard and Veeam restores perfectly from the backup repository.

[DanielJ]

Well, when I test this it's from a vm. ISO created from the backups of the vm, booted on the same vm: BSOD. There are not even any options to possibly get wrong.

[DanielJ]

I wonder if I can get a response to the question above: does "System drivers collected automatically" mean that they are collected from the agent OS or from the VBR OS?

I have opened 07541269 before the weekend. The only response so far would have been useful if the vm had been on a patch level from 2022.

[Gostev]

From the agent OS of course, as that's the only place where drivers from the hardware of the protected system exist in the first place.

[DanielJ]

I'm just grasping at straws to try to understand what makes the recovery ISO little more than a BSOD generator for me. I have tried different vms, a physical server and my own computer. This from a process that leaves no options: Take backup - Generate ISO - Boot from ISO - BSOD.

[Gostev]

Are you booting from the ISO on the same machine you created it from?

[DanielJ]

Yes, the same machine whose backups it is created from.

[Gostev]

Then I guess some 3rd party software impacts the ISO creation process somehow. As I can't imagine ISO not working in a VM considering most of our auto testing is done using VMs of course. So QA should have seen any such issues internally many times

[DanielJ]

There is no such third party software. I have spent two full days testing different restore scenarios. I am at a loss. The ONE thing I got working was using an ISO created from a totally different backup than the vm I tried booting it from. That booted successfully.