I would like to know how to handle Dynamic Disk and LVM in Veeam.
#Question 1#
For example, if I have Veeam Agent on a physical machine, or I have a Hyper-V VM backup, I can use the VBR feature to do Instant VM Recovery to VMware environment.
How are Dynamic Disk and LVM restored in this case?
Is it possible to P2V or V2V to VMware environment without any restriction?
#Question 2#
I also have a question about Direct Restore to AWS EC2.
What are the limitations of restoring a VM with Dynamic Disk and LVM as AWS EC2?
In the case of LVM, I have confirmed that there are the following limitations. https://helpcenter.veeam.com/docs/agent ... tml?ver=40
Hello,
we did not forget about your question. You just put many questions into one thread So I'm still working on the answers (and it will take some more time)
Can you maybe tell us which configurations exactly you are asking for?
Question 1: Windows dynamic disks were converted to basic disks in my test.
I'm sure that it is possible to run into restrictions. I'm still investigating my Linux LVM setup. So I recommend to test.
Question 1: my issue was that I had a normal disk that changed from /dev/sdb to /dev/sdc. It had nothing to do with LVM. I recommend you use UUIDs in the fstab. Logical volumes are converted and work fine. You just need to fix the size of the physical disks (pvresize)
Question 2: dynamic disks and LVM is working fine with restore to EC2 as long as you meet all EC2 requirements. Additionally to the link I posted above, I can also recommend https://docs.aws.amazon.com/vm-import/l ... oting.html Same here: pvresize to inform LVM about the disk size change
Long story short:
1. Check EC2 import limitations
2. a quick test with instant recovery to VMware can show potential issues
3. with the information given in the initial post, nobody can guarantee that it works.
So I'm still working on the answers (and it will take some more time)