Hypervisor Migration - vSZ-E

[khakipants]

We are migrating from VMware to Hyper-V and I need to move our vSZ-E VM. I found this article: https://support.ruckuswireless.com/articles/000014314
I understand that migrating the VM with Veeam or similar migration tools is not supported. I need to start with a new Hyper-V appliance. My question is if it is supported to take a cluster config backup from the VMware appliance and restore it to the Hyper-V VM. The article above seems ambiguous to me about this. I found the follow post about a similar migration, but there wasn't any update on it about the success of this operation.
https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Smartzone-Migration-from-Hyp...

If anyone has experience with such a hypervisor migration, it would be most helpful.

[Stackademic]

I just attempted this blindly, I created a Hyper-V VM with a VHD of the same firmware version as my existing ESX VM. I backed up the ESX VM and then imported the backup to my Hyper-V VM but it seems to be putting it in a Crash Mode. I put in a ticket as well but was hoping someone might have followed up with you directly in the meantime?

[khakipants]

I did get a reply from support. They assured me that a configuration backup and restore is supported when going from the VMware appliance to Hyper-V. The article 14314 is just saying you need to start with a fresh VM appliance. Backup and restore should be supported as long as the platform is the same (VSZ-e to VSZ-e), the version is the same (6.1.2 LT-GD Patch 5 on both appliances), and the specs are the same (disk size, core count, memory amount). 

I am very interested in your Crash Mode issue. I will be doing my migration very soon. In this case, it should be pretty easy to fail back to the old controller if it doesn't go well. However, I do need a migration solution that works. Please keep us posted. 🙂

[Stackademic]

I got ahold of support and they couldn't give me a reason why it was failing. We did find that if I created a new cluster on the Hyper-V guest and just restore the configuration for the vsz itself and not the cluster it seems to work fine. Just as a heads up you will need to reach out to support for a temp license so you can RMA your current serial to the new serial for licensing. If you're ok with downtime you can just contact them for an RMA instead.

[khakipants]

Thank you for the update. This information is very helpful. I will attempt to get a temp license as well as attempt the cluster restore first, before trying the configuration restore. I'll post back here once complete to update anyone else who tries this.