Thanks for confirming!

GUI itself is not quite scalable for large deployments. Please consider using CLI.

You are always welcome

That's a great question. 19551 is the VSAN version that comes inside. VSAN cannot be updated without the other components of CVM. That's why once 19551 is installed, CVM should also be up-to-date. CVM, in turn, is not only about VSAN. That's why versioning is different: to emphasize other components...

You are always welcome
You can do everything on your own by altering config files.
GUI offers a safe and convenient way of doing that.

Welcome to StarWind Forum! This could work only if you have a witness on the third site or in the cloud. VSAN, as any active-active mirroring solution, has strict requirements to network redundancy (see https://www.starwindsoftware.com/system-requirements and https://www.starwindsoftware.com/best-pr...

No. GUI offers a more convenient way of doing it.

You are always welcome
P.s. Ask if you are eligible for NFR. That's a longer trial license.

Thanks!
There is an issue with connecting to the Proxmox host.
Try copying the files to the Hyper-V host > convert them locally > and assemble the VM. Or convert to OVF templates.

Could you please share the entire conversion log?

Thanks for your post. Converting the VM with multiple disks should be OK.
I have logged an internal testing request.

This webinar is like 8 years old
A lot of things has changed since then. You are always welcome to contact the account manager and check it here https://www.starwindsoftware.com/resour ... s_stories/.

Thanks for your notice!
V2V converter converts the format. The setting you are referring to is a failover-cluster-specific feature. That's why it might be off.

Could you please explain what you mean by highly available?
I was saying to use the host. You need to import it to the cluster, I believe, after the migration is over.

Thanks for sharing your experience! That's a very good point.