Veeam Moov Beta Feedback

[SysPxrzival]

Hello everyone!

Today i stumbled across VEEAM Moov as a tool to help migrating workloads from a vSphere environment onto a KVM based one and i wanted to provide some feedback. We use Morpheus (Enterprise) as the target environment and a physical Veeam B&R Server running version 13.0.2.29

I installed the VM, configured our Backup-Server and deployed a helper.

I noticed that when deploying the helper, Veeam Moov expects Morpheus to report back about the state of the helper-vm. By default, the helper-vm is configured to install the Morpheus Agent, which stalls the deployment in the fInalization stage for a long time which leads to the deployment step timing out and failing. I was able to work around this issue with unchecking the "Install agent?" checkbox within the virtual image of the helper vm. I dont know if the Morpheus Agent is necessary for the helper to work properly. This also might only be the case because we selected to do the agent installation with cloud-init and not via the qemu-guest-agent.

So far so good. Next step was to do the preflight-inspector:

Running the preflight also has some bugs. The inspection wont detect all backed up vms. We have several hundred vms within our repo but the inspector is only able to find 68 of them. Also, the disk size will get misreported for most of the vms. I noticed that it will sometimes report the size of one vm within a separate backup job for all of the vms within this job. So the size reporting can differ when running the preflight-inspect multiple times.

Analyzing the vms disks about drivers etc. generally fails and it wont detect anything.

Continuing onto the actual restore task:

I took a precreated backup job with three vms, which luckily got detected within the preflight, and created a migration job for them. Defining all relevant information per VM was good, but when starting the migration job as a cold or hot migration, the selected vms get skipped immediately without further information on why.


So the tool seems promising, but because of the bugs its technically unusable at this time. I hope this feedback helps resolving these issues.

Thanks for the attention on this topic.

[david.domask]

Hi Maximillian,

I assume you're referring to this tool, correct? https://community.veeam.com/blogs-and-p ... ials-13714

This is not an officially supported product, it's a tool created by a community member. I strongly advise leave your feedback on the Community Forums where the creator will see the feedback.

I will be locking this topic as it's not about an official Veeam Product, but please do share your feedback on the Community Forums with the creator. Thanks!