Implementing and Managing Microsoft ® Hyper-V 2.0

1. Implementing and Managing Microsoft®Hyper-V 2.0 Nicola Ferrini info@nicolaferrini.it Level 300 - Advanced

2. Who Am I ? • Trainer • TechnicalWriter • SystemsEngineer • Server & Application Virtualization Technology Specialist • Technet Speaker • Microsoft System Center Influencer • More on: • http://www.nicolaferrini.it/curriculum.shtml • http://www.windowserver.it/ChiSiamo/Staff/tabid/71/Default.aspx

3. Agenda • Evaluating and Planning for Virtualization • Configuring the Hyper-V Server Role • Creating and Configuring Virtual Hard Disks and Virtual Machines • Implementing High Availability for Server Virtualization • Integrating VMM with Hyper-V • Creating and Deploying Virtual Machines Using VMM 2008 R2 • Managing Virtual Machines Using Virtual Machine Manager 2008 • Configuring and Managing the VMM Library • Configuring User Roles and the VMM Self-Service Portal

4. Virtualization Modes Management Profile Virtualization Document redirection Offline files Presentation Virtualization Application Virtualization Desktop Virtualization

5. What Is Server Virtualization? Server virtualization enables multiple virtual machines to run on one physical host Benefits: • Server consolidation • Service or application isolation • Simplified server deployment and management • Increased service and application availability • Multiple operating systems can run on one consistent platform

6. What Is Hyper-V? Windows Kernel Provided by OS ISV/IHV/OEM Microsoft Hyper-V Microsoft / Citrix Parent Partition Child Partitions Applications Applications Applications VM Worker Processes Applications User Mode WMI Provider VM Services Non-Hypervisor Aware OS Supported Linux Distributions Windows Server 2008 Windows Server 2003, 2008 Kernel Mode VSP Windows Kernel Linux VSC IHV Drivers VSC Emulation VMBus VMBus VMBus Windows hypervisor Ring -1 “Designed for Windows” Server Hardware

7. Features of Hyper-V in Windows Server 2008 R2 Dynamic virtual machine storage Live Migration Improved VHD performance Enhanced processor support Enhanced processor support Enhanced networking support Hyper-V in Windows Server 2008 R2 Cluster shared volumes

8. Requirements and Limits for Virtual Machines and Hyper-V Host computer components Virtual machine components

9. Demonstration: How to manage Hyper-V In this demonstration, you will see how to manage and configure Hyper-V using Hyper-V Manager

10. Using and Configuring iSCSI Storage iSCSI Initiator iSCSI storage: • Uses the existing IP network • Is configured using the iSCSI initiator • Should use a dedicated NIC • Required for virtual machine failover clustering

11. Settings for Virtual Machines Virtual Machine Settings

12. Exporting and Importing Virtual Machines in Hyper-V Originating Computer Exported Virtual Machine Destination Computer Imported Virtual Machine

13. What Are Hyper-V Virtual Machine Snapshots? Snapshots: Snapshot files: • Virtual machine configuration .XML file • Are a point-in-time copy of a virtual machine • Do not affect the running state of a virtual machine • Save state files • Differencing disk (.AVHD)

14. Demonstration: Using Snapshots in Hyper-V R2 In this demonstration, you will learn how to: Take and manage a virtual machine snapshot Create a snapshot Revert to a previous snapshot Merge snapshots

15. Planning Hyper-V Hosts When planning Hyper-V hosts: • Simplify and standardize the host platform • Consider using the Server Core installation option • Automate and standardize administration of the virtual server environment by: • Standardizing the host and virtual server configuration • Implementing remote management solutions at the host server level • Implementing VMM

16. Guidelines for Designing Virtual Machines Guidelines: • Simplify and standardize the host platform • Plan virtual machines for specific server roles by: • Monitoring the servers before virtualization • Configuring each virtual machine with a hardware configuration that is similar to the hardware required on a physical server • Deploy Windows Server 2008 or Windows Server 2008 R2–based virtual machines whenever possible • Consider other options for ensuring physical server utilization

17. Designing Virtual Machines for SQL Server Guidelines: • Ensure that the Hyper-V integration components are installed • Plan virtual machine hardware settings to match physical server hardware • Use fixed-size disks and SCSI controllers for database and log file drives • To ensure adequate CPU capacity: • Remember virtual machines are limited to four processors • Do not over-commit CPU resources • Remember networking-intensive workloads require more CPU capacity

18. Designing Virtual Machines for Exchange Server When designing virtual machines for Exchange Server: • Use standard server sizing rules • Configure appropriate storage • Do not use virtual machine snapshots • Configure adequate CPU resources • Consider how to use Hyper-V and native Exchange Server high availability • Consider I/O requirements

19. Designing Virtual Machines for SharePoint When designing virtual machines for SharePoint: • Configure virtual machine hardware like physical server hardware • Do not take snapshots of virtual servers • Avoid over-committing the virtual CPUs • Consider deploying all of the servers in a server farm on a single physical server • Assign adequate memory • Use only Internet Protocol Version 4 (IPv4) • Choose the right storage implementation for the SharePoint server role

20. What Is a Failover Cluster?

21. Failover Cluster Functionality in Windows Server 2008 R2 • Clustered Shared Volumes • Live migration • Processor compatibility mode • Windows PowerShell cmdlets for failover clusters • Additional tests in cluster validation

22. Configuration Options for a Failover Cluster Quorum

23. How Does a Failover Cluster Work with Hyper-V Nodes? Shared Bus or iSCSI Connection A dedicated network connects the failover cluster nodes

24. Planning a Failover Clustering Strategy for Hyper-V 1 Identify the applications that require high availability Identify the application components that must be highly available 2 3 Identify the application characteristics 4 Identify the total capacity requirements 5 Create the Hyper-V design

25. Best Practices for Failover Clusters Running Hyper-V   • Use Windows Server 2008 R2 as the Hyper-V host • Plan for failover scenarios • Plan the network design for failover clustering • Plan the shared storage for failover clustering • Use the recommended failover cluster quorum mode • Deploy standardized Hyper-V hosts • Develop standard management practices

26. Implementing Hyper-V and Failover Clustering Install and configure Windows Server 2008 or Windows Server 2008 R2 1 2 Configure shared storage 3 Install the Hyper-V and Failover Clustering features 4 Validate the cluster configuration 5 Create the cluster 6 Create a virtual machine on one of the cluster nodes 7 Make the virtual machine highly available

27. Demonstration: Implementing Failover Clustering for Hyper-V • In this demonstration, you will see how to implement failover clustering for Hyper-V

28. Configuring Clustered Shared Volumes CSV benefits: • Fewer LUNs required • Better use of disk space • Virtual machine files are in a single logical location • No special hardware required • Increased resiliency To implement CSV: 1 Create and format volumes on shared storage 2 Add the disks to failover cluster storage 3 Add the storage to the CSV

29. What Is Live Migration?

30. Considerations for Implementing Live Migration • Verify basic requirements • Configure a dedicated network adapter for the private virtual network • Use similar host hardware • Verify network configuration • Manage Live Migrations

31. Demonstration: Implementing Live Migration • In this demonstration, you will see how to implement Live Migration

32. What Is VMM 2008 R2? VMM 2008 R2 provides centralized administration and management of your virtual environment VMM is used to: • Manage Hyper-V hosts • Manage virtual server hosts • Manage VMware hosts • Manage and deploy virtual machines • Perform physical-to-virtual (P2V) and virtual-to-virtual (V2V) conversions

33. Infrastructure Components of VMM 2008 R2 VMM Administrator Console VMM Server VMM Database VMM Library Hosts Host groups VMM Self-Service Portal

34. What’s New in VMM 2008 R2? What’s new: • Windows Server 2008 R2 Hyper-V Host Management • Enhanced Support for SAN Transfers • Enhanced Support for Shared Storage • Quick Storage Migration • Maintenance Mode for Hosts • Support for VMware Port Groups for Virtual Switches • Support for Virtual Machine Permissions Assigned in Hyper-V

35. Demonstration: Managing SCVMM 2008 R2 In this demonstration, you will learn how to manage SCVMM 2008 R2

36. What Is Windows PowerShell? Windows PowerShell is: • A scripting and command-line technology • Directly accessible through a command shell, msh.exe • Used by GUI tools Windows PowerShell features include: • Cmdlets • Aliases • Variables • Pipelining • Scripting support • Access to cmd.exe commands • Signed scripts

37. Using Windows PowerShell to Manage VMM The VMM command shell includes the standard PowerShell cmdlets, as well as a set of cmdlets specifically for VMM, such as: • Get-VMCheckPoint • Get-VMCheckpoint -MostRecent –vm "VM01" | Restore-VMCheckpoint • Get-Help Get-VMMServer

38. Types of Hosts That VMM 2008 R2 Supports • Windows Server based host in trusted domain • Windows Server based host in non-trusted domain • Windows Server based host in perimeter • ESX based host Supported Virtualization platforms: • Virtual Server 2005 R2 • Hyper-V • VMware ESX Server 3.0 or above • VMware ESX Server 3.5i • VMware VirtualCenter (VC) 2.5 (VMware Infrastructure 3 [VI3]) • VMware vSphere 4 (VI3 features only)

39. Demonstration: Adding Hosts to SCVMM • In this demonstration, you will learn how to add hosts to SCVMM 2008 R2

40. Supported Guest Operating System Platforms for Virtual Machines Server operating systems that the child partition supports: • Windows 2000 Server SP4 • Windows Server 2003 SP2 (x86 Edition or x64 Edition) • Windows Server 2003 R2 SP2 (x86 Edition or x64 Edition) • Windows Server 2008 (x86 Edition or x64 Edition) • Windows Server 2008 R2 • SUSE Linux Enterprise Server 10 with SP2 (x86 Edition or x64 Edition) • SUSE Linux Enterprise Server 10 with SP1 (x86 Edition or x64 Edition) • SUSE Linux Enterprise Server 10 with SP2 (x86 Edition or x64 Edition) • SUSE Linux Enterprise Server 11 (x86 Edition or x64 Edition) • Red Hat Enterprise Linux (RHEL) 5.2 and 5.3 (x86 Edition or x64 Edition) (Emulated devices only) Client operating systems supported in child partition: • Windows XP SP3 (x86 Edition or x64 Edition) • Windows Vista SP1 (x86 Edition or x64 Edition) • Windows 7 (x86 Edition or x64 Edition) Integration Servicesimproves integration between the physical computer and the virtual machine

41. Sources for Deploying New Virtual Machines

42. What Is Host Rating? Represents suitability of the physical machine to the host virtual machine Host rating: • Depends on: • CPU usage • Memory usage • Disk I/O • Network usage • Is a recommendation, not a mandatory condition • Calculation metric can be changed

43. What Is Virtual Machine Placement? Evaluation and selection of the most suitable host for the virtual machine Types: • Automatic placement • Intelligent placement Considerations: • Default path must be configured • Host compatibility must be checked

44. Demonstration: Creating and Placing a New Virtual Machine Using VMM 2008 R2 In this demonstration, you will learn how to use VMM to create a new virtual machine, place it on the host, and store it in a library

45. Demonstration: Deploying a New Virtual Machine from the VMM Library In this demonstration, you will learn how to deploy a virtual machine from the VMM library

46. What Is P2V Conversion? Converts an operating system that is running on physical hardware to an operating system running inside a virtual machine Considerations: • VHDs are made from disk images from source computer • New virtual machine has the same computer identity as the physical computer

47. Requirements for the Source and Destination Computers in the P2V Process Requirements for the source computer: Requirements for the destination computer: • RAM size • Volume size • ACPI BIOS • Cannot be in perimeter • Virtualization platform • RAM size • Cannot be in perimeter Considerations for the operating system: • NT 4.0 is not supported • Itanium versions are not supported • Windows Server 2003 Sp1 is not supported

48. Online and Offline P2V Conversions Online conversion uses VSS to convert the physical server to a virtual machine while the operating system and applications are running on the physical server Offline conversion uses Windows PE to convert the physical server to a virtual machine while the operating system and applications are not running on the source server

49. Usage Scenarios for P2V Conversion Scenarios: • Consolidating servers • Decommissioning of old hardware • Simplifying support for old operating systems Prioritizing Virtualization Candidates: • Underutilized computers that are not business critical • Computers with low utilization • Computers with higher utilization • The remaining underutilized computers

50. What Is V2V conversion? Converts existing VMware virtual machines to virtual machines running on Hyper-V Converting VMware-based virtual machines: • From ESX host, Library or File Share • Original VM is unaffected • .vmdk files are used as source to build .vhd