Can't restore the whole disk from Veeam Recovery Media

[Rumato163]

Hello all.
The steps:
1. Install Free Linux Veeam Agent on OEL6 VM on MS HyperV
2. Create a backup of whole bootable disk sda with all LVM volumes on it
3. Boot from Veeam Recovery Media and try to restore the whole sda

The issue:
Veeam Recovery Media can't recognize sda disk on VM and I can't perform a restoration of it.

What was tried/completed:
1. The second disk on VM is present in Recovery Media menu. So I've decided to mount both of vm discs on the same IDE buss.
2. Try to remove the second sdb from the vm

Nothing has done the trick

[nielsengelen]

It's currently a known bug that restores on LVM volumes doesn't work as expected (see veeam-agent-for-linux-f41/does-veeam-ag ... 36134.html as well) however we will adjust this in an upcoming version.

[Rumato163]

Understood.
Do you have any estimations about release date of next version?

[PTide]

Hi,

Do you have any estimations about release date of next version?

By the end of this month.

OEL6 VM on MS HyperV

Is it Gen2 or Gen1 VM?

Veeam Recovery Media can't recognize sda disk on VM and I can't perform a restoration of it.

Could please provide more detailed description? Is sda visible in the recovery UI and jus throws errors or it's not shown at all?

What are partition tables on both disks? Please provide an output of lsblk.

Thank you.

[Rumato163]

Is it Gen2 or Gen1 VM?

What do you exactly mean? How can it be determined?

Is sda visible in the recovery UI and jus throws errors or it's not shown at all?

It is not visible at all.

What are partition tables on both disks? Please provide an output of lsblk.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 1024M 0 rom
sda 8:0 0 16G 0 disk
├─sda1 8:1 0 256M 0 part /boot
└─sda2 8:2 0 15.8G 0 part
└─vmdisk1-lv_root (dm-0) 253:0 0 15.8G 0 lvm /
sdb 8:16 0 100G 0 disk
└─vg_huge-lv_huge (dm-1) 253:1 0 100G 0 lvm /huge

[PTide]

What do you exactly mean? How can it be determined?

In the VM settings check if it has "Firmware" or "BIOS" in boot options.

Are there any differences between two disks? Have you tried to create and attach another disk to the VM?

[Rumato163]

It has BIOS feature in settings where you can choose boot device order.

These two disks: sda and sdb are almost the same.
sda - 30Gb fixed size vhdx
sdb - 100Gb fixed size vhdx
Both of them are connected to IDE controller.
I've tried to connect them to SCSI controller but ineffectually. sda was not visible

And -No I haven't tried to connect another one disk. Should I?

[PTide]

First please boor from Recovery Media, switch to a command line, run fdsik -l in order to check whether it's just a UI bug or the machine cannot detect the drive at all. If the drive is not shown in fdisk output then please try starting Recovery Media on another VM and see if the issue persists.

Thanks

[Rumato163]

fdisk -l shows all the disks:
sda1 - boot
sda2 - LVM root
sdb

[PTide]

Have you managed to reproduce the issue on another VM?

[Rumato163]

Not yet.
Because the condition for that task was:

If the drive is not shown in fdisk output

[Rumato163]

I have successfully reproduced that issue on another VM on HyperV with 2 different disks