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?
-
Hinako
- Lurker
- Posts: 1
- Liked: never
- Joined: Apr 23, 2026 4:20 am
- Full Name: Hinako Yoshida
- Contact:
-
Andreas Neufert
- VP, Product Management
- Posts: 7378
- Liked: 1590 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Veeam Backup support issues with VME Bulk Migration Tool (qcow2-v2)
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
The product was released already. Please find here the documentation: https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
Who is online
Users browsing this forum: No registered users and 1 guest