Vipul Shah Sr. Product Manager Microsoft Session Code: MGT312 What We Will Cover Why Microsoft Virtualization for Microsoft Server Applications? SQL Server Virtualization Scenarios Consolidation, BI and.
Download ReportTranscript Vipul Shah Sr. Product Manager Microsoft Session Code: MGT312 What We Will Cover Why Microsoft Virtualization for Microsoft Server Applications? SQL Server Virtualization Scenarios Consolidation, BI and.
Vipul Shah Sr. Product Manager Microsoft Session Code: MGT312 What We Will Cover 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 Virtualization Trends “What types of workloads have you deployed virtualization technology for 2006 vs. 2008” 79% Test and Development 74% 74% Production Application Servers 64% 51% Disaster Recovery Systems 29% Production Databases 30% 50% 47% Data/Storage Mgmt Systems 21% 47% Production Web Servers 47% 45% End-User Desktops 5% 2008 41% Production Middleware Systems 2006 26% 0% 20% 40% 60% Source: Virtualization and Management: Trends, Forecasts, and Recommendations; Enterprise Management Associates (EMA); April 2008 80% Customers are Reaping the Benefits Save Costs: Improve Resource Utilization • Reduce server sprawl, save space • Save on power and cooling costs • Optimize usage of current hardware resources Enhanced Business Continuity • Increase availability of business applications • Delivers cost effective high availability • Improve service levels, less downtime Agile and Efficient Management • Rapidly provision business applications • Quickly test applications • Increase administrative flexibility “By the time we hit our fifth virtual machine on a host, we’ve usually paid for the host. Long term, we will be able to reduce our total data center holdings by 75 percent.” Robert McSkinsky, Senior Systems Administrator, Dartmouth-Hitchcock Medical Center “We can no longer tolerate service interruptions. With virtualization, we are creating a redundant data center in Normandy to ensure business continuity” Amaury Pitrou, Projects Architecture, Desktops and Mobility Director Bouygues Constructions “Building a physical server took almost four hours before virtualization. Hyper-V™ has helped decrease this time to 20 minutes.” Vito Forte, Chief Information Officer WorleyParsons Microsoft Virtualization for Server Applications Business Critical Applications Business Applications Enterprise Applications Database Line Of Business (LOB) Custom Applications Collaboration Management Platform Communication Microsoft Server Applications Virtualization Platform Hyper-V™ Microsoft Virtualization = Windows Server 2008 R2 Hyper-V + System Center Microsoft Virtualization: The Best Choice for Microsoft Server Applications Microsoft Server Applications Built for Windows Complete Management Solution Low Cost Complete Solution *Built-in Virtualization with One-stop Support *Deep Application Knowledge *A comparable solution can cost up to six times more† *Large Partner Ecosystem *Physical & Virtual Management *Lower Ongoing Costs 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. Virtualization Deployment Scenarios for Microsoft SQL Server Currently a variety of consolidation strategies exist and are utilized. Typically, as isolation goes up, density goes down and operation cost goes up. IT Managed Environment Virtual Machines Instances Databases MyServer Sales_1 Consolidate_1 Marketing_1 Online_Sales ERP_10 ERP_10 Microsoft Confidential DB_1 DB_2 DB_3 Schemas Higher Density, Lower Costs Higher Isolation, Higher Costs SQL Server Consolidation Consolidation Considerations Multiple SQL Instances Multiple Virtual Machines (VM) Isolation Shared Windows instance Dedicated Windows instance CPU Resources Number of CPUs visible to Windows instance Up to 4 virtual CPUs CPU over-commit is supported Memory Server Limit Dynamic(max server memory) Statically allocated to VM (Offline changes only) 64GB limit per VM 2 TB Limit per Host Storage SQL Data Files with standard storage options SQL Data Files using Passthrough or Virtual Hard Disks exposed to VM Windows System Resource Manager(process level) SQL Server Resource Governor Hyper-V guest VM SQL Server Resource Governor 50 Practical limit determined by physical resources Clustering, Database Mirroring, Log Shipping, Replication Live Migration, Guest Clustering, Database Mirroring, Log Shipping, Replication Good Comparable with multiple instances, acceptable overhead Resource Management Number of instances High Availability Performance Virtual Memory & Second-Level Translation With Virtualization an additional level of mapping is required Second Level Address Translation (SLAT) provides the extra translation into Virtual Machine address spaces Performance advantage over non-enabled CPUs The Virtual / Process view Virtual Machine 1 Virtual Machine 3 Virtual Machine 1 Hyper Visor Operating System The Physical / real view Physical Memory Pages SQL Server Consolidation Scalability Configuration: Results: • 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 • Increased throughput with consolidation • Near linear scale in throughput with no CPU over- commit • Improved performance with Windows Server 2008 R2 and SLAT processor architecture Throughput (Batch requests/sec) Virtual Instances Scalability % CPU 80 Almost Linear Scale No CPU over-commit 3500 CPU over-commit 70 3000 60 2500 Heavy Load 50 2000 40 ) 1500 30 Moderate Load 1000 20 500 10 0 0 1VM 2VM Batch req/sec 3VM 4VM %CPU 5VM 6VM Relative Throughput 7VM 8VM Relative Throughput for Windows Server 2008 Low Load SQL Server Consolidation Scalability Configuration: • OS: Microsoft® Windows Server® 2008 R2 Hyper-V™ • Hardware: HP DL785 (32 core, and 48 cores) with SLAT Hitachi Data Systems AMS2500 Storage • Virtual Machines: 4 virtual processors and 7 GB RAM per virtual machine; Fixed size VHD Results: • Drop-in compatibility of Istanbul processors with existing infrastructure • ~50% performance improvement with AMD HyperTransport Assist (Intel snoop filter) feature • Keep cache coherency traffic between the two sockets from appearing on the external bus Comparing Istanbul vs. Shanghai 100 90 94.05 82.12 93.12 90.28 4500 91.70 80 70 5000 55% 4000 42% Batches/sec_Istanbul 3500 Batches/sec_Shanghai 3000 %Processor Time_Istanbul 50 2500 %Processor Time_Shanghai 40 2000 Relative Throughput_Istanbul 30 1500 Relative Throughput_Shanghai 20 1000 10 500 59.79 60 60.67 57.84 57.84 60.15 0 0 VM1 VM2 VM4 VM6 VM8 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 Virtualization Benefits: • Increase agility by rapidly provisioning and scalingout BI components on demand • Reduce the number of physical servers, save on power and space • If virtual, put SSIS and Data Warehouse on the same Virtual Machine (VM) External ERP Web VM Legacy Reporting Server Operational Data Store SQL Server® Integration Services (SSIS) Data Warehouse (DW) Reporting Server Click Here For More Information Data Mart & OLAP Cube Data Mart & OLAP Cube 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 Click Here For More Information 2 3 SQL Server Database Mirroring Hyper-V Live Migration Technology in Windows Server 2008 R2 that allows you to move running VMs from one physical server to another physical server without disruption of service or perceived downtime Live Migration Process 1. 2. a) b) 3. a) b) 4. Initiated via in-box cluster UI, SCVMM, PowerShell VM State/Memory Transfer Create VM on the target Move memory pages from the source to the target via Ethernet Final state transfer and virtual machine restore Pause virtual machine Move storage connectivity from source host to target host via Ethernet Un-pause & Run Host 1 Blue = Shared Storage (FC, iSCSI) Yellow = Networking Green = Live migration networking (1Gb or better) Host 2 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 Virtualization Benefits: • No loss of service during failover with live migration. Migration is completely transparent to the user • Improve availability with less complexity • Better server utilization due to consolidation • Easier set up and management through System Center VMM Click Here For More Information VM 11 Live Migration Host cluster Shared Storage iSCSI, SAS, Fibre 2 Performance & Resource Optimization PRO Pack Technologies Virtual Machine Manager PRO Packs Partner PRO Technology Brocade Monitor IO performance from the server to the data in the SAN Dell The “PRO-enabled” Dell Management Pack ensures that host machines operate under normal power and temperature thresholds. Other PRO alerts include memory, storage controller, and disk remediation. Citrix Workflows can be initiated to automatically start or provision VMs based on an entity’s health and automatically update NetScaler load balancing rules Emulex Monitor I/O rates across the HBA relative to maximum available bandwidth HP Monitor the following attributes of their servers: hard drive, array controller, power, temperature, processor, memory, fans, and alert on degradation or critical errors providing the appropriate recommended resolution Quest Software For non-Windows Operating Systems and non-Microsoft application technologies, the solution enables intelligent virtual machine tuning Secure Vantage Extends the native capabilities of Security Management providing users the ability to mitigate risk and remediate policy violations across virtual environments For complete list, visit http://www.microsoft.com/systemcenter/virtualmachinemanager/en/us/pro-partners.aspx Hyper-V Configuration Guidelines 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 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 requirements OS 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 SQL Server Best Practices Guest virtual machines are limited to 4 CPU cores Best performance if VMs are not over-committed for CPU 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. Virtualization Deployment Scenarios for Microsoft Office SharePoint Server 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: o Windows® SharePoint Services o Web Application Service • Application Servers: o Office SharePoint Server Search Service (Index or Query) o Document Conversion Launcher Service o Document Conversion Load Balancer Service o Excel Calculation Services • SQL Server SharePoint Roles & Virtualization Considerations Role Virtualization Decision Considerations and Requirements Ideal • Easily provision additional servers for load balancing and fault tolerance Query Role Process Search Queries Ideal • For large indexes, use physical volume over dynamic expanding VHD • Requires propagated copy of local index Application Role Excel Forms Services Ideal • Provision more servers as resource requirements for individual applications increase Web Role Render Content Index Role Crawl Index Database Role Consider Consider • Environments where significant amount of content is not crawled • Requires enough drive space to store the index corpus • Environments with lower resource usage requirements • Implement SQL Server® alias for the farm required For details, see SharePoint Virtualization whitepaper at http://www.microsoft.com/virtualization/solutions/business-critical-applications 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 Click Here for More Information Failover Server Shared Storage iSCSI, SAS, Fibre PRODUCTION Index 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 seconds with 1% concurrency with a heavy user load profile of over 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 Click here for more information Source: EMC Virtual Architecture for Microsoft Office SharePoint Server 2007 Enabled by Hyper-V (whitepaper) SharePoint Virtualization Best Practices Best Practices and Recommendations CPU • Configure a 1-to-1 mapping of virtual processor to logical processors for best performance • Be aware of “CPU bound” issues Memory • Ensure enough memory is allocated to each virtual machine Disk • Be aware of underlying disk read write contention between different virtual machines to their virtual hard disks • Ensure SAN is configured correctly Network • Use VLAN tagging for security • Associate SharePoint® virtual machines to the same virtual switch Others • Ensure that integration components are installed on the virtual machine • Do not use other host roles (use server core) • Avoid single point of failure: load balance your virtual machines across hosts and cluster virtual machines Virtualization Deployment Scenarios for Microsoft Exchange Server Exchange 2010 Sizing Guidance Role Physical Deployment Virtual Deployment Notes Maximum Processor Cores Memory Sizing Processor Core : MBX Ratio Maximum Virtual Processors Memory Sizing Standard VM Standard VM Ratio Edge/ Hub 12 processor cores 1 GB per processor core • 1:5 with Anti-Virus • 1:7 with no AV 4 virtual processors 1 GB per processor core 4 VPs + 4GB 1 HUB VM : 5 MBX VMs To accommodate peak I/O (e.g. processing queue) locate Transport DB + Logs on separate spindles CAS 12 processor cores 2GB per processor core 3:4 4 virtual processors 2 GB per processor core 4 VPs + 8GB 3 CAS VMs : 4 MBX VMs Detailed guidance to be available by early Dec CAS/ Hub MultiRole 12 processor cores 2GB per processor core 1:1 4 virtual processors 2 GB per processor core 4 VPs + 8GB 1 CAS/HUB VM : 1 MBX VM Simplifies core ratio. Better balanced workloads on typical servers which have 8, 16 or 24 core counts. MBX 12 processor cores 4GB + 330MB per MBX N/A 4 virtual processors 4GB + 330MB per MBX 4GB + 330MB per MBX 4 VPs + 1624GB Adjust for number of mailboxes and database cache for send/receive profile CAS/HUB CAS/HUB MBX CAS/HUB CAS/HUB CAS/HUB MBX CAS/HUB 8 cores MBX MBX MBX MBX 16 cores 24 cores Mailbox Server Guidelines Virtual Processor ≠ Logical Processor • Total Send + Receive (75k message size) Database Cache Per Mailbox (MB) Users Per Core Physical MBX Role Users Per VP Virtual MBX Role 50 1000 900 12 100 900 810 250 15 150 800 720 300 18 200 700 630 350 21 250 600 540 400 24 300 500 450 450 27 350 400 360 500 30 400 300 270 50 3 100 6 150 9 200 Total Send + Receive (75k message size) Mailbox Storage Configuration Recommended configuration for database and log volumes 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 Exchange 2010 High Availability 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 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 Host Based Failover Clustering Live Migration and Exchange 2010 Support Guidelines Supportability Quick Reference Exchange 2010 2010 SP2 or R2 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 For More Information… Virtualization Windows Server 2008 R2 Hyper-V http://www.microsoft.com/windowsserver2008/en/us/hyperv-main.aspx Windows Virtualization Team Blog http://blogs.technet.com/virtualization Infrastructure Planning and Design Guides for Virtualization http://technet.microsoft.com/en-us/solutionaccelerators/ee395429.aspx?SA_CE=VIRT-IPD-WEB-MSCOM2009-09-21 Microsoft Virtualization Solutions http://www.microsoft.com/virtualization/en/us/solution-business-apps.aspx Exchange Exchange Virtualization Best Practices Webcast http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=enUS&EventID=1032428204&CountryCode=US Exchange Server 2010 Guidance http://technet.microsoft.com/en-us/library/bb124558(EXCHG.140).aspx Exchange Team Blog http://blogs.technet.com/exchange For More Information… SQL Server SQL Server Virtualization http://www.microsoft.com/sqlserver/2008/en/us/virtualization.aspx SQL Server Whitepapers http://www.microsoft.com/sqlserver/2008/en/us/white-papers.aspx SQL Server Virtualization Best Practices Webcast http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032428764&EventCateg ory=5&culture=en-US&CountryCode=US SharePoint Solutions for Optimizing SharePoint http://www.microsoft.com/systemcenter/en/us/managing-microsoft-applications/optimizingsharepoint.aspx Microsoft Virtualization Solutions http://www.microsoft.com/virtualization/en/us/solution-business-apps.aspx Microsoft Consulting Services UK SharePoint Blog http://blogs.msdn.com/uksharepoint/archive/2009/03/04/topic-1-recommendations-foroptimizing-the-performance-of-a-virtualized-sharepoint-environment.aspx Resources www.microsoft.com/teched www.microsoft.com/learning Sessions On-Demand & Community Microsoft Certification & Training Resources http://microsoft.com/technet http://microsoft.com/msdn Resources for IT Professionals Resources for Developers Complete an evaluation on CommNet and enter to win an Xbox 360 Elite! © 2009 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.