So what is guest cluster? A guest cluster is when you create cluster inside of virtual machines. In the past we’ve done that trough ISCSI or FC and lately with Shared VHDX in Windows Server 2012 R2. And like any other cluster you will want to monitor these clusters with SCOM but as they are just like any other cluster where is the catch? Continue reading “Notes from System Center Battlefield: Monitoring Guest Clusters with SCOM”
Imagine the following situation: You have two Windows Server 2012 R2 Hyper-V clusters – Cluster1 and Cluster2. Every cluster has two or more nodes. On Cluster1 you have two virtual machines VM1 and VM2. The virtual machines are in guest cluster and are using one or more Shared VHDX files. As you probably know virtual machines with shared vhdx files cannot be migrated with shared nothing live migration. Than how to move VM1 and VM2 from Cluster1 to Cluster 2? Here is a solution for you:
- Logon to VM2. Start Failover Cluster Console. Pause VM2 as node in the cluster and drain all roles.
- Shut down VM2.
- Logon to VM1. Shut down VM1.
- Remove cluster resources for VM1 and VM2 from Cluster1.
- Open Hyper-V console on the node of Cluster 1 where VM1 and VM2 are.
- From the VM settings of VM2 remove all shared VHDX disks. Apply.
- From the VM settings of VM1 remove the checkbox for shared VHDX on all drives where is checked. Apply
- From Hyper-V console move VM1 to one of the nodes of Cluster2.
- From Hyper-V console move VM2 to one of the nodes of Cluster2.
- Now VM1 and VM2 are on Cluster2.
- Open the Hyper-V console on the node of Cluster2 where VM2 is.
- Open VM settings for VM2. Attach all shared vhdx files as disks that you’ve removed in step 6 in the same order as before. Check the checkbox for shared VHDX on all of them. Apply
- Open VM settings for VM 1. Check the checkbox for shared VHDX for all disk that you’ve removed in step 7. Apply.
- Add VM1 and VM2 as cluster resources in Cluster2.
- Start VM1. Check if VM1 is healthy and all resources/roles are up in the Failover Cluster Console.
- Start VM2. Resume VM2 as node of the guest cluster. Migrate all roles and resources to make sure everything is ok.
These are all the steps you need. I hope they will help you.