VIR314 Microsoft Server Applications Built for Windows *Built-in Virtualization with One-stop Support Complete Management Solution Low Cost Complete Solution *Deep Application Knowledge *A comparable solution can cost up to six times.
Download ReportTranscript VIR314 Microsoft Server Applications Built for Windows *Built-in Virtualization with One-stop Support Complete Management Solution Low Cost Complete Solution *Deep Application Knowledge *A comparable solution can cost up to six times.
VIR314 Microsoft Server Applications Built for Windows *Built-in Virtualization with One-stop Support Complete Management Solution Low Cost Complete Solution *Deep Application Knowledge *A comparable solution can cost up to six times more† *Large Partner Ecosystem *Physical & Virtual Management Increased Deployment Options *Cross Platform and Hypervisor Support *Lower Ongoing Costs 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. Memory Available value can be negative, indicating VM is under memory pressure and guest OS is paging Virtualization Deployment Scenarios for Microsoft SQL Server Higher Isolation, Higher Costs 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 Schemas MyServer Sales_1 Consolidate_1 Marketing_1 Online_Sales ERP_10 ERP_10 Microsoft Confidential DB_1 DB_2 DB_3 Higher Density, Lower Costs Multiple SQL Instances Multiple Virtual Machines (VM) Shared Windows instance Dedicated Windows instance 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 number of VMs supported is limited by the hardware resources only. Note that there is a 384 VM limit and a 50 VM limit for clustering. Clustering, Database Mirroring, Log Shipping, Replication Live Migration, Guest Clustering, Database Mirroring, Log Shipping, Replication Good Comparable with multiple instances, acceptable overhead Isolation CPU Resources Resource Management Number of instances High Availability Performance Support SQL Server 2005 to SQL Server 2008 Enterprise Edition The Virtual / Process view Virtual Machine 1 Virtual Machine 3 Virtual Machine 1 Hyper Visor Operating System The Physical / real view Physical Memory Pages 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 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 scaling-out 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 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 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 11 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 Live Migration Host cluster Shared Storage iSCSI, SAS, Fibre 22 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 OS VHD Size (minimum 15GB) + VM Memory Size = Minimum VHD size OS VHD Size + (VM Memory Size) + Data Files + Log Files Virtualization Deployment Scenarios for Microsoft Office SharePoint Server 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 Role Virtualization Decision Considerations and Requirements Web Role Render Content 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 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 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 ondemand provisioning Failover Server Shared Storage iSCSI, SAS, Fibre PRODUCTION Index Click Here for More Information 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) 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 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 + 3-30MB 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 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 100 900 810 12 150 800 720 250 15 200 700 630 300 18 250 600 540 350 21 300 500 450 400 24 350 400 360 450 27 400 300 270 500 30 50 3 100 6 150 9 200 Total Send + Receive (75k message size) Exchange 2010 2010 SP2 or R2 http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA1-2127ENW.pdf http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA1-9895ENW.pdf http://www.microsoft.com/virtualization http://technet.microsoft.com/library/cc753637(WS.10).aspx http://blogs.technet.com/b/virtualization/ http://blogs.msdn.com/b/virtual_pc_guy www.microsoft.com/teched www.microsoft.com/learning http://microsoft.com/technet http://microsoft.com/msdn