UNC311_Scott Schnoll_(Exchange Server and Hyper-V)

UNC311_Scott Schnoll_(Exchange Server and Hyper-V)Exchange Server and Hyper-VUNC311AgendaHyper-V OverviewExchange Virtualization Support PolicyPerformance OverviewSystem Design and ConfigurationHigh Availability and Disaster RecoveryScenarios and RecommendationsAnalyst View on VirtualizationHyper-V OverviewHyper-V OverviewHyper-V technology is available in:Microsoft Windows Server 2008 with Hyper-V and Microsoft Windows Server 2008 R2 with Hyper-VFull Windows Server product with Hyper-V RoleAvailable in Server Core and Full InstallationSupports up to 1 TB of memory(Enterprise/Datacenter)Microsoft Hyper-V Server 2008 and Microsoft Hyper-V Server 2008 R2Standalone server virtualization productMicro-kernelized hypervisor with no third party devicesSupports up to 32 GB of memoryFree,and no CALs required(Guest OSes must be licensed and need CALs)Hyper-V OverviewHyper-V Root(Parent)Hyper-V Root(Parent)Instance of Windows 2008/R2 Instance of Windows 2008/R2 running on physical server with running on physical server with Hyper-V role installed or Microsoft Hyper-V role installed or Microsoft Hyper-V Server 2008/R2Hyper-V Server 2008/R2Hyper-V Guest(Child)Hyper-V Guest(Child)Virtual machine running a supported Virtual machine running a supported operating system,using resources operating system,using resources provided by Hyper-V rootprovided by Hyper-V rootPassthrough DiskPassthrough DiskA disk defined in the Root which is A disk defined in the Root which is made available to a single Guest as made available to a single Guest as a SCSI or IDE diska SCSI or IDE diskVirtual Hard Disk(VHD)Virtual Hard Disk(VHD)A file hosted on a disk in the Root A file hosted on a disk in the Root which appears as a disk inside the which appears as a disk inside the Guest machine.Can be used to install Guest machine.Can be used to install a supported operating system or store a supported operating system or store data data Hyper-V OverviewVirtual Machine State File(VSV)Virtual Machine State File(VSV)File hosted in Root file system used to File hosted in Root file system used to save Virtual Machine state during save save Virtual Machine state during save operation or Quick Migrationoperation or Quick MigrationDifferencing VHDsDifferencing VHDsLinked to Fixed or Dynamic VHD Linked to Fixed or Dynamic VHD disk,changes to the linked disk are disk,changes to the linked disk are written to the differencing file written to the differencing file instead of the file for the linked disk instead of the file for the linked disk so that system can be rolled back to so that system can be rolled back to a previous state.Used with a previous state.Used with Snapshots(For Testing/Demo Only)Snapshots(For Testing/Demo Only)Temp Memory Storage(BIN)Temp Memory Storage(BIN)Equal in size to the memory allocated to Equal in size to the memory allocated to the guest,this file in the Root file the guest,this file in the Root file system is used to dump memory during system is used to dump memory during a system save or a Quick Migrationa system save or a Quick MigrationFixed/Dynamic VHDsFixed/Dynamic VHDsFixed disk is configured to a preset Fixed disk is configured to a preset size and blocks are pre-allocated in size and blocks are pre-allocated in Root file systemRoot file systemDynamic disk configured to a Dynamic disk configured to a preset size but blocks are allocated preset size but blocks are allocated in Root file system as the file in Root file system as the file grows.Uses less disk,but creates grows.Uses less disk,but creates performance hit.performance hit.Exchange Virtualization Support PolicyExchange Virtualization Support PolicyExchange Server 2007 and Exchange Server 2003 http:/ Server 2010http:/ alsoMicrosoft press releasehttp:/ Volume Licensing Brief from WWLP-http:/ policy for Microsoft software running in non-Microsoft hardware virtualization software-http:/ partners for non-Microsoft hardware virtualization software-http:/ server software and supported virtualization environments-http:/ Virtualization Support PolicyExchange Server 2010 and Exchange Server 2007 with Service Pack 1 or later are supported:On Windows Server 2008 with Hyper-V or Windows Server 2008 R2 with Hyper-VOn Microsoft Hyper-V Server 2008 or Microsoft Hyper-V Server 2008 R2On any 64-bit hypervisor that has been validated under and is a participant in the Microsoft Server Virtualization Validation Program(SVVP)http:/ Server 2003 with Service Pack 2 or later is supported:On Microsoft Virtual Server 2005 R2 or later version of Virtual ServerNo other virtualization platforms supportedNo other versions of Exchange Server are supported in a hardware virtualization environmentNot SupportedMixing hypervisor-provided clustering,migration or portability solutions with Exchange HA guests(DAG,mailbox database copies)Virtualizing the Unified Messaging server roleUsing hardware-based VSS/VDS to back up guestsVSS backup of root for passthrough disks or iSCSI disks connected to initiator in guestUsing VHD disks greater 2040 GBUsing hypervisor snapshots,differencing/delta disksHaving a virtual:logical processor ratio greater than 2:1Applications running in root partitionPerformance OverviewPerformance OverviewTest results show that performance of Exchange on Hyper-V is quite goodScales well from 1 to 4 processors(per VM)Storage and network design require consideration of CPU impact to the RootAll guest I/O requests are serviced by the RootMore pieces to monitorPerformance in the RootPerform in the Exchange VMDisk PerformanceRoot System Configuration:Guest System Configuration:Network Configuration:Disk Configuration:2 x 2GHz Quad Core(8 LP),16 GB RAM4 x 2GHz(4 VP),4 GB RAM,Passthrough SCSI DisksSingle NIC in Root on Hyper-V Switch,no Jumbo Frames Dedicated LUN/Volume for DB and LOG,iSCSI-72 x 134 GB FC Disks in multiple RAID SetsClient Access PerformanceRoot System Configuration:Guest System Configuration:Network Configuration:2 x 2GHz Quad Core(8 LP),16 GB RAM4 x 2GHz(4 VP),4 GB RAMSingle NIC in Root on Hyper-V Switch Hub Transport PerformanceRoot System Configuration:Guest System Configuration:Network Configuration:Hyper-V Disk Configuration:Native Disk Configuration:2 x 2GHz Quad Core(8 LP),16 GB RAM4 x 2GHz(4 VP),4 GB RAMSingle NIC in Root on Hyper-V Switch Fixed VHD Disks via Direct Attached Storage(DAS)Direct Attached Storage(DAS)Performance AnalysisAccuracy of performance counters in guest might be a concern for monitoringCPU cycles in a VM are relative to the CPU slices provided from the virtualization layerMay skew resultsComprehensive comparison of physical resources and application consumption is difficult to achieveApplication counters are only available in the guestRoot only provides view of resources it owns and Hyper-V performance countersSystem Design and ConfigurationDeployment RecommendationsVirtualization isnt freeHypervisor adds overhead,must account for this when sizingWorkload costs rise as well,though this is more difficult to characterizeWorking on additional guidance here over the next few monthsHyper-V doesnt change Exchange design requirements from an application perspectiveDesign for Performance,Reliability and Capacity(MBX/Hub/Edge)Design for Usage Profiles(CAS/MBX)Design for Message Profiles(Hub/Edge)Installing Exchange On Hyper-VSetup experience is the same as physical serversSizing guidance is the same as physical serversCPU and Memory rules of thumb applyBuild out virtual machine configuration prior to installing ExchangeRoot ConfigurationSeparate LUNs/Arrays for Root operating system,Guest operating system VHDs and guest data storageLUNs should use RAID to provide data protection and performanceSnapshot creation and differencing disks for guest VMs are not supported for production Exchange systemsOversubscribing CPUs greater than 2:1(virtual processors-to-physical cores)is not supported for ExchangeOnly management applications running on Root(anti-virus,backup,remote tools,etc.)Guest ConfigurationExchange Server 2007 SP1 on Windows Server 2008 or Exchange Server 2010 on Windows Server 2008/R2Fixed VHDs for guest machine operating systemNeed to account for page file consumption in addition to operating system requirements15 GB+15 GB+VM Memory SizeVM Memory Size=Minimum VHD sizeMinimum VHD sizeMust include space on root for each guest machines BIN fileCAS=OS VHD Size+(VM Memory Size)CAS=OS VHD Size+(VM Memory Size)HUB=OS VHD Size+(VM Memory Size)+QueuesHUB=OS VHD Size+(VM Memory Size)+QueuesMBX=OS VHD Size+(VM Memory Size)+DBs+LogsMBX=OS VHD Size+(VM Memory Size)+DBs+LogsNetwork ConfigurationFor Exchange guest machines deployed without HA,we recommend you follow guidelines provided by your hypervisor vendorFor Exchange guest machines deployed with HA,we recommend at least two NICs in each rootOne NIC dedicated to hypervisorOne NIC dedicated to guest machinesAdditional NICs for iSCSIConfigure at least two virtual NICs for each Exchange guest that uses HA(e.g.,DAG,CCR,SCC)Exchange Storage ConfigurationExchange storage should be on spindles separate from Guest VHD physical storageExchange storage must be Fixed VHD,SCSI pass-through or iSCSIPreference is to use SCSI passthrough for Transport and Mailbox server databases and log filesAll disks should honor I/O stream segregation the same as physical(separate database and Log LUNs)FC/SCSI HBAs must be configured to Root and LUNs presented to VMs as passthroughor VHDsHyper-V and Exchange Disk StorageUsing iSCSI StorageiSCSI best performance occurs when initiator is configured to the Root and disks are presented to Guest as passthroughSeparate iSCSI gigabit network recommendedDedicated NIC with Jumbo frame and no Virtual Network Switch bound has better performanceLimits portability of VMsiSCSI in Guest is supportedPerformance hit for using the guest network stackUseful for SCCBenefit:greater portability of VMsBackup for Virtualized ExchangeNo integration between Exchange VSS Writer and Hyper-V VSS WriterYou must backup from within the guestScenarios and RecommendationsScenario:Small or Remote OfficeHyper-V is a good fit when Exchange servers in branch offices cannot be consolidated to a central data center(due to bandwidth/connectivity issues)and for small or remote branch offices that need high availabilityHyper-V enables 50%reduction of physical server count in branch scenarios where high availability is requiredScenario:Disaster RecoveryStandby servers and clusters can be created in a Hyper-V environment in the production site and/or in a warm standby siteProvide as near to the same level of functionality as possible in the event of the loss of the production siteScenario:Mobile LANFor situations that require complete network infrastructure that can be deployed to a specific location at a moments notice.A Hyper-V server can be used to host Exchange as well as file server services and domain infrastructure services in a compact form factorScenario:Server ConsolidationIn some environments,consolidating Active Directory,Client Access and Hub Transport roles on Hyper-V provides benefits,but:You need to consider the overall impact to availability of the role and to performance of the RootYou are not supporting fewer operating system instancesBalance virtual machines/roles across physical machines to reduce single point of failure riskScenario:Mailbox ConsolidationMailbox consolidation to a single resource is not an optimal deployment scenarioIncreases overall risk due to“all eggs in one basket approach”for a critical resourceExchange servers tend to be highly utilized and have few resources available for sharing with other workloads from Exchange serversRequires additional networkinterfaces and complexity,especially with iSCSI Exchange 2007 TestingPower studyWhite Paper:Comparing the Power Utilization of Native and Virtual Exchange Environmentshttp:/ Joint testing with HP at MSFT Enterprise Engineering Center(EEC)Exchange 2007 TestingPower studyWorkload16,000 active mailboxes simulated with Loadgen75%MAPI(Outlook 2007 Online,Heavy profile)25%ActiveSync(ActiveSync v12 DirectPush default script)25%OWA(2007 Enterprise default script)SMTP messages injected at 7 msg/secConclusions50%reduction in server power utilization,potentially saving 8,582 kWh/year34-37%reduction in overall solution power utilization(including storage)What should I virtualize?Exchange Teams ViewShould You Virtualize Your Exchange 2007 SP1 Environment?http:/ the Microsoft HyperGreen Tool to calculate potential savings in terms of cooling,power,and hardware,as well as CO2 emission reductions per yearIncludes technical checklists to help you evaluate your current hardware utilization footprint to see if your existing Exchange 2007 environment is a potential candidate for moving to a hardware virtualization environmentWhat should I virtualize?Analysts View“A virtualized server application or workload can yield many advantages increased utilization of hardware,simplified management and flexibility of deployment.”“Virtualization technology is not ideally suited to every x86 server workload or application.Some are a poor fit and will yield little to no business benefit if virtualized.”“Mission-and safety-critical applications are often poor candidates for virtualization the potential cost/efficiency benefits of virtualization can be easily outweighed by the risks introduced by the process of virtualization.”Source:Gartner Inc.,“Server Workloads:What Not to Virtualize,”by Brian Gammage and Philip Dawson,March 26,2008Key TakeawaysExchange on Hyper-V performance looks goodExchange on Hyper-V is a good fit for certain branch office scenariosFully assess the risks/benefits before deploying Exchange on Hyper-VExchange is a business critical application directly affecting broad base of users every dayVirtualization can add complexity and risk to your environmentSharing infrastructure is a bad thingDefine clear goals for virtualization and assessability of Exchange on Hyper-V to achievethose goals before proceedingQ&AAsk the Expert(F4)In next 70 minutes,I will be available at the“Ask the Expert”area to answer your questions