Veeam Backup support issues with VME Bulk Migration Tool (qcow2-v2)

[Hinako]

My understanding of the root cause why virtual machines migrated from a VMware environment to a VME environment using the VME Standard Migration Tool
(Bulk Migration) in the Veeam Plug‑in beta version are not supported for Veeam backup is as follows.

Route Cause
Virtual machines migrated using the Bulk Migration Tool are created in the qcow2‑v2 file format.
Because of the limitations of qcow2‑v2—specifically, its inability to persist dirty bitmaps—backup operations fail.
Is it correct to understand that only virtual machines configured with qcow2‑v2 are not supported?

In HPE PCBE dHCI, virtual machines are deployed on vVols via the Alletra MP Plug‑in, so qcow2 is not used.
In addition, the latest Bulk Migration tool supports qcow2‑v3, so is it correct to understand that this issue does not apply in that case?

[Andreas Neufert]

It was just a matter of development stage for the beta.
The product was released already. Please find here the documentation: https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

[cody.ault]

The GA version does have logic to handle VMs migrated using the older version of the tool that used an older version of qcow2. For those VMs, we won't try to track changes. For VMs migrated with the newer version of the tool that use a newer version of qcow2 that supports checkpoints, it should work fine. The Alletra MP Plug-in storage uses a RAW format that sits on the lun-per-vdisk and should also be fine since we can create redirect the checkpoint for CBT to some other file-based storage.