Give a try and create recovery media from Console, not from agent!

https://helpcenter.veeam.com/docs/backup/agents/agent_backup_create_image.html?ver=120

Edit. Sorry, missread. You already did that.

Hi, thank you. I already created the boot media this way, from VBR Console (on the backup server).

Backup of that Win server is managed by backup server or managed by agent?

If it’s the second, I’ll give a try to create recovery media from Agent itself.

Managed by Backup Server

Hi Simon, could it be that during the copy the backup file got corrupted? Have you tried to restore using the original backup repository as the source?

Similar issue solved by the community:

Hello, thanks but I mentionned this thread in my question … as I said, backup and media creation are made with same (latest) versions, so this case didn’t helped me much.

Hello, same problem her.

Trying to validate bare-metal recovery of a physical Windows 2019 server. Copied the backup files on usb drive, created recovery media from VBR and tried to restore on a different server.

“Veeam Agent for Microsoft Windows is unable to open backup files created by Veeam Backup & Replication”

The version of the agents at backup and restore time is the same?

I know this link is for Agent v6.0 but did you select the option for the files on the network and then point it to the VBR server rather than copying the files to a USB disk and using that?  Just wondering if both methods were tried?

How to Perform Bare Metal Recovery - Veeam Agent for Microsoft Windows Guide

Step 6 shows selecting network location.

Hello, yes agent version is the same (installed 5 days ago, no update since)

I did not try, as I don’t have the same VLAN and FW configuration on my office, the backed up Windows server is in a remote site. And as our VBR systems are isolated, it will require to open FW rules. I wanted to avoid this for the test, ans also validate that having “only” a backup and the boot media will do the job.

The server is on a different place/network. So i just copied the backup files to usb drive, bring it to our company and want to test a bare metal recovery..

Ok - so then when you copied the files to the USB drive did you copy all files - VBM, VBK, VIB for the entire backup chain?  If you are missing files in the chain that might be possibly why it cannot read the files properly.  Something to check and make sure.

Ok, but you tried a recovery media created directly from the agent itself?

This too is super important.

To be more detaild, i have a backup copy job to a usb drive. This usb drive was cloned, so i think i got all files.

But maybe the copy job is the problem in this scenario?

I would take the data from the primary job…

The format of the copy jobs is slightly different.

Backup copy job produce a forever incremental, it's possible that got corrupted. Have you select the Health check guard (weekly or how you prefer)?

And have you tried to copy vbks directly from the original source? And here, you have a Synthetic with Check guard or a full weekly or monthly?

but i just wanted to test a ransomware scenario, with only backup copy on usb drives are available for restore..

Agreed with Joe here on this one.

The Veeam agent and it's recovery media cannot access backup copies directly. You need to access those through a Veeam Backup repository. So in case of a DR, you would have to install a fresh VBR server, import the backup files and then connect the recovery media to this VBR server.

OK, thanks for these response, I also used the data (complete backup chain) from a backup copy job.

I will try to use original backup repo data and give you a feedback.

Hm, i tried the following. Import the Backup Copy to my Veeam Server Repository, started the bare metal machine with veeam usb stick, and choose bare metal recovery from my veeam server repository. There are all machines available for restore but not the imported backup copy.

So, backup copy can’t be used for a system restore? Or am i missing something?

Next try. Created a repository for usb drives like on the original place, imported the backup copy and now i can choose the machine for bare metal recovery and the restore works!