First published on TechNet on Mar 17, 2012
NOTE: the focus here is on server virtualization only and does not include aspects for desktop/ VDI or application virtualization (such as RemoteFX or App-V ) . Nor does this discussion address all aspects of a Private Cloud solution (more on Private Cloud details can be found here: http://www.microsoft.com/en-us/server-cloud/private-cloud/overview.aspx )
High Level Design Steps for a Hyper-V Deployment
Benchmark your dev/test/prod server fleet and establish your candidates for virtualization
We offer a free tool kit that can inventory an environment and produce very detailed reports and information to help with this ( the MAP is a very useful tool beyond just virtualization efforts , too
You may have your own tool(s) or may already have an established list of virtualization candidates
Determine a vailability requirements of the applications/workloads/VMs
Do the service levels of the applications/workloads allow for routine maintenance of the system?
A departmental application that is typically used during business hours only
A re there requirements for the app to sustain high levels of availability?
Mission-critical line-of-business application that is used 24x7
Consider the deployment location/ environment where the VM guests will be hosted
Branch office – often a single- node host deployed on fault-tolerant server hardware
HA Branch Office – often a two-node Failover Cluster deployed on fault-tolerant server hardware
Centralized Data Center – often one or more multi-node Failover Cluster ‘farm s ’
Determine the desired VM Guest ‘hardware’ profile (s) – vProc, vRAM, VHD (s) , vNIC(s)
One idea is to create typical use-case profiles such that the number of VMs per physical host can be easily predicted/budgeted
Low Utilization VM – 1 proc; 768 MB RAM; 20 GB C:\
Standard Utilization VM – 1 proc; 1024 GB RAM; 40 GB C:\
High Utilization VM – 2 proc; 2048 GB RAM; 60 GB C:\
Another idea is to spec each VM based on detailed measurements/requirements for each particular workload.
This can provide more optimal use of physical host server resources but can be more difficult to accomplish due to variations of server workloads and additional time to benchmark/perfmon each application
Application XYZ measured out for 1GB RAM and two Procs
Application ABC measured out at 768 MB RAM and one Proc
SCOM/SCVMM and Dynamic Memory features can help facilitate this effort more easily
Determine the number of planned VM Guests and consider future capacity needs
Determine the OS for the VM Hosts
Microsoft Hyper-V Server 2008 R2 SP1
F ree download
C ommand-line only interface
Hyper-V Role only
http://www.microsoft.com / en-us/server-cloud/hyper-v-server/default.aspx
Microsoft Windows Server 2008 R2 SP1 CORE install + Hyper-V Role
Full feature for-cost OS
C ommand-line only interface
Hyper-V Role (additional Roles available/supported)
Microsoft Windows Server 2008 R2 SP1 GUI install + Hyper-V Role
Full feature for-cost OS
Full GUI ‘typical’ Windows interface
Hyper-V Role (additional Roles available/supported)
Compare features and limit ations of the free/ Standard/Enterprise/Datacenter versions of Hyper-V
A few pro/cons for CORE vs GUI OS versions
CORE – pro
Fewer patches than GUI = fewer reboots due to maintenance
Smaller attack surface than GUI
Fewer ‘casual’ logons/ administration due to lack of typical tools/consoles available on the GUI versions of the OS
CORE – con
Separate/additional build to maintain from GUI version of OS
Admin skillset for managing a command-line OS is not as prevalent as GUI versions of the OS
Some 3 rd party apps/agents/tools have requirements for some of the GUI elements that CORE lacks
Determine the VM host storage architecture/model
Single node host
Direct-attached storage (DAS) - predominantly SAS but becoming SSD
Two-node Failover Cluster
D AS – predominantly SAS
SAN - predominantly iSCSI or fibre channel
Multi-node Failover Cluster ‘farm’
SAN – predominantly iSCSI or fibre channel
Determine the storage architecture details for the VM host (s)
RAID requirements
Controller redundancy requirements
Controller cache requirements
Determine the hardware requirements of the VM Host servers
CPU(s)
RAM
Local storage
NIX
SAN connectivity
Out of band mgmt of the host server(s)
Co nsider the additional overhead of one or more Cluster Failover events and the additional l oad from the VM guests wh en they are migrated onto the remaining node(s)
Finally, a few great resources for some specific Hyper-V details:
W2k8 R2 Performance Tuning Whitepaper (incl udes a Hyper-V section but it ’ s all excellent information :( http://msdn.microsoft.com/en-us/library/windows/hardware/gg463392.aspx
Hyper-V Clustering Survival Guide : http://social.technet.microsoft.com/wiki/contents/articles/239.aspx
Here's a fun site created when Hyper-V first released in WS 2008
http://www.microsoft.com/canada/windowsserver2008/serverunleashe d /default.html
Some cool videos can be accessed by clicking on the "Meet IT 24 - 7" box
My personal fave is “T he Command Line”
Hopefully, the information presented here provides some food for thought regarding your Hyper-V deployments.
Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.