Bare metal restoration with Veeam Recovery Media

[tlaugier]

Hello, I am trying to restore a Veeam backup on a bare metal server using the Veeam Recovery Media but I am unable to see the backups.
The original backups have been generated by one server, they have been copied to a secondary Veeam server using a Backup Copy job. I then exposed those backups on a network share and imported them in the second Veeam instance. Once imported I created a recovery media which I used to boot the server.
However when I enter the file share unc path in the Bare Metal Recovery tool it says there are no backups in the file share.
Do I have to do anything particular in the Veeam console to be able to see those backups ?

[Gostev]

Hello, are you using the latest version? As what you are trying to do wasn't supported until recently.

[tlaugier]

I am using version 12.3.0.

[Gostev]

In that case please open a support case for further investigation.

[gocart879]

Try using IP address for server instead of server name, also there is an area in the boot iso where you can select ip address configuration, worth going in there and removing the static address if it is in there and setting for dhcp. Both of those things prevented me from seeing a backup when doing the same restores.

[rkpal]

Hi, I have raised a technical Support Case Number 07721759, and the Veeam Technical team suggested that I contact the Veeam R&D team through this forum.

Case Details: In my test environment, I'm working on restoring both a Dell physical server and a workstation. The environment is running Veeam Backup & Replication (B&R) v12.3, with the Veeam Agent for Windows (version 6.3.1.1074) fully integrated with the B&R server.
The issue arises when I create restore media from the Veeam B&R console, there is no option to inject Windows 10 drivers. When I boot the target machine using this recovery media, the boot process fails with a Windows blue screen.

However, if I go directly to the client machine (where the Veeam Agent is installed) and manually run:
C:\Program Files\Veeam\Endpoint Backup\VeeamEndPointRecoveryMedia.exe

it gives me the option to inject the required drivers. I use a Windows 10 ISO to inject the necessary drivers during the recovery media creation. The recovery media generated this way works as expected and successfully restores the machine.

During testing, I noticed that when creating recovery media for Windows 10 or later operating systems using the Veeam B&R console, the boot process consistently fails. Only the recovery media created directly from the machine (using the Veeam agent and driver injection via Windows 10 ISO) seems to function correctly.

Since the agent is integrated with the B&R server, I would expect to have similar driver injection capabilities directly through the B&R console. Creating recovery media manually on the client machine is not an ideal or scalable solution. Could you please advise if there is a way to inject drivers when creating restore media from the Veeam B&R console? We have a Standard Operating Environment (SOE) for our systems, and making any changes to it would be both time-consuming and costly. If Veeam can provide an option within the console to inject drivers while creating the recovery media, it would help resolve this issue for us.

[Mildur]

Hello Rakesh,

The issue arises when I create restore media from the Veeam B&R console, there is no option to inject Windows 10 drivers. When I boot the target machine using this recovery media, the boot process fails with a Windows blue screen.

Customization of the recovery media should not be necessary if you are restoring back to the original hardware. All driver files for the protected machine are collected by the backup job, allowing you to create a fully functional recovery media from the backup console without needing to add additional drivers.

If you are still encountering blue screens, please continue to work with support to investigate the root cause. It sounds like your request is looking for a workaround to address another underlying issue. I believe we should resolve the root cause before considering additional, non-required functionality in the product.

Best,
Fabian