This quick blog post shows you how you can simply extend a Hyper-V R2 or Windows Server 2008 R2 Cluster Shared Volume without any downtime. First you expand your LUN in your OEM SAN management software. This is mostly of the time nothing special. But after that you have to expand the Cluster Shared Volume.
In your OEM SAN Management Software expand the size of the LUN or disk
Open the Microsoft Failover Cluster Manager and check the CSV coordinator for the disk or LUN you have expanded. The CSV coordinator is the disk owner in the cluster
Login to the CSV coordinator machine
If you are using the GUI version you can use the Disk Management under Storage in the Server Manager. You can now rescan for disks and then expand the Disk or LUN.
If you are using Hyper-V or Windows Server Core you can use diskpart
First start the cmd and open diskpart
now type list volume, to list all volumes
Use select volume IDNumber, the IDNumber is the number you could see with list volume in the previous step.
now you can type extend
with list volume you can see the results
In some environments sometimes if you need to expand a Cluster Shared volume it makes more sense to create a new one and move the Virtual Machines with Storage Migration but this cannot be done without downtime.
At the end of last year we had our Cisco UCS ordered and in your datacenter. In January we started the testing and made the Clusters ready for the production environment. In February we started the migration of our existing environment, mostly P2V and also some V2V migrations.
Here some interessting facts about our Cisco UCS and Hyper-V project.
We use 12 Cisco UCS Blades this is like 10 HE of rackspace
We migrated 45 Windows Servers and 47 Unix Servers in just one week
We replace 2 racks of server with a half rack of two Cisco UCS Bladecenters
We think we can replace 2-3 racks more with our two Bladecenters.
At the end of this year we think we could replace 4-5 racks with 1/2 rack
We still have a lot of physical and virtual server which will be needed to be migrated to the Bladecenter.
We will get even more out of our Blade Servers by activting Hyper-V Dynamic Memory as a new feature of Hyper-V R2 ServicePack 1
This migration had a lot of positive influence on other things in the datacenter.
we need now 4% less energie overall
we need now 6% less cooling overall
we need less space (1 and 1/2 racks at the moment)
now our system administrator travel 50% less to the datacenter, because of hardware defects or other administrative tasks.
We can deploy new servers in minutes instead of hours
I think all of this numbers (except the time we need to deploy new servers )will increase after the next migrations.
Now I started to write a series of blog posts about installing Microsoft Hyper-V R2 on the Cisco UCS system:
Microsoft Hyper-V and the Cisco UCS Bladecenter are a powerful team. The UCS Virtual Hardware takes alot of complexety from the hypervisor in your case Hyper-V. You don’t need NIC teaming and stuff like that. Thats is making it very easy to deploy Hyper-V Clusters. And with the Microsoft System Center Virtual Machine Manager you can save a lot of time in managing your clusters, hosts, virtual machine and also in P2V and V2V migrations. Since Microsoft SCVMM supports Windows Powershell you can also do a lot of scripting automation. And with the release of the new Version of SCVMM (System Center Virtual Machine Manager 2012) this will even get better for deploying new virtual machines, services and even public and private clouds.
We started with Microsoft Hyper-V R2 Servers before the release of Service Pack 1. We think we can even get a lot more out of your systems with the new Dynamic Memory feature for Hyper-V which comes in Service Pack 1.
At the end we think choosing the Cisco UCS, Microsoft Hyper-V and Microsoft System Center Virtual Machine Manager for our datacenter was the best choice we have made, in terms of costs and technology.
If you are using Microsoft Hyper-V with new Intel Sandy Bridge or Intel Westmere processors and our server has over 48GB of physical RAM you may get a performance decrease. Microsoft released a hotfix (KB2517329) for this problem.
This could also be a problem with a lot of Hyper-V installations on Cisco UCS, because the most of them will use more than 48GB of memory.
The performance decrease could show its self in the the following issues:
The CPU usage is high and the server responds slowly when you copy large files on the computer. For example, you copy a 10-GB file
The disk I/O performance of the virtual machines (VMs) is slow
Windows takes a long time to start
The hotfix is not include in Service Pack 1 for Hpyer-V R2 or Windows Server 2008 R2.
For more information about this you can check KB2517329
We use Microsoft Hyper-V Server 2008 R2 as Operating System for our Cisco Blade Notes. The Cisco UCS does need some special drivers which are not included in Hyper-V Server Image (Network and HBA). So I created a Hyper-V Server 2008 R2 ISO file which includes the Drivers from the Cisco UCS.
Now copy the extracted folder to the Hyper-V Core Server. In my case i copied in the C:\ root of the Core Server via the administrative network share. If you have easy physical access to the server, you could also use a USB stick or something like that.
Now connect to the Core Server and use the cmd.exe to navigate to the folder with the HP Support Pack
Run the “hpsum.exe” to start the HP Smart Update Manager
When the HP Smart Update Manager is started you can use it like on a Full Server installation of Windows Server 2008
You could also try to run the HP Smart Update Manager on another machine and use the remote connection feature.