130 likes | 365 Vues
Virtualization with Windows Server 2008 Hyper-V. Do MUCH More with Less. Presented by: Jon Farley 2W Technologies. Overview. What is Virtualization? Specifically Microsoft Hyper-V Why Virtualize? Because we can! Benefits – Many Reliability, Flexibility, Performance, Lower Cost
E N D
Virtualization with Windows Server 2008 Hyper-V Do MUCH More with Less Presented by: Jon Farley 2W Technologies
Overview • What is Virtualization? • Specifically Microsoft Hyper-V • Why Virtualize? • Because we can! • Benefits – Many • Reliability, Flexibility, Performance, Lower Cost • Recommendations • Implementing Virtualization • Demonstration
What is Virtualization? • 2 Pieces – Hardware & Software • Hardware • Both AMD & Intel built-in virtualization technology • Included in recent Servers & most pc’s • Divides resources at the hardware-level • Keeps each virtual machine isolated from other vm’s • Software • Microsoft’s Virtualization is called “Hyper-V” • built into Windows 2008/Windows 7 • Enables a “Host” server to host 1 or more VM’s • Free version of Win 2008 core • “Windows 2008 Hyper-V Server” to just host VM’s • VM Ware • Invented the concept • Costs $ • Separate App, not part of the Operating System
What is Virtualization? (cont.) • Software (continued) • Hosts & Guests • Host would be full Win 2008 64-bit, or free Hyper-V • *Strongly recommend “R2” version of Win2008 • Guest VM’s could be nearly any operating system • Win 2000/2003/XP/Vista/2008/7, Linux, etc. • 1 Host Hyper-V Server can several VM’s • 2-4,5,6… VM’s but totally depends on workload of each • Be smart about it, distribute load over physical servers appropriately • Separate Disk-intensive VM’s on separate physical servers • Same with Processor or Network intensive VM’s • Hyper-V Manager – will demo later • Control & manage any HV hosts & all their VM’s • Can run from Win2008/R2* server, Win 7 pc, Win Vista*
Why Virtualize? • Because we can & it makes good sense • Hardware & Software now make it possible & affordable • Get more Bang for Your Buck • 1 Server can house several virtual servers • Domain controller, file server • Database server, V8/E9 • Terminal server to host clients • In the past, there was a 1-TO-1 ration between Hardware & Servers • Was very expensive to split up server functions, required hardware for each • Now just buy a couple extra Windows server licenses • Enterprise version of 2008 allows for 1 physical host & 4 Virtual servers • *About the cost of 3 individual 2008 Standards • Standard allows 1 Host & 1 Virtual
Benefits • What is #1 benefit? • HARDWARE INDEPENDENCE!! • 1 Crash away from dreaded “Blue Screen of Death” • If the hardware, drives or operating system get damaged… • Downtime! • Very costly to business. • In a virtual environment, can quickly port a VM to another physical server or even beefy PC! • Very little downtime • No longer tied to the hardware • Another layer between VM operating systems & hardware • “Removed” from hardware
Benefits (cont.) • Improved backups, disaster recovery • Entire virtual server can be backed up • w/backup commands capture backup image • Or shutdown the vm & copy the .vhd file to backup disk • Can easily restore entire VM if it got damaged • Can Make backup copies for Test or demo use • Before loading a new update, won’t damage production server • Very Fast Performance • No difference between virtual & physical server
Benefits (cont.) • Improved backups, disaster recovery • Entire virtual server can be backed up • w/backup commands capture backup image • Or shutdown the vm & copy the .vhd file to backup disk • Can easily restore entire VM if it got damaged • Can Make backup copies for Test or demo use • Before loading a new update, won’t damage production server
Benefits (cont.) • Next Step-System Center Virtual Machine Manager (SCVMM) • Setup a Redundant/Failover “farm” of 2 or more physical servers • Centrally control all Hyper-V host servers & all VM’s • Inexpensive license, maybe $500 per physical server*Very cheap for full server redundancy • Allows for “Live Migration” (R2 only) • Move a VM from one physical box to another with *Min downtime (2 mins. Or less)
Implementing Virtualization • One Server at a time • Start with one • Phase-out old servers, migrate to Virtual servers • Make any new server virtual from day 1 • P2V (Physical to Virtual) Conversions • Move an existing server from old hardware to VM • Retire Old, Slow, or Unstable hardware • Once virtualized • Can give same server more RAM, disk space • Will run much faster since on fast host server • Often much easier than reinstalling a entire server & all applications
Recommendations • Build Accordingly • You can overload any server, physical or virtual • Provide plenty of Memory & Disk space for all VM’s • Sum of all RAM for VM’s plus 2gb or more for HV Host • Have “Utility” disk partition for backups • VM’s on partition by themselves • Can then backup entire volume (to utility) & get an image of all VM’s • Dual Quad Core processors if 2 or more VM’s • Or more for large environments • Multiple Network cards on host • Spread network load/traffic over separate gb network connections
Demonstration… • Show our 2W virtual servers in action • Also, new 2008 “RemoteApp” • Much improved Terminal Services
Questions or Comments? Thanks for your time! Jon Farley Ph: 312-533-4033 x8045 Email: Jon@2WTech.com