Make running VM highly available in VMM 2012 R2
So I was helping a customer to migrate a VMware VM to their Hyper-V environment that is managed with System Center VMM, As I described in an earlier post I had some things that I did not like in the built-in v2v conversion that is part of the VMM.
In this migration I used Double-Take Move and this is a really nice software from Vision Solutions that allows you to migrate a running VM and will only get a few minutes downtime during the failover :-). The great thing is that the VM is replicated to the hyper-v host directly and you get a synthetic NIC and also a VHDx virtual disk.
There are though some small things that need to be considered and Double-Take does not do the whole part when used separately, when using it with Vision Solutions system center integration toolkit we can automate these things too, but for migrating just a few VM´s that is a bit of overkill. So what do we need to take care of,
- DT does not set VLAN on the nic for the migrated VM, that can be done during the replication in VMM when the newly provisioned VM appears there and set the right vm network and bandwidth etc.
- DT does not make the VM highly available during the migration, it can be deployed on the Clusterstorage volume though.
- DT does not remove VMware tools during the migration so that has to be cleaned up after.
- DT does not update/install the Hyper-V integration components.
So now to the main focus for this article, when the VM has been migrated to Hyper-V, how do I configure it to be highly available? When looking in the properties of the VM on VMM that option is greyed out
And trying to add it through the PowerShell cmdlets in VMM gives the following error message:
So the way to do it is with the Hyper-V and failover cluster cmdlets instead:
hyper-v\Get-VM SCACR2 -ComputerName HV02 | Add-VMToCluster -Cluster (Get-Cluster HVCL)
And then when refreshing the VM in VMM you can see that it is now highly available 🙂
The workaround option that is available in VMM to be able to make the VM highly available is to do a Live Storage migration to another CSV Volume/SMB share and in the wizard check the box for making it highly available but that involves file copying and goes painfully slower than the Add-VMToCluster on the running VM that already resides on a shared storage volume.
And this also (at least in my test environment) creates a copy cluster resource that has to be cleaned up manually cause the real one is running..