Let's talk about the degree of automatization. Do you expect the software to automatically restore LV structure in case the VG is spread across many PV residing on different drives, or you just want the automatization to work with basic scenarios (like the on on the picture above)? If the former then do you expect it to work on a set of drives that differ from the original set by capacity or number of disks or both?I am the only one who expect from whole disk a whole disk???
That can happen if there is already a layout on the disk. If you choose a fresh new disk to restore to then you won't get such a result and will have to create LVs manually.However, by selecting "Current-System" > sda > restore whole disk from - generates the lvm and restores lv_root
That's correct, it can be seen from the restore session log that the bootloader wasn't restored to /sda. Could you please clarify once again how excatly did you perform the restore? Was it "backup to disk" or "disk from backup"? In both cases these should have appeared a "loader (sda)" entry in the "Restore" column, did you see that entry?After the restore has been completed, I tried to boot the system without success. Booting again from the Veeam.iso and trying to mount the lv_root and boot was successful. Looks to me that the bootloader is missing.
That can happen if there is already a layout on the disk. If you choose a fresh new disk to restore to then you won't get such a result and will have to create LVs manually.
Could you please clarify once again how exactly did you perform the restore? Was it "backup to disk" or "disk from backup"?
something is not right here...In other words, you've tried the following two cases:The disk was empty (new vmdk). My problem is that there are differences between "whole disk" restores:
selecting "In Backup" > sda > restore whole disk to :: does not restore lv_root.
selecting "Current-System" > sda > restore whole disk from :: generates the lvm and restores lv_root
1. Pick sda, choose "restore whole disk from ...", pick sda from the backup.
2. Pick sda2 and choose "create LVM physical volume". Enter VG name. Make sure that it has the same name as in the backup you're restoring from.
3. Pick free space inside the VG, choose to "restore volume from ...", pick root LV from the backup. Perform the same for the remaining free space and swap LV. Start restore.
about the degree of automatization.
"Restore whole disk from" is supposed to restore a bootloader as well...regarding the BootLoaderType error - our QA team saw that error before, however we did not manage to reproduce it. Does it happen every time? Could you please describe settings of the VM that you are trying to restore?But If I try to restore the bootloader I got the error "Unable to convert BootloaderType::type [-1080767520] to string.
Noted as a feature request.I would expect for a simple one harddisk LVM configuration (on most server and client installations for the system) that a "whole disk restore" should be a straight forward process" which will restore the data, partiontable and bootloader and be able to boot again, without the need of knowledge of LVM structure and creation. That should work with same disk size or larger.
Do you mean LV schrink? That option (and many others) is available in a command line interface via lvresize command.Nice addon would be to shrink...
Yes, that's a known bug.But If I try to restore the bootloader I got the error "Unable to convert BootloaderType::type [-1080767520] to string. Is that a known issue with the beta?
Users browsing this forum: No registered users and 1 guest