Hi
When migrating VMs from Hyper-V 2012 to Hyper-V 2016, using VEEAM Replication we ran into the issue that VEEAM Replication always creates a thin disk as target. Since thin disks cause performance with UNMAP on our storage we had to convert the thin disks to thick disks after migration, needing double the disk space on a CSV.
For VMware you can use VEEAM Powershell to force a thin target disk, but for Hyper-V this doesn't work. Before creating a test environment to test this, I thought I'd ask here
Well, we tried that but this has one big drawback: you need double diskspace to convert the thin disks to thick. With small VMs this is doable, but with big VMs (20TB and more) this is not desirable. Especially since you can't shrink the CSV afterwards, so you have to storage migrate the VM afterwards to a more fitting CSV.
