Windows Server Backup: Option to restore VM is greyed out.

[driekeshvd]

Hi,

We have a hyper-V host running 2019 CORE, with some VM’s running 2019 standard.

I backed up a virtual machine (at least, I think I did) with Windows Server Backup from the host. The backup reside on a USB disk connected to the host. The backup was set up from another VM via server manager → computer manager.

When I try to restore the VM, the option to restore “Hyper-V” is greyed out in “Select Recovery Type”.

Did I make a mistake in the backup process?

[adrian_ych]

Please get a proper backup software like Veeam Backup & Replication for Hyper-V (if less than 10 VMs, you can try or use the community edition).

Veeam Data Protection Platform Features Comparison | Veeam

…

Then the problem is that you are actually running server 2019 std “core” with hyper-v feature and not hyper-v 2019. So are you actually backing up the VMs like files on a file server and not a VM ?? Then you will need to restore the VM as if they are files and see if they can be piece together as a VM.

Hyper-V server and/or ESXi will not have this issue (coz they will not have option to use Server backup as well).

…

Do you want to show screenshot of your backup settings as well ?

[lsxcpu]

Did you not back up the system volume information? Ie. The boot volume.

[adrian_ych]

@lsxcpu

Did you not back up the system volume information? Ie. The boot volume.

I think he meant the VM, not recovery of host…

[bagaudin-acronis]

It looks like the backup doesn’t contain the VM backups, at least not detected correctly or you’re running restore from the server without the Hyper-V role.

I am curious as to how exactly you created the original backup and what is the directory path and content of the backup folder.

For reference here is the example from my test setup:

Also, see if you can just mount the .vhd(-x) file to extract the backed up .vhd(-x) with VM files as a last resort.

[adrian_ych]

@bagaudin-acronis

For reference here is the example from my test setup:

Can you do a test recovery as well ??

BTW, I would the best is to move off Server backup and use a proper backup solution (backup software with backup repository) ?

[driekeshvd]

@adrianyong4136

So are you actually backing up the VMs like files on a file server and not a VM ?? Then you will need to restore the VM as if they are files and see if they can be piece together as a VM.

My mistake. Indeed, I was backing up the files instead of backing up the VM. This was just a test VM.

The restore went fine.

We already have Backup Exec. Using WSB will probably just be a temporary solution.

Thank you.

[adrian_ych]

@driekeshvd

@adrianyong4136

So are you actually backing up the VMs like files on a file server and not a VM ?? Then you will need to restore the VM as if they are files and see if they can be piece together as a VM.

My mistake. Indeed, I was backing up the files instead of backing up the VM. This was just a test VM.

The restore went fine.

We already have Backup Exec. Using WSB will probably just be a temporary solution.

Thank you.

Backup Exec which edition ?

There are many reasons to use Veeam or Vembu as they are “VM born” backup software…whereas the others are evolved from physical machine backups.

Do review Veeam or Vembu…

[driekeshvd]

Backup Exec which edition ?

There are many reasons to use Veeam or Vembu as they are “VM born” backup software…whereas the others are evolved from physical machine backups.

Do review Veeam or Vembu…

20.6. I did not have a say in selecting the backup software.

It is becoming a pain. I’m having trouble in backing up VM’s running 2019. I cannot seem to use GRT. I would like to use Instant VM recovery to test the backup’s.

The backup job always returns “Failed to mount one or more virtual disk images”. I don’t know if i’m willing to invest more time on this issue.

[bagaudin-acronis]

@adrianyong4136

they are “VM born” backup software…whereas the others are evolved from physical machine backups.

I’ll add Acronis Cyber Backup and Acronis Cyber Backup Cloud as there were two separate evolution tracks started with True Image Echo (physical) and vmProtect (Virtual) :))))