qemu-img convert VM.vmdk -O qcow2 VM.qcow2
Yes, I guess that's a preferrable method at least until we investigate what happens to disk during .vhd --> raw conversion. Did you use qemu-img for .vhd to raw as well? I'm also curious what will happen if you create a new VM in KVM with raw disks and try to backup the VM?I'm guessing this is the ideal method to start, and ended up being easier than what I was doing anyway.
That would be great, thanks!Anyway if your team becomes more interested in this, I wouldn't mind uploading the problematic .vhd image to an FTP
You can restore computer disks from volume-level backups and convert them to disks of the VMDK, VHD or VHDX format.
During disks restore, Veeam Agent for Linux creates standard virtual disks that can be used by VMware vSphere and Microsoft Hyper-V VMs.
• When you restore a disk in the VMDK format, Veeam Agent for Linux creates a pair of files that make up the VM virtual disk: a descriptor file and file with the virtual disk content.
• When you restore a disk in the VHD/VHDX format, Veeam Agent for Linux creates a file of the VHD or VHDX format.
You can save converted disks locally on any server added to the backup infrastructure or place disks on a datastore connected to an ESX(i) host (for VMDK disk format only). VMDK disks can be restored as thin provision and thick disks:
• Disks restored to a datastore are saved in the thin provisioned format.
• Disks restored to a server are saved in the thick format.
VHD/VHDX disks are always restored as dynamically expanding.
Veeam Agent for Linux supports batch disk restore. For example, if you choose to restore 2 computer disks, Veeam Agent for Linux will convert them to 2 virtual disks and store these disks in the specified location. <...>
Users browsing this forum: No registered users and 3 guests