1 / 44

Virtualization Scenarios for Business Critical Applications

Required Slide. VIR314. SESSION CODE: . Virtualization Scenarios for Business Critical Applications. Allen Stewart Principal Group Program Manager Server and Cloud Division Microsoft Corporation. Agenda. Why Microsoft Virtualization for Microsoft Server Applications?

maddox
Download Presentation

Virtualization Scenarios for Business Critical Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Required Slide VIR314 SESSION CODE: Virtualization Scenarios for Business Critical Applications Allen Stewart Principal Group Program Manager Server and Cloud Division Microsoft Corporation

  2. Agenda • Why Microsoft Virtualization for Microsoft Server Applications? • SQL Server Virtualization Scenarios • Consolidation, BI and HA Scenarios • Scalability Tests, Best Practices, Sizing Guidelines • SharePoint Virtualization Best Practices • Exchange Virtualization Best Practices • Links to Reference Material

  3. Microsoft Virtualization: The Best Choice for Microsoft Server Applications Complete Management Solution Microsoft Server Applications Built for Windows Low Cost Complete Solution *A comparable solution can cost up to six times more† *Built-in Virtualization with One-stop Support *Deep Application Knowledge *Large Partner Ecosystem *Lower Ongoing Costs *Physical & Virtual Management Increased Deployment Options *Cross Platform and Hypervisor Support Virtualization-friendly Licensing *Only available with Microsoft Virtualization †Based on a comparison of Microsoft® System Center Server Management Suite Datacenter with VMware® vSphere Enterprise Plus with VMware vCenter Server.. Assumes a five host configuration, 2 processors on each host, 2 years support costs for both products, and no operating system costs included.. The Microsoft solution can use either the free Microsoft Hyper-V Server 2008 R2 hypervisor or an existing Windows Server 2008 R2 hypervisor.  Based on Microsoft estimated retail prices and published VMware prices available at https://www.vmware.com/vmwarestore as of 08/04/2009 for purchases in the United States. Actual reseller prices may vary.

  4. Why Hyper-V for Business Critical Workloads • Better Flexibility • Live Migration. Moves running VMs between compatible physical hosts for performance, hardware maintenance, operating system maintenance, and power optimization without any disruption or perceived loss of service using a memory-to-memory operation using processors from the same manufacturer and family. • Hot add and removal of storage. Supports the addition or removal of VHDs or pass-through disks connected to the VMs virtual SCSI controllers while a VM is running. • Processor compatibility mode for Live Migration. Enables Live Migration across different CPU versions within the same manufacturer and processor family.

  5. Why Hyper-V for Business Critical Workloads • Greater Scalability • Scalability to 64 logical processors. Hyper-V scales up to 64 logical processors on the physical system and up to four virtual processors for each VM. • Server core parking. Places processor cores into a park/sleep mode when not in use. This enables the processor to consume less power without affecting system performance. • Increased Performance • Second Level Address Translation (SLAT). The Hyper-V SLAT feature takes advantage of this advanced processor technology to further improve VM performance and to reduce the non productive processing overhead on the hypervisor. • Virtual Machine Queue (VMQ) support. Enables physical computer network interface cards (NICs) to use direct memory access (DMA) for VM memory, increasing I/O performance.

  6. Dynamic Memory • Hot add and remove of memory As a virtual machine needs memory – its needs are evaluated against the needs of other virtual machines in the system, and it is given memory accordingly. • DM does not overcommit resource • DM treats memory like how we treat processor • Dynamically schedulable resource

  7. How does DM work • Adding Memory • Memory added to virtual machine in enlightened fashion • No hardware emulation • Integration with MM in the guest OS • Light Weight • Removing Memory • Ballooning

  8. Memory columns Dynamic Memory UI Memory Settings Memory Available value can be negative, indicating VM is under memory pressure and guest OS is paging

  9. Virtualization Deployment Scenarios for Microsoft SQL Server

  10. The benefits of using Hyper-V with SQL Server include: • Close to native performance with minimal additional overhead. • Simplified SQL Server database workload consolidation for Online Transaction Processing (OLTP) workloads and Analysis Services workloads. • Deployment flexibility using core technologies such as Live Migration, virtual disk hot add and removal, in addition to flexible network configuration and optimization. • SysPrep support. Enables the creation of standardized Windows deployment images with SQL Server preinstalled.

  11. SQL Server Consolidation • Currently a variety of consolidation strategies exist and are utilized. • Typically, as isolation goes up, density goes down and operation cost goes up. Higher Density, Lower Costs Higher Isolation, Higher Costs IT Managed Environment Virtual Machines Databases Instances Schemas MyServer Sales_1 Consolidate_1 Marketing_1 Online_Sales DB_1 ERP_10 DB_2 DB_3 ERP_10 Microsoft Confidential

  12. Consolidation Considerations

  13. Virtual Memory & Second-Level Translation • With Virtualization an additional level of mapping is required • SLAT improves VM performance by reducing the hypervisor overhead from upwards of 10 percent down to 2 percent, and by reducing memory overhead. This improves the scalability significantly because it enables more VMs to run concurrently on a single host server. The Virtual / Process view The Physical / real view • Physical Memory Pages Virtual Machine 1 Virtual Machine 3 Virtual Machine 1 Hyper Visor Operating System

  14. SQL Server Consolidation Scalability • Configuration: • OS: Microsoft® Windows Server® 2008 R2 Hyper-V™ • Hardware: • HP DL585 (16 core) with SLAT • HP EVA 8000 storage • Virtual Machines: 4 virtual processors and 7 GB RAM per virtual machine; Fixed size VHD • Results: • Increased throughput with consolidation • Nearlinear scale in throughput with no CPU over-commit • Improved performance with Windows Server 2008 R2 and SLAT processor architecture ) Throughput (Batch requests/sec) % CPU Almost Linear Scale No CPU over-commit CPU over-commit Heavy Load Moderate Load Low Load Relative Throughput for Windows Server 2008

  15. Virtualization for SQL Server Business Intelligence • Scenario Description: • Business Intelligence (BI) components with lower resource requirements such as Data Mart (DM), OLAP Cube, Reporting Servers are good candidates for scale out and ideal for virtualization • Operational Data Store (ODS), Data Warehouse (DW), SQL Server® Integration Services could be physical or virtual depending on scale up requirements • If virtual, put SSIS and Data Warehouse on the same Virtual Machine (VM) • Virtualization Benefits: • Increase agility by rapidly provisioning and scaling-out BI components on demand • Reduce the number of physical servers, save on power and space VM Legacy External ERP Web Data Mart & OLAP Cube Reporting Server SQL Server® Integration Services (SSIS) Data Warehouse (DW) Operational Data Store Data Mart & OLAP Cube Reporting Server 2 1 • Click Here For More Information

  16. Remote Site Consolidation with DB Mirroring • Scenario Description: • Help protect from data loss with SQL Server® Database Mirroring. Automatically, failover from primary to standby using witness. • Consolidate mirrored database servers on standby site with virtualization • Use mirrored databases with database snapshots for reporting • Ensure there is enough CPU capacity at the standby site to provide acceptable SLA upon failover VM SQL Server Database Mirroring 1 Reporting Server (DB Snapshot) 2 • Virtualization Benefits: • Better server utilization on standby site due to consolidation • Cost effective disaster recovery solution without using costly specialized hardware • Management efficiency based on SQL Server and System Center management tools 3 2 SQL Server Database Mirroring • Click Here For More Information

  17. SQL Server with Live Migration • Scenario Description: • Manage high availability with multipathing and live migration for planned downtime situations, such as hardware and software maintenance • Failover individual virtual machines (VMs) to other hosts within a cluster by using Cluster Shared Volume (in Windows Server® 2008 R2) • Use Microsoft ® System Center Virtual Machine Manager for migrations. System Center VMM can perform host compatibility checks before migrations and manage multiple Live Migrations with queues. • Nodes in cluster can be active-active • Ensure there is enough CPU capacity for the failover nodes in cluster VM Live Migration 1 2 1 2 • Virtualization Benefits: • No loss of service during failover with live migration. Migration is completely transparent to the user • Improve availabilitywith less complexity • Better server utilization due to consolidation • Easier set up and management through System Center VMM Host cluster Shared Storage iSCSI, SAS, Fibre • Click Here For More Information

  18. Performance & Resource Optimization

  19. PRO Pack Technologies Virtual Machine Manager PRO Packs For complete list, visit http://www.microsoft.com/systemcenter/virtualmachinemanager/en/us/pro-partners.aspx

  20. Hyper-V Configuration Guidelines • New SP1 behavior to better protect the parent partition from rampaging virtual machines • New registry key in place • Allows you to reserve static memory for the parent partition • May result in less memory being available for VMs • Hyper-V Root Configuration • Plan for 1GB+ memory reserve for the management OS in the root partition • Plan for one dedicated NIC for management purposes • Plan (ideally) for one dedicated NIC for live migration and CSV • Separate LUNs/Arrays for management OS, guest OS VHDs and VM storage • Management OS and VHD LUNs should employ RAID to provide data protection and performance • Challenge for blades with 2 physical disks • Hyper-V Guest Configuration • Fixed-sized VHDs for Virtual OS • Need to account for page file consumption in addition to OS requirementsOS VHD Size (minimum 15GB) + VM Memory Size = Minimum VHD size • Account for space needed by additional files by VM • Example for SQL: OS VHD Size + (VM Memory Size) + Data Files + Log Files

  21. I/O and disk latency for dedicated pass-through disks versus VHDs

  22. SQL Server Best Practices • Guest virtual machines are limited to 4 CPU cores • Best performance if VMs are not over-committed for CPU • Maintain 8 virtual CPU to core ratio • Test Network intensive applications for acceptable SLAs • Use multi-pathing on host or within the VM to ensure maximum throughput and high availability for VM workloads • Utilize either pass-through disk or fixed-size VHD for guest virtual machines • Avoid using emulated devices. Instead, ensure integration components are installed and synthetic devices are being used.

  23. Virtualization Deployment Scenarios for Microsoft Office SharePoint Server

  24. What is a SharePoint Farm? What is a SharePoint® Farm? A collection of one or more SharePoint Servers and SQL Servers® providing a set of basic SharePoint services bound together by a single configuration database in SQL Server • Key Components: • Web Front End (WFE) Servers: • Windows® SharePoint Services • Web Application Service • Application Servers: • Office SharePoint Server Search Service (Index or Query) • Document Conversion Launcher Service • Document Conversion Load Balancer Service • Excel Calculation Services • SQL Server

  25. SharePoint Roles & Virtualization Considerations

  26. Production Farm – Physical & Virtual Mix VM • Scenario Description: • Optimized scenario for high-end production is mixed physical and virtual • Index and database roles on dedicated physical servers to provide very high scalability • Virtual web, query, and application roles • All servers managed by System Center Suite DEV TEST • Virtualization Benefits: • Unified management: physical and virtual • Dynamic data center: scale dynamically and on-demand provisioning Failover Server PRODUCTION Index Shared Storage iSCSI, SAS, Fibre • Click Here for More Information

  27. Partner Evidence: SharePoint Virtualization DESCRIPTION • Deployment with mix of physical & virtual servers • Web, Query and Application roles are deployed virtual; database role is deployed physical • Maintains resource optimization with PRO RESULTS • Average response time of under 3-5 secondswith1% concurrency witha heavy user load profile ofover 300K user capacity • VIRTUAL MACHINE SPECIFICATIONS • 1 Index server dedicated for crawling: 4 CPUs, 6 GB RAM per VM • 10 Web Front End & Query servers: 4 CPUs, 4 GB RAM per VM • 2 Application servers: 2 CPUs, 2 GB RAM per VM • 2 Domain controllers: 2 CPUs, 2 GB RAM per VM Source: EMC Virtual Architecture for Microsoft Office SharePoint Server 2007 Enabled by Hyper-V (whitepaper) Click here for more information

  28. SharePoint Virtualization Best Practices

  29. Virtualization Deployment Scenarios for Microsoft Exchange Server

  30. Deployment Recommendations • Exchange application is not ‘virtualization aware’ • Core Exchange Design Principles Still Apply • Design for Performance, Reliability and Capacity • Design for Usage Profiles (CAS/MBX) • Design for Message Profiles (Hub/Edge) • Virtualization Design Principles Now Apply • Design for Performance, Reliability and Capacity • Virtual machines should be sized specific to the Exchange role (EDGE, HUB, CAS, MBX, multi-role) • Hosts should be sized to accommodate the guests that they will support

  31. Exchange 2010 Sizing Guidance 8 cores CAS / HUB Multi-Role Server 16 cores 24 cores

  32. Mailbox Server Guidelines Database Cache requirements are the same for physical and virtual deployments Virtual Processor ≠ Logical Processor Hypervisor and the Virtualization Stack consume CPU Reduce recommended MBX count by ~10%

  33. Mailbox Storage Configuration • Virtual SCSI (passthrough or fixed disk) • Recommended configuration for database and log volumes • iSCSI • Standard best practice for iSCSI connected storage apply (dedicated NIC, jumbo frames, offload, etc.) • iSCSI initiator in the guest is supported but need to account for reduced performance

  34. Exchange 2010 High Availability • Database Availability Group (DAG) • A group of up to 16 Exchange Server 2010 Mailbox servers that provide automatic database-level recovery • Uses continuous log replication and a subset of Windows Failover Clustering technologies • Can extend across multiple datacenters/AD sites • Benefits of Exchange Native Data Protection • Protection from database, server or network failure • Automatic failover protection and manual switchover control is provided at the mailbox database level instead of at the server level. • Support for up to 16 copies, support for lag copies

  35. Host Based Failover Clustering • Host Based Failover Clustering HA • Using Host Based Failover Clustering and automatically failing VMs to an alternate cluster node in the event of a critical hardware issue (virtualization platform independent) • What you need to be aware of: • Not an Exchange Aware Solution • Only protects against server hardware/network failure • No HA in the event of storage failure / data corruption • Trend is larger mailboxes = larger database sizes = longer time to recover from data loss = DAG • Not supported for MBX VMs that are members of a DAG

  36. Live Migration and Exchange 2010 • Physical Computer Maintenance • Operating System/Application Updates • Hardware Maintenance • Rebalancing Workloads • Dynamic Redistribution of VM’s to optimize workload on physical hardware • Green IT • ‘Off Peak’ Virtual Machine Consolidation

  37. Supportability Quick ReferenceExchange 2010 • Supported • Root: Hyper-V or any virtualization platform in SVVP • Guest: • Exchange 2010 • Windows 2008 SP2 or R2 • Mailbox, Client Access, Hub Transport, Edge roles • Meets basic Exchange system requirements • Storage is fixed VHD, SCSI pass through, or iSCSI • Not Supported • Combination of Exchange Mailbox HA (i.e. Mailbox servers in a DAG) and any host/hypervisor-based clustering or migration technologies (e.g. Microsoft Live Migration, VMware V-Motion, etc.) • Snapshots, differencing/delta disks • Unified Messaging role • Virtual/logical processor ratio greater than 2:1 • Applications running in root partition (excluding AV)

  38. Partner Evidence: Exchange Virtualization • HP recommended configurations for Exchange 2010 virtualization using Hyper-V R2 • Sizing for 20,000 users, 512 MB mailboxes • All roles virtualized and Live Migration for MBX servers • Hardware: HP ProLiant BL460c G6 (BL460c G6) server blade and HP StorageWorks 8400 Enterprise Virtual Array (EVA8400) storage systems http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA1-2127ENW.pdf • Sizing for 5,000 users, 256 MB mailboxes • All roles virtualized and Live Migration for MBX servers • Hardware: HP ProLiant BL460c G6 (BL460c G6) server blades and HP LeftHand P4500 (P4500) storage systems http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA1-9895ENW.pdf

  39. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Track Resources • Virtualization @ Microsoft: http://www.microsoft.com/virtualization • Hyper-V on TechNet: http://technet.microsoft.com/library/cc753637(WS.10).aspx • Virtualization Team Blog: http://blogs.technet.com/b/virtualization/ • Virtual PC Guy: http://blogs.msdn.com/b/virtual_pc_guy

  40. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet • http://microsoft.com/msdn

  41. Required Slide Speakers, please list the Breakout Sessions, Interactive Sessions, Labs and Demo Stations that are related to your session. Related Content • Breakout Sessions: VIR402- Virtualization FAQ, Tips, and Tricks • Interactive Sessions: VIR09-INT – Virtualization Round Table Discussion • Hands-on Labs: VIR04-HOL – Config and Managing Windows Server 2008 R2 Hyper-V • VIR07-HOL – Introduction to Windows Server 2008 R2 Hyper-V • Product Demo Stations: TLC-35 – Server Virtualization

  42. Required Slide Complete an evaluation on CommNet and enter to win!

  43. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

  44. Required Slide

More Related