Tuesday, 26 March 2013

Hyper-V 3.0 web resources


Thursday, 7 March 2013

Hyper-V 3.0 ReFS

I thought I would be clever and try out the new ReFS file system in Windows 2012. Did some reading and it sounds great. I also used Google to search for resources about using ReFS volumes in Hyper-V clusters, but little was found.

Lesson learn't...as always with M$ all the glistens isn't gold :( 


Hyper-V 3.0 hotfixes

When installing Hyper-v clusters in either Windows 2008r2 SP1 or Windows 2012, it's really important to keep up to date with all the hotfixes. Oddly enough you would think that Windows update would do this. But that's not always the case.

Here is a list of hotfixes from the Cluster team.

http://social.technet.microsoft.com/wiki/contents/articles/15577.list-of-failover-cluster-hotfixes-for-windows-server-2012.aspx
http://blogs.technet.com/b/yongrhee/archive/2011/05/22/list-of-failover-cluster-windows-server-2008-r2-sp1-hotfixes.aspx

Here is a list of hotfixes from the Hyper-V team.

http://social.technet.microsoft.com/wiki/contents/articles/15576.hyper-v-update-list-for-windows-server-2012.aspx

http://social.technet.microsoft.com/wiki/contents/articles/20885.hyper-v-update-list-for-windows-server-2012-r2.aspx

To see if you have a hotfix installed or not you can use this command. In this example I am searching for a hotfixed numbered 2813630 & 2796995

wmic qfe list full | find "2813630"
wmic qfe list full | find "2796995" - ODX hotfix
wmic qfe list full | find "2919355" - Windows 2012 R2 Update


If the return result is blank you don't have it installed.

To list all the hotfixes installed on the system use that command:

wmic qfe list full | find "KB"

Tuesday, 26 February 2013

Running the Hyper-V BPA in Windows 2008r2 core mode

To run the Hyper-V 2.0 BPA in Windows 2008r2 core mode you need to run the following commands from the command line of the core mode installation.


c:\ocsetup ServerManager-PSH-Cmdlets /norestart

c:\ocsetup BestPractices-PSH-Cmdlets /norestart



Start PowerShell


C:\PowerShell

PS C:\import-module ServerManager

PS C:\import-module BestPractices

PS C:\Invoke-BpaModel Microsoft/Windows/Hyper-V

PS C:\Get-BPAResult Microsoft/Windows/Hyper-v



If you want to export the results into a HTML page as a table, use this command instead

Get-BpaResult -BestPracticesModelId Microsoft/Windows/Hyper-V | Where-Object {$_.Severity -eq "Error" -or $_.Severity -eq “Warning” } | ConvertTo-Html -Property Severity,Category,Title,Problem,Impact,Resolution,Help -Title "BPA Report for Hyper-V" -Body "BPA Report for Hyper-V" –Head "" | Out-File "C:\bpa.html"

Friday, 11 January 2013

Slow storage vMotion from VMFS 3 to VMFS 5

I was moving a customer from vSphere 4.1 to 5.1. I have read that it's best to create a new datastore with VMFS 5 and migrate VMs over. The new hosts could see both new and old datastores.
I initiated a Storage vMotion to move a VM from the VMFS 3 to VMFS 5 datastore but it was taking ages. The performance charts where shows approx 17 MB/s. I rechecked my configuration and all was good. I decided to move a VM from a VMFS 5 datastore to another VMFS 5 datastore and this time the throughput was over 117 MB/s

Turns out that because the VMFS3 datastores have a 2MB block size and the VMFS 5 datastores are automatically created with a 1MB block size this slows things right down.

http://www.yellow-bricks.com/2011/02/24/storage-vmotion-performance-difference/ 

So allow plenty of time and be patient when migrating from VMFS 3 datastores :)