How do I safely get Hyper V VM's out of a failover cluster and onto a standalone hyper v server?
Posted on 2011-10-13
I am having problems, major problems, with a new ish windows cluster. It is only used for Hyper V to make our VM's highly available.
I have 3 nodes each identical in hardware (with the exception of 1 which i have added an additional network card, the plan is to to this to all 3).
The 3 nodes are connected by iSCSI to a Dell md3000i SAN. each node uses 2 NIC ports for iscsi traffic and i have 2 redundant switches in place.
My problems seem to have started after having added the 3rd node to the cluster and changed the quorum to node majority. prior to this it was node and disk majority.
Earlier today windows update must have rebooted 1 or more of the nodes (these should obviously not have been set to automatically update). Now we seem to be stuck in a sort of cycle where 1 or more of the nodes cannot reconnect to the iscsi disks.
It's fairly difficult to try and explain the symptoms.
What i want to do is get rid of the failover clustering role BUT I have to keep the VM's safe. My plan is to take clustering back to a lab environment and do more testing before putting production servers in there.
i can see 2 options,
1. move the VHD files off to another hyper v server outside the cluster.
2. somehow strip the cluster layer away from the nodes leaving them as normal hyper v servers.
I think i'd prefer option 2 as the hardware is better, to be honest though i'm happy to try any suggestions.
thanks in advance,