Previously I’ve blogged here, here and here about SCVMM and SCOM maintenance mode integration. In the past if you put Hyper-V hosts in maintenance mode in SCVMM the corresponding SCVMM object for the host is also put in maintenance mode. The problem with this scenario is that you can get some alerts if you patch the hosts automatically or bring them completely down for other maintenance tasks. Now with System Center 2012 R2 this is no longer the case. If you put the hyper-v hosts in SCVMM in maintenance mode:
The computer object of the host is put in maintenance mode in SCOM:
Now you can perform maintenance task on host without getting noisy alerts and we are closer to better automation.
I would like to thanks the VMM product group for listening on my feedback and for those who voted for this feature change.
If you are still on Windows Server 2012 Hyper-V and not migrated to R2 do not worry Microsoft hasn’t forgot you. The Windows Server 2012 Hyper-V MP received small update to fix some bugs. You can download the new version here.
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.
No detailed explanation is needed for these posters. Very useful way to study or explain a technology. Download them from here.
The Hyper-V MP provides good monitoring but certainly that MP can be extended to provide more advanced monitoring. For Hyper-V 2008 R2 MP some Microsoft employees extended that MP and provided this extension MP at codeplex site. Now they are providing us with similar extension MP for Hyper-V 2012 MP.
New features in this release:
VMs Integration Services Version monitor
Hyper-V Replica Health Monitoring Dashboard and States
SMB Shares I/O latency monitor
Included features from previous release
Hyper-V Hypervisor Logical processor monitoring
Hyper-V Hypervisor Virtual processor monitoring
Hyper-V Dynamic Memory monitoring
Hyper-V Virtual Networks monitoring
NUMA remote pages monitoring
SLAT enabled processor detection
Hyper-V VHDs monitoring
Physical and Logical Disk monitoring
Host Available Memory monitoring
Stopped and Failed VMs monitoring
Failed Live Migrations monitoring
Keep in mind that the management pack is with beta status. You can download it from codeplex site.