330 likes | 347 Views
Deploying Business Critical Workloads and Applications. Dai Vu Director, solutions marketing Microsoft Corporation. Virtualization Trends. Source: Virtualization and Management: Trends, Forecasts, and Recommendations ; Enterprise Management Associates (EMA); April 2008.
E N D
Deploying Business Critical Workloads and Applications Dai Vu Director, solutions marketing Microsoft Corporation
Virtualization Trends Source: Virtualization and Management: Trends, Forecasts, and Recommendations; Enterprise Management Associates (EMA); April 2008
Microsoft Virtualization for Server Applications Business Critical Applications Management Platform Business Applications Enterprise Applications Line Of Business (LOB) Custom Applications Database Collaboration Communication Microsoft Server Applications Virtualization Platform Microsoft Virtualization = Windows Server 2008 R2 Hyper-V +System Center Hyper-V™
Virtualization Deployment Scenarios for Microsoft SQL Server
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 Marketing_1 Online_Sales DB_1 ERP_10 DB_2 ERP_10 DB_3 Microsoft Confidential
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
SQL Server Consolidation Scalability Results: • Drop-in compatibility of Istanbul processors with existing infrastructure • ~50% performance improvement with AMD HyperTransport Assist feature • Keep cache coherency traffic between the two sockets from appearing on the external bus 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
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
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
PRO Pack Technologies Virtual Machine Manager PRO Packs 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 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
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: • 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
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
Virtualization Deployment Scenarios for Microsoft Exchange Server
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
Exchange 2010 Sizing Guidance 8 cores CAS / HUB Multi-Role Server 16 cores 24 cores
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%
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
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
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
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
Support Guidelines • TechNet is the single source: http://technet.microsoft.com/en-us/library/cc794548.aspx • SVVP Support Policy Wizard is a great tool:http://www.windowsservercatalog.com/svvp.aspx?svvppage=svvpwizard.htm • Always confirm SPW results with our TechNet article • Check back for updates • Clarifications published frequently
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)
Microsoft Virtualization: The Best Choice for Microsoft Server Applications Microsoft Server Applications Built for Windows Complete Management Solution 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.
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-MSCOM-2009-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=en-US&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&EventCategory=5&culture=en-US&CountryCode=US SharePoint • Solutions for Optimizing SharePoint http://www.microsoft.com/systemcenter/en/us/managing-microsoft-applications/optimizing-sharepoint.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-for-optimizing-the-performance-of-a-virtualized-sharepoint-environment.aspx
© 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.